Install Jentic One Beta

Connect the Maskbreak Fraud Detection API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Maskbreak Fraud Detection 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%2Fmaskbreak.com%2Fmaskbreak" | 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%2Fmaskbreak.com%2Fmaskbreak" | 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 Maskbreak Fraud Detection API.

Evaluate a visitor session from the client-side token, fingerprintEventId, email, and timezone to get an allow, review, or block decision

Look up any public IP for Tor exit and cloud-server range matches and read its ASN, AS name, and registration country

Check up to 20 public IPs in one keyless bulk call for quick triage

Read the key's hourly quota, monthly allowance, and lookups used without consuming evaluation quota

GET STARTED

Start building with Maskbreak Fraud Detection API

Explore with Jentic One

View OpenAPI Document

Use Cases

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

★ Agent-driven fraud triage through Jentic

An agent reviewing signups or orders can call Maskbreak through Jentic to triage each one: it evaluates the session when a client-side token is available, falls back to an IP lookup when only an address is known, and routes review verdicts to a human. The verdict and 0-100 risk score give the agent a clear decision field instead of raw network data.

For each new signup in the queue, look up its IP with the Maskbreak lookup operation, flag any result with a review or block verdict, and post the flagged signups with their risk scores to the review channel

Checkout and signup bot screening

Sites that see fake accounts or card testing evaluate each visitor session server-side by forwarding the Maskbreak client-side token along with the email and timezone. The decision reflects network, device, and email signals, and when the client token is missing the API returns a degraded answer flagged with degraded: true so the caller knows the network layer could not run.

POST the visitor's Maskbreak token, fingerprintEventId, and email to the evaluate operation, block the signup if the decision is block, and require email verification if it is review

Quota-aware monitoring

Teams on the Free plan get 10,000 visitor checks a month, up to 1,000 an hour, and a used-up monthly allowance answers with the monthly_quota_exceeded code. Reading the usage route, which consumes no evaluation quota, lets an integration slow down or alert before checks start failing.

Call the usage operation, compare month_used to monthly_limit, and send an alert when the remaining monthly allowance is running low

Key Endpoints

10 endpoints — the maskbreak fraud detection api scores visitor sessions and ip addresses for fraud signals such as vpns, residential proxies, datacenter hosts, antidetect browsers, tor exits, and bots, and returns an allow, review, or block verdict with a 0-100 risk score.

METHOD

PATH

DESCRIPTION

POST

/v1/evaluate

Evaluate a visitor session

GET

/v1/lookup/{ip}

Look up an arbitrary IP address

GET

/v1/usage

Quota position for the calling key

POST

/oauth/token

Exchange an API key for a short-lived bearer token

POST

/api/lookup-bulk

Free bulk IP check

GET

/v1/evaluate/sample

Sample evaluation response

POST

/v1/evaluate

Evaluate a visitor session

GET

/v1/lookup/{ip}

Look up an arbitrary IP address

GET

/v1/usage

Quota position for the calling key

POST

/oauth/token

Exchange an API key for a short-lived bearer token

POST

/api/lookup-bulk

Free bulk IP check

GET

/v1/evaluate/sample

Sample evaluation response

Why Jentic?

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

Setup

Wiring Maskbreak by hand means choosing between a bearer API key and the OAuth client_credentials exchange, keeping live and test keys apart, and tracking hourly and monthly quotas yourself. Through Jentic you install once, import Maskbreak from the API Directory, store the key once, and your agent calls it.

Permission scoping

Maskbreak carries the session details in the request body, so rules bound which operations your agent may call rather than which visitor. You choose the operations it may call, such as IP lookups and usage reads, so session evaluations that spend your visitor-check allowance are not included unless you add them.

Credential isolation

Your Maskbreak 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 'detect a VPN user' or 'score a visitor for fraud', and Jentic returns the matching Maskbreak operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Maskbreak Fraud Detection API through Jentic.

What authentication does the Maskbreak Fraud Detection API use?

Per its OpenAPI spec, the Maskbreak API accepts your API key as a bearer token, with live keys starting sk_live_, or a short-lived token from the OAuth client_credentials grant at /oauth/token, where client_id is your account email and client_secret is your API key. The device-evidence challenge accepts the bearer key, while the free lookup, sample, status, and threat-feed routes need no credential. Through Jentic the key is stored encrypted on your own instance and injected at call time.

Is there a Maskbreak MCP server?

You don't need an MCP server to give your agent Maskbreak. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context.

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

Yes. For a triage agent, write a rule that allows only the IP lookup and usage operations, so it can score addresses and check remaining quota but cannot run session evaluations that draw on your visitor-check allowance. Every call it makes is logged.

What are the rate limits for the Maskbreak API?

The spec states the Free plan allows 10,000 visitor checks a month, up to 1,000 an hour, and that the keyed IP lookup has its own monthly allowance of 10 times the plan's visitor checks. The keyless bulk check takes up to 20 IPs and is limited to 3 batches an hour per caller IP. A used-up monthly allowance returns the monthly_quota_exceeded code. See https://maskbreak.com/pricing for paid plan limits.

What is the difference between evaluating a session and looking up an IP?

Evaluating a session uses the client-side Maskbreak token for full network and device intelligence, so it can detect VPNs, residential proxies, antidetect browsers, and bots. A bare IP lookup only checks Tor exit lists and published cloud-server ranges, keeps country and city null, and known: false means neither list matched, not that the address is safe.

How do I check an IP address with Maskbreak through Jentic?

Search Jentic for an intent like 'check if an IP is a VPN or proxy', import the Maskbreak API, and store your API key once. Your agent then calls GET /v1/lookup/{ip} and reads the verdict and risk score. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Maskbreak Fraud Detection API

AI ReadinessAI-Aware (B+)67/100

See full scorecard

Official vendor OpenAPI document · agent-readySecurityThreat Detectionbearer, oauth210 EndpointsREST

For Agents

Evaluate a visitor session or IP address for VPN, proxy, datacenter, Tor, and bot signals and get an allow, review, or block verdict with a risk score. Check quota usage and run keyless single or bulk IP checks.

Use for: Check whether this signup came through a VPN or residential proxy, I need to score a visitor session for fraud before approving checkout, Look up whether an IP address is a Tor exit node, Find out if an IP belongs to a cloud datacenter range

Not supported: Does not handle payment processing, chargeback disputes, user authentication, or IP geolocation down to city level. Use for fraud, proxy, VPN, and bot risk verdicts only.

The Maskbreak Fraud Detection API scores visitor sessions and IP addresses for fraud signals such as VPNs, residential proxies, datacenter hosts, antidetect browsers, Tor exits, and bots, and returns an allow, review, or block verdict with a 0-100 risk score. Live visitor evaluation combines a client-side token with network and device evidence, while bare IP lookups check Tor exit lists and published cloud-server ranges with more limited coverage. A usage route reports the calling key's hourly and monthly quota position, and keyless free lookup routes check a single IP or a batch of up to 20.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 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).

60%

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: B+Signals: 4

13%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

60%

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: DSignals: 4

54%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

70%

OperationId Quality

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

60%

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.

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1

72%

Authentication Strength

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B+Signals: 1

68%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Maskbreak Fraud Detection API to your agent

Capabilities

Start building with Maskbreak Fraud Detection API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Maskbreak Fraud Detection API

Jentic AI Readiness Score

Maskbreak Fraud Detection API

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