IP Geolocation and VPN Proxy Risk Detection

# IP Geolocation and VPN Proxy Risk Detection Look up public IPv4 and IPv6 addresses for geolocation, ASN and network organization data. Evaluate separate VPN, proxy, Tor, mobile and datacenter signals, plus a 0–100 risk score that combines provider intelligence with hosting and bot heuristics. ## When to use it - Add IP network context to signup, login and checkout reviews. - Enrich security events with geography, ASN and hosting indicators. - Give an AI assistant a structured IP lookup tool for reviewing network signals. The score supports investigation; it does not prove fraud, identify a person or justify automatically rejecting a customer. ## Choose an endpoint | Endpoint | Input | Result | | --- | --- | --- | | `GET /ip-lookup` | `ip`: public IPv4 or IPv6 | Geolocation, timezone, ASN and network organization. | | `GET /fraud-check` | `ip`: public IPv4 or IPv6 | VPN, proxy, Tor, mobile and hosting signals with a risk assessment. | | `GET /health` | None | Service status and timestamp. | For a specific customer or event, pass the trusted public IP explicitly, for example `/fraud-check?ip=8.8.8.8`. Do not rely on an omitted `ip` to discover an end user hidden behind your application server or marketplace gateway. URL-encode IPv6 query values. ## Authentication and quick start Choose a plan on this listing and use the gateway URL from the endpoint playground with `X-JoJAPI-Key: YOUR_JOJ_API_KEY`. Keep the key on your server. Open the endpoint, enter a public IP, and inspect the documented JSON response before integrating the result. Current prices, quotas and billing rules are shown on the listing. Functional successes use `{ "success": true, "data": { ... }, "error": null }`. Application errors use `{ "success": false, "data": null, "error": { "code": "...", "message": "..." } }`. Health has a smaller response. Gateway authentication, quota and subscription errors may use a different envelope. ## Use with AI agents through MCP Connect an HTTP-compatible MCP client to `https://mcp.jojapi.com/fraudguard-and-ip-risk-intelligence-api`. Set `Authorization: Bearer YOUR_JOJ_API_KEY` as a connection header. The marketplace exposes the documented endpoints as tools; use the **MCP server** and **OpenAPI spec** links on this listing for the current contract. Pass the IP explicitly, choose lookup for network context or fraud-check for risk signals, and preserve individual flags when summarizing results. Tool calls use the same gateway, subscription and quotas as ordinary HTTP requests. ## Accuracy and limits Geolocation and network signals depend on upstream provider coverage and can be incomplete or outdated. VPN, proxy and hosting classifications can produce false positives and false negatives. A public resolver, shared NAT, cloud host or privacy service is not evidence of wrongdoing. A low score does not guarantee safety. Private and reserved IP addresses are not supported. Correct invalid input instead of retrying it. For temporary upstream failures, use bounded retries with backoff. A healthy service does not guarantee upstream data availability for every address.