New Intelligence APIs now available

Starting today the new CaptchaFox Intelligence APIs are available on the CaptchaFox platform.

They let you evaluate requests before they reach your application and get more context about incoming traffic, for example during signups, logins, or other sensitive actions. The Intelligence APIs are available starting with the Team plan.

Since 2025, we've been providing extended risk details to Enterprise customers through the insights field of the CAPTCHA verification response. With the Intelligence APIs, we're now opening up those signals as standalone endpoints that you can query independently of a CAPTCHA verification.

The first one to land is IP Risk Intelligence.

What's New?

IP Risk Intelligence helps you understand whether a request is coming from a regular user or from traffic such as a proxy, VPN, Tor exit node, hosting provider, residential proxy, or known bot traffic.

A single request returns:

• Classification and risk assessment with a numeric score (0–100) and risk level
• Network and location data including ASN, organization, country, city, and timezone
• Proxy detection for datacenter, VPN, Tor, and residential proxy traffic with confidence and provider
• Bot detection for known crawlers and AI tools
• Boolean signals for quick rule evaluation

Use cases

Protect signups and logins. Account takeover and credential stuffing attacks today almost always run through proxy infrastructure. IP Risk Intelligence tells you whether a login attempt comes from a residential proxy, VPN, or Tor IP, so you can respond with email confirmation, a one-time code, or an additional CAPTCHA challenge. On signups, the same signal prevents large-scale fake account creation without blocking legitimate users.

Apply stricter rules to VPN and proxy traffic. Not all proxy traffic is malicious. Many users work behind corporate VPNs or protect their privacy. Instead of blocking this traffic outright, allow the login itself but require step-up verification for sensitive actions, like changing the email address, adding a payment method, withdrawing funds, or rotating API keys.

Categorize bots and crawlers. Not all bots are equal. You may want to allow search crawlers on public pages, gate AI training crawlers to specific content, and block automated scripts entirely from checkout, login, or password reset flows. The bot classification gives you the provider and category to enforce those rules without accidentally locking out legitimate crawlers.

Add friction only when needed. Every extra verification step costs conversion. With the risk score and boolean signals, you can build adaptive UX: clean IPs go straight through, medium risk gets a light challenge, and high risk is verified harder or blocked. Instead of picking one threshold that applies to all users, you react to the actual risk profile of each request.

Prevent abuse in your own workflows. Beyond login and signup, the signals are useful anywhere automated or anonymized traffic can cause damage: coupon redemptions, trial activations, comments, reviews, form submissions, or API calls.

Example request

1curl https://api.captchafox.com/v1/intelligence/ip-risk/check \
2  -X POST \
3  -H "Authorization: Bearer YOUR_API_KEY" \
4  -H "Content-Type: application/json" \
5  -d '{"ip":"198.51.100.24"}'

Example response

1{
2  "classification": "residential_proxy",
3  "risk_level": "critical",
4  "risk_score": 86,
5  "ip": "198.51.100.24",
6  "version": 4,
7  "network": {
8    "asn": 14061,
9    "organization": "DigitalOcean, LLC",
10    "type": "hosting",
11    "mobile": false
12  },
13  "location": {
14    "country_code": "DE",
15    "country": "Germany",
16    "state": "Hesse",
17    "city": "Frankfurt",
18    "timezone": "Europe/Berlin"
19  },
20  "proxy": {
21    "confidence": "high",
22    "type": "residential",
23    "provider": "Bright Data",
24    "last_seen_at": "2025-01-10",
25    "percent_days_seen": 100
26  },
27  "signals": {
28    "proxy": true,
29    "vpn": false,
30    "tor": false,
31    "hosting": true,
32    "residential_proxy": true,
33    "blocklist_match": false
34  }
35}

Getting Started

Create an API key in the CaptchaFox Portal under Settings → Keys → API Keys and send it as a bearer token with each request. The full reference with all fields, classifications, and error codes is in the Intelligence APIs documentation.