Install Jentic One Beta

Connect the FraudLabs Pro Fraud Detection to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FraudLabs Pro Fraud Detection, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffraudlabspro.com%2Ffraudlabs-pro-fraud-detection" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffraudlabspro.com%2Ffraudlabs-pro-fraud-detection" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with FraudLabs Pro Fraud Detection API.

Score a transaction for fraud risk via /v1/order/screen with order, billing, IP, and payment fields

Receive a fraud score and recommended action (approve, review, reject) for each scored order

Submit post-transaction feedback (approved, rejected, chargeback) via /v1/order/feedback

Detect proxy, VPN, and high-risk IP signals as part of the screening response

GET STARTED

Start building with FraudLabs Pro Fraud Detection API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use FraudLabs Pro Fraud Detection API for, with concrete tasks.

★ Real-Time Order Screening

An online merchant calls /v1/order/screen during checkout with the cart, billing and shipping addresses, customer IP, and payment method. FraudLabs Pro returns a numeric fraud score plus recommended action so the merchant can auto-fulfil low-risk orders, route medium-risk to manual review, and reject high-risk ones before settlement.

POST /v1/order/screen with the API key plus the order, billing, shipping, IP, and payment payload, then act on the recommended action in the response

Post-Transaction Feedback Loop

Once the bank settles or charges back, the merchant calls /v1/order/feedback with the original order id and the realised outcome. FraudLabs Pro uses the feedback to tune the per-merchant model so future screens reflect what is actually fraud for that merchant's customer base.

POST /v1/order/feedback with the order id and the status (APPROVED, REJECTED, or CHARGEBACK) once the transaction settles

Cash-On-Delivery Risk Filter

Cash-on-delivery merchants in Southeast Asia screen orders against FraudLabs Pro before dispatching the courier. The screen catches obvious fraud signals (mismatched IP and shipping country, proxy IPs, blacklisted phone numbers) so the merchant avoids the most expensive failure mode for COD: a delivered order the customer refuses.

POST /v1/order/screen with the COD order's phone, address, and IP and decline dispatch if the recommended action is REJECT

AI Agent Fraud Triage

An agent triages a checkout queue, calling FraudLabs Pro through Jentic to score each order and submitting feedback once outcomes are known. The agent never sees the API key directly and surfaces a plain-language summary explaining the verdict for each order.

Search Jentic for 'score an order for fraud risk', load the /v1/order/screen schema, execute against each pending order, then post a summarised verdict to operations

Key Endpoints

2 endpoints — fraudlabs pro fraud detection is the version 1 fraud-screening api for online merchants who need to detect chargeback risk on credit-card, paypal, and cash-on-delivery transactions.

METHOD

PATH

DESCRIPTION

POST

/v1/order/screen

Score an order for fraud risk

POST

/v1/order/feedback

Submit post-transaction feedback (APPROVED, REJECTED, CHARGEBACK)

POST

/v1/order/screen

Score an order for fraud risk

POST

/v1/order/feedback

Submit post-transaction feedback (APPROVED, REJECTED, CHARGEBACK)

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the FraudLabs Pro Fraud Detection API by hand means appending your license key to each request and building your own retry and error handling around the screen and feedback endpoints. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.

Permission scoping

FraudLabs Pro Fraud Detection carries the order details in the request body rather than the URL path, so scoping is operations-only: you limit the agent to the operations it needs, such as scoring an order, and leave out posting feedback unless you add it. Every operation the agent can run is one you chose.

Credential isolation

Your FraudLabs Pro license key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'score an order for fraud risk', and Jentic returns the matching FraudLabs Pro operation with its input schema so the agent works with the two endpoints directly rather than parsing the spec.

FAQs

Specific to using FraudLabs Pro Fraud Detection API through Jentic.

What authentication does the FraudLabs Pro Fraud Detection API use?

The v1 fraud-detection API takes the FraudLabs Pro license key on each request as a parameter. Through Jentic, the key is stored encrypted in the vault and substituted at execution time so it never enters the agent's context.

Can I score a credit-card transaction for fraud risk with this API?

Yes. POST to /v1/order/screen with the billing address, shipping address, customer IP, item list, and payment method. The response carries a numeric fraud score, a recommended action, and the underlying signals such as IP proxy detection and address mismatch.

What are the rate limits for the FraudLabs Pro Fraud Detection API?

FraudLabs Pro applies monthly transaction quotas per plan rather than per-second rate limits. The free Micro plan covers a few hundred screens per month and paid plans scale into the millions; only /v1/order/screen calls count toward quota, not feedback.

How do I send chargeback feedback through Jentic?

Search Jentic for 'send fraud feedback', load the /v1/order/feedback schema, and execute it with the order id from the original screen plus status set to CHARGEBACK. The feedback retrains the per-merchant model so future screens of similar customers are more accurate.

Is the FraudLabs Pro v1 API free?

FraudLabs Pro offers a free Micro plan with a small monthly screen allowance, and paid plans scale by volume. The v1 fraud-detection endpoints share the same plan and quota as the rest of the FraudLabs Pro product.

Should I use v1 or v2 of the FraudLabs Pro API?

New integrations should use v2 (under /v2/order/screen) for the latest signals and the SMS verification endpoints. The v1 endpoints under /v1 remain supported for legacy integrations and follow the same scoring contract.

Can I limit what my agent is allowed to do with the FraudLabs Pro Fraud Detection API?

Yes. Because this API carries the order details in the request body rather than the URL path, scoping is operations-only, and your self-hosted Jentic One instance enforces the rules you set for which operations the agent may call. You can allow the agent to score an order via /v1/order/screen while leaving out /v1/order/feedback, or enable both if you want the agent to submit post-transaction outcomes. Every operation the agent can run is one you chose, and your license key stays with your own instance and is injected only at execution time.

FraudLabs Pro Fraud Detection

Browse all Fraudlabspro APIs

AI ReadinessFoundational (C)56/100

See full scorecard

Community OpenAPI document · agent-readySecurityThreat DetectionapiKey2 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Score a transaction for fraud risk and submit post-transaction feedback through FraudLabs Pro's v1 fraud-detection endpoints. Authentication is the API key on each request.

Use for: I need to score a transaction for fraud risk, Send a chargeback signal for an order I screened earlier, Check whether the customer's IP looks like a proxy, Mark an order as approved so the model learns the outcome

Not supported: Does not handle payment processing, refunds, or SMS verification - use for transaction fraud scoring and post-transaction feedback only.

FraudLabs Pro Fraud Detection is the version 1 fraud-screening API for online merchants who need to detect chargeback risk on credit-card, PayPal, and cash-on-delivery transactions. The spec exposes two endpoints: /v1/order/screen scores a transaction in real time and returns a fraud verdict with the underlying signals, while /v1/order/feedback records the eventual outcome (approved, rejected, chargeback) so the per-merchant model improves with usage.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the FraudLabs Pro Fraud Detection to your agent

Capabilities

Start building with FraudLabs Pro Fraud Detection API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

FraudLabs Pro Fraud Detection

Jentic AI Readiness Score

FraudLabs Pro Fraud Detection

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness