# Compare x402 geocoding and location APIs

x402 endpoints that turn an address into coordinates, coordinates into a place, or a point into a timezone — compared on price per call, with explicit gaps where we have not looked yet.

> These are observations, not accusations. A band of LOW, MEDIUM or HIGH describes how much of
> what we check we were able to confirm — it is not a judgement about the operator of an
> endpoint. Every signal, its weight and its rationale are published at /methodology, and any
> operator can claim an endpoint, correct a fact or opt out at /crawler.

| Endpoint                       | Price per call | Network        | Asset          | Pays to                                    | Observed signals            | Watched for          | Terms last observed  |
| ------------------------------ | -------------- | -------------- | -------------- | ------------------------------------------ | --------------------------- | -------------------- | -------------------- |
| Places & Local Business Search | 0.020000 USDC  | eip155:8453    | USDC           | 0x59ea036C64f0F54CDD14a3BE8a1a6586B58DA71c | 96/100 LOW (methodology v1) | under a day, 1 probe | 2026-08-15T05:30:46Z |
| Satellite & GeoRisk x402 API   | — not observed | — not observed | — not observed | — not observed                             | — not observed              | under a day, 1 probe | 2026-08-15T06:00:42Z |
| Timezone Converter             | 0.001000 USDC  | eip155:8453    | USDC           | 0xbA667287B8Ef89565F8fD7AcD4d22Ce98E0f39cd | 96/100 LOW (methodology v1) | under a day, 1 probe | 2026-08-15T04:30:24Z |
| Wallets Demo Weather           | 0.001000 USDC  | eip155:84532   | USDC           | 0xCBd4E4218B2Cd8300f1bd07b9B4B720fAb6B51B3 | 96/100 LOW (methodology v1) | under a day, 1 probe | 2026-08-15T05:45:20Z |
| WebberSites x402 Data API      | 0.001000 USDC  | eip155:8453    | USDC           | 0xdd5fcEa81CA6f1EB39FEd5B973DE794293B81ba6 | 96/100 LOW (methodology v1) | under a day, 1 probe | 2026-08-15T05:00:45Z |

**Not ranked by price.** These endpoints price in different assets, networks or decimal precisions, so their amounts are not one scale and are not ranked against each other.

## What the facilitator claims

These figures are published by the facilitator that lists the endpoint. They are not our
observations, and they are shown separately from them for that reason. An advertised price and
the price the endpoint actually served us are two different facts, and a disagreement between
them is a finding rather than an error.

| Endpoint                       | Listed by    | Usage (30d)          | Unique payers (30d) | Advertised price |
| ------------------------------ | ------------ | -------------------- | ------------------- | ---------------- |
| Places & Local Business Search | coinbase-cdp | 5 calls in 30 days   | 5 unique payers     | 20000 atomic     |
| Satellite & GeoRisk x402 API   | coinbase-cdp | 4 calls in 30 days   | 4 unique payers     | 2000 atomic      |
| Timezone Converter             | coinbase-cdp | 270 calls in 30 days | 71 unique payers    | 1000 atomic      |
| Wallets Demo Weather           | coinbase-cdp | 13 calls in 30 days  | 4 unique payers     | 1000 atomic      |
| WebberSites x402 Data API      | coinbase-cdp | 11 calls in 30 days  | 9 unique payers     | 1000 atomic      |

## What this table does and does not say

- These endpoints price in different assets, networks or decimal precisions, so their amounts are not one scale and are not ranked against each other.
- Availability and latency are not shown here. They are aggregates over the sampled probe dataset and are read one endpoint at a time, which is what the history page does — this page reads the index and makes no outbound request. Estimating them from the probe records kept in the database instead would over-report failure, because routine successful probes are deliberately not kept.
- Usage figures on this page are published by the facilitator that lists the endpoint (coinbase-cdp), not measured by us. They are shown because they are better data than anything we can collect — and attributed because they are somebody else's.

---

JSON: `/api/v1/compare?category=geocoding` · full per-endpoint records: `/api/v1/endpoints` · categories: `/api/v1/categories`

Every figure here is something we observed by asking the endpoint, except where it is labelled as
a facilitator's claim. Nothing on this page is a statement about an operator.