# QuantaFlow x402 API Gateway – RapidAPI WFT GeoDB Proxy

> QuantaFlow x402 API Gateway – RapidAPI WFT GeoDB Proxy 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-10).

Proxies requests to the RapidAPI WFT GeoDB geographic database service via x402 micropayment protocol, enabling pay-per-call access to city, region, and country geolocation data.

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/rapid-wft-geo-db?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-x402-api-gateway-rapidapi-wft-geodb-proxy-fb3b87e2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4k3yVF9-eYJk_3W-PrTij

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-x402-api-gateway-rapidapi-wft-geodb-proxy-fb3b87e2 -d '<json body>'
```

Example prompt: Look up all cities in Germany with a population over 500,000 and return their names, coordinates, and timezones.

## When to prefer this

Choose this endpoint when you need pay-per-call, no-subscription access to the WFT GeoDB geographic database through an x402 micropayment flow — ideal for agents that query location data infrequently and want to avoid monthly API subscriptions, or for web3-native workflows where on-chain micropayments are preferred over traditional API keys.

## Known failure modes

- Payment failure if USDC balance is insufficient or x402 handshake fails
- Upstream RapidAPI rate limit exceeded returns 429
- Invalid path or query parameters return 400 or empty results from upstream
- Upstream GeoDB service downtime returns 502 or 503
- Malformed JSON body causes request forwarding failure

## How this service works

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

## Output

The raw upstream GeoDB API response is passed through — typically JSON containing city or region records with fields like city name, country code, region, population, latitude, longitude, and timezone, depending on the path and query parameters supplied.

## 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-x402-api-gateway-rapidapi-wft-geodb-proxy-fb3b87e2/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)