timezone derived

api.geoprimitives.devInference derived

GET https://api.geoprimitives.dev/v1/timezone

passlisted in Coinbase#2 by calls of 21 on this host

0.005 USDC

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

Compare with another Every figure as JSON Cite this page

the price, as of 2026-09-15 21:20 UTC · method · pinnable

Validation state: pass; as of 2026-09-15 05:00 UTC · method · pinnable · sweep daily-2026-09-15
Uptime, 7 / 30 / 90 days: 100% / 100% / 100%; as of 2026-09-15 05:00 UTC · method · pinnable · 5 of 5 in 7d, 5 of 5 in 30d, 5 of 5 in 90d
Calls, trailing 30 days: 6; as of 2026-09-15 21:20 UTC · method · pinnable
Unique payers, trailing 30 days: 3; as of 2026-09-15 21:20 UTC · method · pinnable
Last called: 2026-09-14 19:51 UTC; as of 2026-09-15 21:20 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.005 USDC; as of 2026-09-15 21:20 UTC · method · pinnable · on eip155:8453
Networks: 1; as of 2026-09-15 21:20 UTC · method · pinnable

Counters

29 observations, 3 of them a change

How has the volume on this endpoint moved?

Calls counted in the trailing 30 days on this endpoint, at every snapshot since 2026-09-10. Each point is a trailing-30-day sum as the registry published it, not a daily rate. The axis is truncated to the range of the data with a break at its foot.

In words

Of api.geoprimitives.dev's 21 listings, timezone ranks 2nd by calls.

timezone takes the query parameters at, lat and lon.

A response from timezone, as declared, includes at, cell, isDST, notes, query, source and 2 others.

timezone drew 6 calls from 3 unique payers in the trailing 30 days.

The last call to timezone came 1 day before the snapshot, 2026-09-14.

Per call, timezone declares 0.005 USDC on Base.

At api.geoprimitives.dev, timezone takes GET requests, is listed in the Coinbase registry, and falls under inference by TOLL's rules.

timezone answered the sweep of 2026-09-15 with a valid 402, as at every sweep since 2026-09-11.

Closest in price to timezone within inference: chat completions at x402.orthogonal.com and agent record rubric assert at rubric-protocol.com.

timezone is priced above 17% of comparable listings in inference.

Within inference, 89% of endpoints with counters have fewer calls.

The wallet paid by timezone is the payee of 21 endpoints on one host.

Seller tags: timezone, iana, dst and utc-offset.

The price of timezone is declared by 148 other listings in inference too.

Payment options as declared

the payment options, as of 2026-09-15 21:20 UTC · method · pinnable

Every payment option declared on this listing
registry	network	asset	amount	scheme	pay to
Coinbase	eip155:8453	USDC	0.005 USDC	exact	0x76A51b…968FCe

Preflight checks at the last sweep

the checks, as of 2026-09-15 05:00 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, UTC	state	sweep
2026-09-15 05:00 UTC	pass	daily-2026-09-15
2026-09-14 04:52 UTC	pass	daily-2026-09-14
2026-09-13 04:51 UTC	pass	daily-2026-09-13
2026-09-12 07:06 UTC	pass	daily-2026-09-12
2026-09-11 10:45 UTC	pass	daily-2026-09-11

Registry presence

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

2026-09-10 19:08 UTClisted in Coinbase

Declared input and output, as listed

From the registry record, not validated by TOLL.the declared schema, as of 2026-09-14 19:51 UTC · method · live

The input and output block

{
  "input": {
    "type": "http",
    "method": "GET",
    "queryParams": {
      "at": "2026-07-04T16:00:00Z",
      "lat": 40.7128,
      "lon": -74.006
    }
  },
  "output": {
    "type": "json",
    "example": {
      "at": "2026-07-04T16:00:00.000Z",
      "cell": "862a1072fffffff",
      "isDST": true,
      "notes": [],
      "query": {
        "lat": 40.7128,
        "lon": -74.006
      },
      "source": "boundary",
      "timezone": "America/New_York",
      "localTime": "2026-07-04T12:00:00-04:00",
      "utcOffset": "-04:00",
      "boundaries": {
        "dataset": "tz_world_mp",
        "license": "CC0-1.0",
        "tzdbVintage": "2016d",
        "h3Resolution": 6,
        "accuracyMetres": 1600
      },
      "abbreviation": "EDT",
      "dstOffsetMinutes": 60,
      "utcOffsetMinutes": -240,
      "standardUtcOffset": "-05:00",
      "standardUtcOffsetMinutes": -300
    }
  }
}

What the listing says

