# OnchainExpat Reverse Geocode API

> OnchainExpat Reverse Geocode API is a paid API for AI agents from x402.onchainexpat.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).

Converts geographic coordinates (latitude/longitude) into a human-readable address or location name via a pay-per-request x402 endpoint

## Facts

- Endpoint: POST https://x402.onchainexpat.com/api/x402-tools/reverse-geocode
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/onchainexpat-reverse-geocode-api-40b6a79d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OmbwxYMOvMCKXm6jpg1FR

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 onchainexpat-reverse-geocode-api-40b6a79d -d '<json body>'
```

Example prompt: Can you reverse geocode these coordinates for me — latitude 48.8566, longitude 2.3522 — and tell me the full address or place name?

## When to prefer this

Choose this endpoint when you need a pay-per-use, crypto-native reverse geocoding solution that accepts USDC micropayments via the x402 protocol, avoiding the need for API key management or subscription plans. Suitable for agents that already operate in a Web3 or x402 payment context.

## Known failure modes

- Invalid or out-of-range coordinates return an error
- Missing latitude or longitude in request body
- Payment not provided or x402 payment rejected — returns 402 Payment Required
- Coordinates in remote or unmapped areas may return sparse or no address data
- Network timeout or upstream geocoding service unavailability

## How this service works

Pay-per-request AI, crypto, proxy, and utility APIs using x402 protocol

## Output

A JSON object containing the human-readable address components derived from the input coordinates, such as street name, city, region, postal code, and country.

## Example request

```json
{
 "latitude": 48.8566,
 "longitude": 2.3522
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "latitude",
  "longitude"
 ],
 "properties": {
  "latitude": {
   "type": "number",
   "description": "Latitude in decimal degrees. Alias: 'lat'"
  },
  "longitude": {
   "type": "number",
   "description": "Longitude in decimal degrees. Alias: 'lon'"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "cached": {
   "type": "boolean"
  },
  "address": {
   "type": "object"
  },
  "latitude": {
   "type": "number"
  },
  "longitude": {
   "type": "number"
  },
  "display_name": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onchainexpat-reverse-geocode-api-40b6a79d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.onchainexpat.com](https://www.zero.xyz/host/x402.onchainexpat.com/llms.txt)