# QuantaFlow IP Geolocation API (rapid-geobyip)

> QuantaFlow IP Geolocation API (rapid-geobyip) is a paid API for AI agents from quanta-roan.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-20).

Geolocates an IP address, returning geographic location data such as country, city, region, and coordinates via a pay-per-call x402 gateway.

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/rapid-geobyip-fast-ip-geolocation-api?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-ip-geolocation-api-rapid-geobyip-3bbdd7fa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Mt7kdjojLDk4e8W-b8QTn

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability quantaflow-ip-geolocation-api-rapid-geobyip-3bbdd7fa -d '<json body>'
```

Example prompt: Look up the geographic location of IP address 203.0.113.42 — I need the country, city, region, and coordinates.

## When to prefer this

Choose this endpoint when you need fast, per-call IP geolocation billed via x402/USDC micropayments without a subscription, especially in web3-native or agent-driven workflows. It is a good fit when you want pay-as-you-go pricing at $0.01 per lookup and can integrate with the x402 payment protocol. Prefer alternatives if you need bulk batch geolocation, guaranteed SLAs, or prefer traditional API key authentication.

## Known failure modes

- Invalid or private/reserved IP address returns an error or empty location data
- Malformed query parameters result in upstream rejection
- Payment failure via x402 protocol blocks the request before it reaches the upstream
- Upstream rapid-geobyip service unavailable causes a gateway timeout or 502 error
- Rate limits on the upstream API may cause throttling responses

## How this service works

Every request, a quantum of value. x402 protocol-based payment endpoint for web3/DeFi tools.

## Output

Returns the upstream geolocation response for the queried IP, including fields such as country, country code, city, region, latitude, longitude, timezone, ISP, and ASN, passed through directly from the rapid-geobyip upstream service.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "body": {
   "type": "string",
   "description": "Optional JSON body forwarded to POST requests."
  },
  "path": {
   "type": "string",
   "description": "Path below the selected upstream origin."
  },
  "query": {
   "type": "object"
  },
  "method": {
   "enum": [
    "GET",
    "POST"
   ],
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "description": "The upstream response body and content type are passed through after successful payment."
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quantaflow-ip-geolocation-api-rapid-geobyip-3bbdd7fa/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from quanta-roan.vercel.app](https://www.zero.xyz/host/quanta-roan.vercel.app/llms.txt)
