Install Jentic One Beta

Connect the FraudLabs Pro API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FraudLabs Pro API, 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" | 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" | 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 API.

Score an order for fraud risk via /order/screen with billing, shipping, IP, and payment fields

Retrieve a previously screened order's verdict and signals via /order/result

Send post-transaction feedback (approved, rejected, chargeback) via /order/feedback to improve the model

Trigger an SMS verification code to a customer phone via /verification/send

GET STARTED

Start building with FraudLabs Pro API

Explore with Jentic One

View OpenAPI Document

Use Cases

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

★ E-Commerce Checkout Risk Scoring

An online store calls /order/screen at checkout with the cart, billing address, shipping address, IP, and payment method. FraudLabs Pro returns a numeric score plus an action recommendation (approve, review, reject) within a few hundred milliseconds, letting the store auto-fulfil low-risk orders and route high-risk ones to manual review.

POST to /order/screen with the order payload and the API key in the 'key' parameter, then branch on the recommended action returned by the API

Closed-Loop Feedback for Model Tuning

After the merchant settles or charges back an order, the integration calls /order/feedback so FraudLabs Pro learns whether its earlier verdict was correct. Sending feedback is what keeps the per-merchant fraud model accurate over time and is the single highest-leverage thing an integrator can do.

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

SMS Step-Up Verification

When the screen verdict is REVIEW, the merchant triggers /verification/send to push an OTP to the customer's phone, then confirms the code through /verification/result. A successful OTP softens the risk signal and lets the order proceed without manual review.

POST /verification/send with the customer phone, then on user input POST /verification/result with the otp_code and check the response state

AI Agent Risk Triage

An agent monitoring a checkout queue uses Jentic to score orders, send feedback, and request SMS verification when the score is borderline. The agent never holds the FraudLabs Pro key directly and surfaces a plain-language summary of why each order was approved or flagged.

Search Jentic for 'score an order for fraud risk', load the /order/screen schema, execute against each pending order, and post a triage summary back to operations

Key Endpoints

5 endpoints — fraudlabs pro screens online transactions for chargeback risk before merchants commit to fulfilment.

METHOD

PATH

DESCRIPTION

POST

/order/screen

Score an order for fraud risk

GET

/order/result

Retrieve a previously screened order's verdict

POST

/order/feedback

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

POST

/verification/send

Trigger an SMS verification code

POST

/verification/result

Confirm an SMS verification code

POST

/order/screen

Score an order for fraud risk

GET

/order/result

Retrieve a previously screened order's verdict

POST

/order/feedback

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

POST

/verification/send

Trigger an SMS verification code

POST

/verification/result

Confirm an SMS verification code

Why Jentic?

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

Setup

Wiring the FraudLabs Pro API by hand means appending your API key to each request and building your own retry and error handling across its fraud-scoring, feedback, and SMS verification endpoints. Through Jentic you install once, import FraudLabs Pro from the API Directory, store the key once, and your agent calls it.

Permission scoping

FraudLabs Pro carries the order and verification 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 screening an order or reading a result, and leave out sending SMS codes or posting feedback unless you add them. Every operation the agent can run is one you chose.

Credential isolation

Your FraudLabs Pro API 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' or 'send chargeback feedback', and Jentic returns the matching FraudLabs Pro operation with its input schema so the agent does not need to read the developer docs.

FAQs

Specific to using FraudLabs Pro API through Jentic.

What authentication does the FraudLabs Pro API use?

FraudLabs Pro uses an API key passed as the 'key' query or body parameter on every call. Through Jentic, the key is stored encrypted in the vault and substituted at execution time, so the raw key never enters the agent's context.

Can I score an order for fraud risk with the FraudLabs Pro API?

Yes. POST to /order/screen with the order payload - billing address, shipping address, customer IP, payment method, item list, and amounts. The response includes a numeric fraud score, a recommended action, and risk signals such as IP geolocation and proxy detection.

What are the rate limits for the FraudLabs Pro API?

FraudLabs Pro applies per-plan monthly transaction quotas rather than per-second rate limits, with the free Micro plan allowing a few hundred screens per month and paid plans scaling into the millions. Quota is enforced on /order/screen calls; feedback and result retrieval do not count.

How do I send chargeback feedback through Jentic?

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

Is the FraudLabs Pro API free?

FraudLabs Pro offers a free Micro plan with a small monthly screen allowance, plus paid Mini, Small, Medium, and Large plans that scale by transaction volume and include faster support. SMS verification is billed per message in addition to the screen quota.

How do I run SMS step-up verification on a borderline order?

When /order/screen returns a REVIEW recommendation, POST /verification/send with the customer's phone number to deliver an OTP, then POST /verification/result with the user-entered code. A successful verification softens the risk score and lets the order proceed without human review.

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

Yes. Because you self-host Jentic One, your own rules decide which FraudLabs Pro operations the agent may call, and it can only run the ones you grant. FraudLabs Pro carries order and verification details in the request body rather than the URL, so scoping is operations-only: you can allow the agent to screen an order via /order/screen and read a verdict via /order/result while leaving out sending SMS codes through /verification/send or posting feedback via /order/feedback. Your API key is injected only for the operations you approve, so every call the agent can make is one you chose.

FraudLabs Pro API

Name: FraudLabs Pro API
Brand: FraudLabs Pro API
Availability: InStock

Browse all Fraudlabspro APIs

Official vendor OpenAPI document · agent-readySecurityThreat DetectionapiKey5 EndpointsREST

For Agents

Score an order for fraud risk in real time, send post-transaction feedback to improve the model, and run SMS step-up verification when needed. Authentication is an API key in the 'key' query or body parameter.

Use for: I need to score this checkout order for fraud risk, Send a chargeback feedback signal for an order I screened last week, Trigger an SMS verification code to a customer to confirm their phone, Verify the OTP a customer just typed in

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

FraudLabs Pro screens online transactions for chargeback risk before merchants commit to fulfilment. The version 2 API exposes five endpoints covering real-time order screening, asynchronous order-result retrieval, post-transaction feedback (approved, rejected, chargeback) for model improvement, plus an SMS verification flow for step-up authentication. It returns a numeric fraud score, distance and proxy signals, and a recommended action so merchants can auto-approve, review, or reject.

Jentic One on Github View OpenAPI Document

Connect the FraudLabs Pro API to your agent

Capabilities

Start building with FraudLabs Pro API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

FraudLabs Pro API