Fraudlogix Bot & Fraud API
Official vendor OpenAPI document · agent-readySecurityThreat DetectionapiKey1 EndpointsREST
For Agents
Look up an IP address and get back bot, proxy, VPN, and fraud risk signals plus a recommended verdict. Authentication is the x-api-key header.
Use for: I need to check whether this IP is a bot or proxy, Look up the fraud risk for an incoming visitor's IP, Check whether the visitor IP is a known VPN or data centre, Find the country and ASN of an IP address
Not supported: Does not handle device fingerprinting, transaction-level fraud scoring, or chargeback prevention - use for IP-level bot, proxy, VPN, and fraud risk lookups only.
Fraudlogix is an IP risk intelligence service used by ad-tech platforms, lead-gen networks, and online merchants to detect bots, fraudulent traffic, proxies, VPNs, and other malicious activity at the IP layer. The version 5 API exposes a single GET /v5 endpoint that takes an IP address (and optionally a user agent) and returns a structured risk assessment including bot classification, proxy and VPN flags, geolocation, and an overall fraud verdict.
Install Jentic One Beta
Connect the Fraudlogix Bot & Fraud API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Fraudlogix Bot & Fraud 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.
1
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%2Ffraudlogix.com%2Ffraudlogix" | sh2
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%2Ffraudlogix.com%2Ffraudlogix" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Fraudlogix Bot & Fraud API.
Look up an IP address against Fraudlogix's threat database via GET /v5
Receive bot classification, proxy detection, and VPN flags for a given IP
Get geolocation data (country, region, city, ASN) alongside the risk signals
Detect data-centre and hosting-provider IPs that indicate non-human traffic
Return a single overall verdict that ad-tech and merchants can branch on
Use Cases
Patterns agents use Fraudlogix Bot & Fraud API for, with concrete tasks.
★ Ad-Tech Bot Filtering
Programmatic ad platforms call Fraudlogix on every impression or click to filter out bot traffic before billing the advertiser. The single /v5 lookup returns bot classification and proxy flags in milliseconds, letting the platform serve only verified human traffic and reduce invalid-traffic refund disputes.
GET /v5?ip={ip}&useragent={ua} on each impression and drop the impression if the response classifies the IP as a bot
Lead Validation
A lead-generation network filters incoming leads by checking the submitting IP against Fraudlogix. Leads from data centres, residential proxies, or known fraud IPs are quarantined before being sold to advertisers, protecting both the network's reputation and its buyers.
GET /v5 with the lead form submitter's IP and quarantine the lead if the response indicates proxy or data centre origin
Login and Checkout IP Risk Check
An e-commerce site calls Fraudlogix at login and checkout to flag sessions coming from VPNs, residential proxies, or known fraud IPs. The single-call API fits comfortably in a request hook without adding meaningful latency, and the verdict feeds into a broader fraud score alongside other signals.
GET /v5 with the session IP at login and add a risk multiplier to the fraud score if the response flags VPN or proxy
AI Agent Traffic Triage
An agent monitoring web logs uses Jentic to call Fraudlogix on suspicious IPs, summarising the bot, proxy, and VPN signals back to the operator. The x-api-key is held in Jentic's vault and the agent only deals with structured verdicts.
Search Jentic for 'check whether this IP is a bot', execute GET /v5 for each suspicious IP, and post a one-line summary back to the security channel
Key Endpoints
1 endpoints — fraudlogix is an ip risk intelligence service used by ad-tech platforms, lead-gen networks, and online merchants to detect bots, fraudulent traffic, proxies, vpns, and other malicious activity at the ip layer.
METHOD
PATH
DESCRIPTION
GET
/v5
Look up an IP address for bot, proxy, VPN, and fraud signals
GET
/v5
Look up an IP address for bot, proxy, VPN, and fraud signals
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Fraudlogix Bot & Fraud API by hand means setting its x-api-key header on each request and building your own retry and error handling around the single IP-lookup endpoint. Through Jentic you install once, import Fraudlogix from the API Directory, store the key once, and your agent calls it.
Permission scoping
Fraudlogix carries the IP address as a query parameter rather than a URL path resource, so scoping is operations-only: this API exposes one lookup operation, and you grant the agent that read-only IP check and nothing more. The operation the agent can run is the one you chose.
Credential isolation
Your Fraudlogix x-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 'check whether this IP is a bot', and Jentic returns the matching Fraudlogix operation with its input schema so the agent does not need to construct query strings by hand.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Fraudlogix Bot & Fraud API through Jentic.
What authentication does the Fraudlogix API use?
Fraudlogix takes an API key in the x-api-key header on every request. Through Jentic, the key is stored encrypted in the vault and replaced with a scoped execution token before the agent runs.
Can I detect bots and proxies with the Fraudlogix API?
Yes. GET /v5 with an IP (and optionally a user agent) returns bot classification, proxy and VPN flags, data-centre and hosting-provider detection, plus geolocation and ASN. A single response is enough to decide whether to block, throttle, or trust the visitor.
What are the rate limits for the Fraudlogix API?
Fraudlogix applies plan-level quotas rather than published per-second limits, with per-month lookup allowances scaled to the customer's traffic volume. Enterprise customers negotiate higher throughput as part of the contract.
How do I check an IP through Jentic?
Search Jentic for 'check whether this IP is a bot', load the GET /v5 schema, and execute it with the ip parameter. The response carries the verdict and underlying signals as JSON, so the agent can branch on the bot or proxy fields without parsing free text.
Is the Fraudlogix API free?
Fraudlogix offers a trial with a limited monthly lookup quota, then paid plans that scale by lookup volume. There is no perpetual free tier suitable for production traffic.
How do I tell whether an IP is from a data centre?
The /v5 response includes a hosting-provider flag and ASN information that identify data-centre and cloud origins. Treat data-centre IPs as non-human for ad-tech and lead-gen workflows, and as elevated risk for consumer-facing checkout and login flows.
Can I limit what my agent is allowed to do with the Fraudlogix API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. The Fraudlogix API exposes a single read-only lookup, GET /v5, which takes an IP address, so you can grant your agent that one IP risk check and nothing else. Your x-api-key is stored by your own instance and injected only when that lookup runs, so the agent never sees the key or gains access to any other operation.
GET STARTED