# APISphere Geocoding API

> APISphere Geocoding API is a paid API for AI agents from apisphere.us.ci, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-10).

Converts a free-text address or place name query into geographic coordinates (latitude/longitude) with display name results

## Facts

- Endpoint: POST https://apisphere.us.ci/api/v1/geocode?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apisphere-geocoding-api-33f33ce2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MdJqfo5JrXeydfgvXo2mF

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 apisphere-geocoding-api-33f33ce2 -d '<json body>'
```

Example prompt: Can you geocode '1600 Pennsylvania Avenue NW, Washington, DC' and give me the latitude and longitude — return up to 3 results?

## When to prefer this

Choose this endpoint when your agent needs to resolve a free-text address or place name into latitude/longitude coordinates without requiring API key provisioning or account signup. Ideal for AI agent workflows that need frictionless, pay-per-call geocoding billed in USDC on Base. Prefer this over traditional geocoding APIs when operating in a crypto-native or x402-payment environment.

## Known failure modes

- No results found for ambiguous or misspelled query — empty results array returned
- Required 'query' field missing — request validation error
- Unrecognized location string yields zero or low-confidence results
- Payment failure via x402/USDC may block request before geocoding occurs
- Rate or limit parameter exceeds allowable range

## How this service works

Pay-per-call APIs for AI agents. No signup, no API keys — agents pay in USDC on Base via x402. Live endpoints for crypto prices and geocoding.

## Output

Returns an array of geocoding results, each containing latitude, longitude, a human-readable display name, place type, and an importance score. Also includes optional metadata such as cache status, timestamp, and request ID.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "query"
 ],
 "properties": {
  "limit": {
   "type": "integer"
  },
  "query": {
   "type": "string"
  },
  "address": {
   "type": "string",
   "description": "Alias for query."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "results"
 ],
 "properties": {
  "meta": {
   "type": "object",
   "properties": {
    "cache": {
     "type": "string"
    },
    "timestamp": {
     "type": "string"
    },
    "request_id": {
     "type": "string"
    }
   }
  },
  "results": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "latitude",
     "longitude",
     "displayName"
    ],
    "properties": {
     "type": {
      "type": "string"
     },
     "query": {
      "type": "string"
     },
     "latitude": {
      "type": "number"
     },
     "longitude": {
      "type": "number"
     },
     "importance": {
      "type": "number"
     },
     "displayName": {
      "type": "string"
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/apisphere-geocoding-api-33f33ce2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from apisphere.us.ci](https://www.zero.xyz/host/apisphere.us.ci/llms.txt)