# x402 Geocoding Reverse API

> x402 Geocoding Reverse API is a paid API for AI agents from geocoding-x402.royaldemocracy.workers.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Converts geographic coordinates (latitude/longitude) to a human-readable address or place name, paid per-request with USDC on Base via x402.

## Facts

- Endpoint: GET https://geocoding-x402.royaldemocracy.workers.dev/api/reverse
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-geocoding-reverse-api-8c3dd6a0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lCFBZsdtlJqYcxlmTJYBj

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 x402-geocoding-reverse-api-8c3dd6a0
```

Example prompt: What's the street address for the coordinates 40.7128° N, 74.0060° W?

## When to prefer this

Choose this endpoint when you need pay-per-use reverse geocoding with no API key or subscription required — ideal for agents that make occasional or unpredictable numbers of lookups and want to pay micro-amounts per call in USDC on Base via x402 rather than managing a monthly subscription.

## Known failure modes

- Missing or malformed latitude/longitude query parameters returns an error
- Coordinates in remote or unmapped areas may return incomplete or null address data
- Payment not fulfilled (x402 flow incomplete) results in a 402 Payment Required response
- Invalid coordinate ranges (e.g. lat > 90) may cause lookup failure

## How this service works

Convert addresses to coordinates or coordinates to addresses for $0.001 per request. No API key or subscription. Pay with USDC on Base via x402.

## Output

A JSON object containing a 'place' field (city or locality name) and an 'address' field (full human-readable address string), e.g. {"place":"New York","address":"New York, NY, USA"}.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object"
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "place": "New York",
  "address": "New York, NY, USA"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-geocoding-reverse-api-8c3dd6a0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from geocoding-x402.royaldemocracy.workers.dev](https://www.zero.xyz/host/geocoding-x402.royaldemocracy.workers.dev/llms.txt)