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.
Of apiacre.com's 74 listings, data place geocode ranks tied 10th by calls with 39 others.
Callers of data place geocode supply a json body with the fields limit and place.
A response from data place geocode, as declared, includes data, meta, service, version and request_id.
data place geocode drew 2 calls from one payer in the trailing 30 days.
The last call to data place geocode came 14 days before the snapshot, 2026-09-01.
The declared price is 0.002 USDC on Base.
data place geocode takes 1% of the calls counted across apiacre.com.
2 payment options span Base and Solana, to 2 different wallets.
data place geocode, a POST endpoint on apiacre.com, appears in the Coinbase registry; TOLL's taxonomy puts it in search.
data place 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 place geocode within search: geocode reverse at api.agentstools.dev and gift cards search at api.bitrefill.com.
data place geocode is priced above 10% of comparable listings in search.
Its payee wallet receives for 74 listed endpoints on one host.
The seller's tags on data place geocode are place-geocoding, geocode-place, city-to-coordinates and place-to-coordinates.
The price of data place 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 04:26 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 04:26 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 04:23 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 04:22 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 06:37 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 10:08 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": 5,
"place": "London, GB"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"data": {
"query": {
"limit": 5,
"place": "London, GB",
"normalized": "london, gb"
},
"source": {
"dataset": "GeoNames cities500",
"provider": "GeoNames",
"aliasRecords": 766415,
"placeRecords": 235408,
"snapshotBuiltOn": "2026-08-18"
},
"results": [
{
"name": "London",
"rank": 1,
"country": {
"code": "GB",
"iso3": "GBR",
"name": "United Kingdom",
"continentCode": "EU"
},
"geonameId": 2643743,
"matchedNameType": "primary"
}
],
"version": "apiacre-place-geocode/1",
"ambiguous": true,
"limitations": [
"Coverage follows the GeoNames cities500 extract: populated places above 500 r...",
"Matching is exact after Unicode-to-ASCII normalization; this endpoint does no...",
"Unqualified names can be ambiguous. Review country, first-level region, GeoNa...",
"Population-based ranking is a selection aid, not proof that the first candida...",
"Results use the bundled 2026-08-18 snapshot and can differ from newer GeoName..."
],
"candidateCount": 2,
"resultsTruncated": false,
"candidateCountCapped": false
},
"meta": {
"cached": false,
"sources": [],
"warnings": [],
"duration_ms": 42,
"next_actions": [
{
"path": "/v1/data/us-weather-forecast",
"title": "Global weather forecast",
"method": "POST",
"reason": "Use one selected place candidate's coordinates for a separately authorized cu...",
"service": "data.us-weather-forecast"
}
]
},
"service": "data.place-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 place geocode on apiacre.com", snapshot of 2026-09-15 21:20 UTC. https://tollindex.com/e/apiacre-com-v1-data-place-geocode-37a41e/at/2026-09-15T21-20Z. Accessed [access date].
BibTeX
@misc{toll-e-apiacre-com-v1-data-place-geocode-37a41e-2026-09-15T21-20Z,
author = {TOLL},
title = {data place geocode on apiacre.com},
howpublished = {\url{https://tollindex.com/e/apiacre-com-v1-data-place-geocode-37a41e/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.