passlisted in Coinbase#10 by calls of 74 on this host
0.002 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 2
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-09-01 12:52 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.002 USDC
- Networks
- 2
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 29 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
Among the 74 endpoints on apiacre.com, data reverse geocode is tied 10th by calls with 39 others.
data reverse geocode takes a json body with the fields limit, latitude, longitude and radius_km.
A response from data reverse geocode, as declared, includes data, meta, service, version and request_id.
One payer accounts for all 2 calls to data reverse geocode over 30 days.
Its last counted call came 14 days before the snapshot.
Per call, data reverse geocode declares 0.002 USDC on Base.
It accounts for 1% of the calls counted across the host.
For data reverse geocode the listing declares 2 accepts on Base and Solana, to 2 different wallets.
TOLL files data reverse geocode under search: a POST endpoint on apiacre.com, listed in the Coinbase registry.
data reverse geocode answered the sweep of 2026-09-15 with a valid 402, as at every sweep since 2026-09-11.
Closest in price to data reverse geocode within search: exa contents at stableenrich.dev and weather at x402.ottoai.services.
Among comparable prices in search, data reverse geocode sits above 10% of them.
The wallet paid by data reverse geocode is the payee of 74 endpoints on one host.
Seller tags: reverse-geocoding, coordinates-to-place, coordinates-to-city and nearest-city.
The price of data reverse geocode is declared by 113 other listings in search too.
the payment options, as of 2026-09-15 21:20 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.002 USDC | exact | 0xa0BFa4…24869B |
| Coinbase | solana: | USDC | 0.002 USDC | exact | B4CHWQeQ…3HDLan |
the checks, as of 2026-09-15 05:29 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-15 05:29 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 05:03 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 04:59 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 07:16 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 10:56 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-09-01 12:52 UTC · method · live
The input and output block
{
"input": {
"body": {
"limit": 3,
"latitude": 51.5074,
"longitude": -0.1278,
"radius_km": 10
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"data": {
"query": {
"limit": 3,
"latitude": 51.5074,
"radiusKm": 10,
"longitude": -0.1278
},
"source": {
"dataset": "GeoNames cities500",
"provider": "GeoNames",
"aliasRecords": 766415,
"placeRecords": 235408,
"snapshotBuiltOn": "2026-08-18"
},
"matched": true,
"results": [
{
"name": "London",
"rank": 1,
"admin1": {
"code": "ENG",
"name": "England"
},
"country": {
"code": "GB",
"iso3": "GBR",
"name": "United Kingdom",
"continentCode": "EU"
},
"geonameId": 2643743
}
],
"version": "apiacre-reverse-geocode/1",
"limitations": [
"Coverage follows the GeoNames cities500 extract: populated places above 500 r...",
"This endpoint returns nearby populated places, not street addresses, parcels,...",
"The nearest populated place is not proof of the queried coordinate's postal a...",
"Distances are rounded great-circle distances between coordinates and place ce...",
"The search radius is capped at 500 km and results use the bundled 2026-08-18 ..."
],
"candidateCount": 99,
"resultsTruncated": true
},
"meta": {
"cached": false,
"sources": [],
"warnings": [],
"duration_ms": 42,
"next_actions": [
{
"path": "/v1/data/us-weather-forecast",
"title": "Global weather forecast",
"method": "POST",
"reason": "Use the queried coordinates for a separately authorized current global forecast.",
"service": "data.us-weather-forecast"
}
]
},
"service": "data.reverse-geocode",
"version": "1",
"request_id": "018f1f54-7f38-7ba2-8dc3-5f90272d9f1a"
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-15 21:20 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "data reverse geocode on apiacre.com", snapshot of 2026-09-15 21:20 UTC. https://tollindex.com/e/apiacre-com-v1-data-reverse-geocode-71f443/at/2026-09-15T21-20Z. Accessed [access date].
BibTeX
@misc{toll-e-apiacre-com-v1-data-reverse-geocode-71f443-2026-09-15T21-20Z,
author = {TOLL},
title = {data reverse geocode on apiacre.com},
howpublished = {\url{https://tollindex.com/e/apiacre-com-v1-data-reverse-geocode-71f443/at/2026-09-15T21-20Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-15 21:20 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.