TOLL

What software pays for, recorded every six hours.

Snapshot
2026-10-13 14:08 UTC
Sweep
daily-2026-10-21 · finished 2026-10-21 22:33 UTC
Listed
32,435

data place geocode derived

apiacre.comSearchderived

POST https://apiacre.com/v1/data/place-geocode

passlisted in Coinbase#27 by calls of 41 on this host

0.002 USDC

per call, as the listing declares it on eip155:8453

Compare with anotherEvery figure as JSONCite this page

the price, as of 2026-10-13 14:08 UTC · method · pinnable

Validation state
pass
as of 2026-10-21 09:04 UTC · method · pinnable · sweep daily-2026-10-21
Uptime, 7 / 30 / 90 days
100% / 100% / 100%
as of 2026-10-21 09:04 UTC · method · pinnable · 7 of 7 in 7d, 21 of 21 in 30d, 32 of 32 in 90d
Calls, trailing 30 days
1
as of 2026-10-13 14:08 UTC · method · pinnable
Unique payers, trailing 30 days
1
as of 2026-10-13 14:08 UTC · method · pinnable
Last called
2026-10-08 10:12 UTC
as of 2026-10-13 14:08 UTC · method · pinnable
First observed by TOLLderived
2026-09-10
as of 2026-09-10 19:08 UTC · method · pinnable · observation began 10 September 2026; listings that predate it show that date
Pricederived
0.002 USDC
as of 2026-10-13 14:08 UTC · method · pinnable · on eip155:8453
Networks
2
as of 2026-10-13 14:08 UTC · method · pinnable

Counters

101 observations, 2 of them a change, fewer than the 3 a trace needs

How big is this endpoint among the ones like it?

1 call100,000this endpoint
Calls counted in the trailing thirty days across the 2,591 endpoints in Search that carry counters, binned on a logarithmic scale because the range runs over five orders of magnitude. The marked bin is this endpoint, at 1: 1,889 in the category are counted higher and 701 lower.

No trace is drawn of this endpoint’s own volume. Its counters have changed 2 times across 101 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.

In words

Of apiacre.com's 41 listings, data place geocode ranks tied 27th by calls with 14 others.

data place geocode takes 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 a single call from a single payer in the trailing 30 days.

The last call to data place geocode came 5 days before the snapshot, 2026-10-08.

On Base, data place geocode asks 0.002 USDC per call.

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-10-21 with a valid 402, as at every sweep since 2026-09-11.

Closest in price to data place geocode within search: gift cards search at api.bitrefill.com and weather history at agent402.tools.

data place geocode is among the cheapest in search; 7% of comparable listings ask less.

The wallet paid by data place geocode is the payee of 74 endpoints on one host.

The seller's own tags are place-geocoding, geocode-place, city-to-coordinates and place-to-coordinates.

data place geocode dropped out of the registry at the pull of 2026-10-01 and was listed again on 2026-10-08.

The price of data place geocode is declared by 167 other listings in search too.

Payment options as declared

the payment options, as of 2026-10-13 14:08 UTC · method · pinnable

Every payment option declared on this listing
registrynetworkassetamountschemepay to
Coinbaseeip155:8453USDC0.002 USDCexact0xa0BFa4…24869B
Coinbasesolana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpUSDC0.002 USDCexactB4CHWQeQ…3HDLan

Preflight checks at the last sweep

the checks, as of 2026-10-21 09:04 UTC · method · pinnableendpoint answered HTTP 402

No named check failed.

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTCstatefailed checkssweep
2026-10-21 09:04 UTCpass0daily-2026-10-21
2026-10-20 09:16 UTCpass0daily-2026-10-20
2026-10-19 06:53 UTCpass0daily-2026-10-19
2026-10-18 09:02 UTCpass0daily-2026-10-18
2026-10-17 19:04 UTCpass0daily-2026-10-17
2026-10-16 05:15 UTCpass0daily-2026-10-16
2026-10-15 06:53 UTCpass0daily-2026-10-15
2026-10-14 05:10 UTCpass0daily-2026-10-14
2026-10-13 09:42 UTCpass0daily-2026-10-13
2026-10-12 07:06 UTCpass0daily-2026-10-12
2026-10-11 05:31 UTCpass0daily-2026-10-11
2026-10-10 13:48 UTCpass0daily-2026-10-10
2026-10-09 05:46 UTCpass0daily-2026-10-09
2026-10-08 13:35 UTCpass0daily-2026-10-08
2026-10-01 07:06 UTCpass0daily-2026-10-01
2026-09-30 06:23 UTCpass0daily-2026-09-30
2026-09-29 18:43 UTCpass0daily-2026-09-29
2026-09-28 04:34 UTCpass0daily-2026-09-28
2026-09-25 20:17 UTCpass0daily-2026-09-25
2026-09-23 05:56 UTCpass0daily-2026-09-23
2026-09-22 06:06 UTCpass0daily-2026-09-22
2026-09-21 06:29 UTCpass0daily-2026-09-21
2026-09-20 19:08 UTCpass0daily-2026-09-20
2026-09-19 04:30 UTCpass0daily-2026-09-19
2026-09-18 10:20 UTCpass0daily-2026-09-18
2026-09-17 04:27 UTCpass0daily-2026-09-17
2026-09-16 04:28 UTCpass0daily-2026-09-16
2026-09-15 04:26 UTCpass0daily-2026-09-15
2026-09-14 04:23 UTCpass0daily-2026-09-14
2026-09-13 04:22 UTCpass0daily-2026-09-13
2026-09-12 06:37 UTCpass0daily-2026-09-12
2026-09-11 10:08 UTCpass0daily-2026-09-11

Registry presence

Presence in a registry, not liveness of the service (method). Newest first.

  1. back in Coinbase
  2. absence from Coinbase confirmed, rule v1
  3. absent from Coinbase at this pull
  4. listed in Coinbase

Declared input and output, as listed

From the registry record, not validated by TOLL.the declared schema, as of 2026-10-08 10:12 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-10-13 14:08 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-10-13 14:08 UTC. https://tollindex.com/e/apiacre-com-v1-data-place-geocode-37a41e/at/2026-10-13T14-08Z. Accessed [access date].

BibTeX

@misc{toll-e-apiacre-com-v1-data-place-geocode-37a41e-2026-10-13T14-08Z,
  author = {TOLL},
  title = {data place geocode on apiacre.com},
  howpublished = {\url{https://tollindex.com/e/apiacre-com-v1-data-place-geocode-37a41e/at/2026-10-13T14-08Z}},
  year = {2026},
  month = {10},
  note = {Pinned view of the snapshot of 2026-10-13 14:08 UTC. Accessed [access date].}
}

Reports and replies about this endpoint

None yet. Anything submitted through the form below is published here with its outcome.

Report an error about data place geocode, or reply as the named seller

No account, no token. Published unedited with its outcome, upheld or not. Do not include personal data.

Kind

Published as typed. Optional.

10 to 4,000 characters.

Verify with the payee wallet (optional, EVM)

Sign this message with the wallet named on the page and paste the signature; it is checked, stored, never published. TOLL reply about endpoint 37a41e2a2de919596a0eda93bd85ddf03d83cc6b7dcfac3cdd931e30935e0c54 from wallet 0xa0BFa4f07281c9b248DC3AED2217836BcA24869B

The 0x address named as payee on this page, 42 characters.

The hex signature of the message above, starting 0x.