Give it a longitude and latitude and it answers with the IANA timezone identifier (America/New_York), the UTC offset in force there right now, whether daylight saving is currently in effect and by how much, the local wall-clock time, and the zone's standard offset. Pass an optional ISO 8601 `at` instant to ask about any moment between 1900 and 2100 instead of now, which is what you want when scheduling something months out across a DST boundary. Parameters go in the query string: this is a GET, there is no body. Two halves, with different vintages, and the difference matters. The offset and the DST rules come from the runtime's own timezone database and are current: a rule change reaches this endpoint when Cloudflare updates ICU, with no redeploy here. The *boundaries* come from tz_world (efele.net), CC0 1.0 and derived from VMAP0, a public-domain US government product. That map was frozen at tzdb 2016d in May 2016, and this catalog sells public-domain and permissively-licensed data only, which is why it is used rather than the current OpenStreetMap-derived alternative. What the vintage costs, measured against IANA's own coordinates for all 312 zones in zone1970.tab rather than estimated: 293 agree. Of the 19 that do not, 7 are Antarctic research stations, which this map does not cover at all and which fall back to the open-water rule; 7 more return a different identifier for the identical offset and DST all year (Australia/Brisbane for Australia/Lindeman, America/Regina for America/Swift_Current, and five like them), so the time is right and only the name is old. That leaves four regions where the answer is up to one hour wrong because the zone was split after 2016: Chilean Magallanes and Aysen (answered as America/Santiago rather than America/Punta_Arenas or America/Coyhaique), the Mexican border municipalities around Ciudad Juarez, Saratov Oblast in Russia, and the weeks each spring when Asia/Hebron and Asia/Jerusalem change on different dates. If you query inside one of those, do not trust this endpoint. Boundary precision is a separate question from vintage. The map is indexed as compacted H3 cells at resolution 6, whose half-width is about 1.6 km, chosen to match VMAP0's own stated positional accuracy of roughly 2 km rather than to flatter the index. So a point within a couple of kilometres of a zone border may be attributed to the neighbour, and no amount of the source's precision would fix that because the source does not have it. Away from a border the answer is exact. Every answer says where it came from under `source`. `boundary` means the point is inside a mapped timezone polygon and is the answer you are paying for. `coastal` means it is over water or on land this map does not cover, and the identifier is the nearest zone within about 60 km -- correct for a harbour or a coastal city whose coordinate falls just offshore, and not a boundary result. `nautical` means open water more than about 60 km from mapped land, answered with the tz database's own rule for international waters, meridians 15 degrees apart; it is not the time kept aboard any vessel and it ignores territorial waters. Longitude and latitude are checked against EPSG:4326 bounds before anything else touches them, because H3 silently normalises an out-of-range latitude into a real but wrong cell rather than refusing it. Reproject with POST /v1/transform first if you are not already in WGS 84. The DST flag is decided on offsets rather than on the tz database's own isdst bit, so Europe/Dublin reads as daylight saving in summer like everywhere else, and it is measured over a window either side of the instant so that a zone which changes its standard offset mid-year -- Asia/Almaty in 2024 -- is not mistaken for one on daylight saving.

the record, 2026-09-14 19:51 UTC · method · pinnable

As declared

GET
eip155:8453
USDC
exact

Every tag is a field on the listing, not a keyword TOLL assigned.

Who is paid

0x76A51b…968FCe

Takes payment for 21 endpoints on 1 host.

Among Inference

counted above89%

of 2,414 that carry counters

cheaper than17%

of 2,403 with a comparable price

2,470 endpoints are in this category. 148 declare exactly this price.

the comparison, 2026-09-15 21:20 UTC · method · live

Nearest on price

google ai mode ai modex402.openwebninja.com0.005 USDCpass
chat completionsx402.orthogonal.com0.005 USDCpass
agent record rubric assertrubric-protocol.com0.005 USDCpass
trust check x402trust402.vercel.app0.005 USDCpass
gauge lifecycleapi.truthbear.co0.005 USDCpass

Same category, nearest declared price, one per payee wallet (method). the list, 2026-09-15 21:20 UTC · method · live

Elsewhere in the record

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, "timezone on api.geoprimitives.dev", snapshot of 2026-09-15 21:20 UTC. https://tollindex.com/e/api-geoprimitives-dev-v1-timezone-643018/at/2026-09-15T21-20Z. Accessed [access date].

BibTeX

@misc{toll-e-api-geoprimitives-dev-v1-timezone-643018-2026-09-15T21-20Z,
  author = {TOLL},
  title = {timezone on api.geoprimitives.dev},
  howpublished = {\url{https://tollindex.com/e/api-geoprimitives-dev-v1-timezone-643018/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].}
}

Reports and replies about this endpoint

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

Report an error about timezone, or reply as the named seller