timezone?at=2026-07-04T16%3A00%3A00Z&lat=40.7128&lon=-74.006

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…

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 insid

UNRATEDListed

Overview

Grade?

UNRATED

0 of 30 paid calls toward a letter

Price

$0.005 per call

Paid calls

none yet

delivery unknown until someone pays

More info

Seller?

0x76a51b5d…21968fce

URL

https://api.geoprimitives.dev/v1/timezone?at=2026-07-04T16%3A00%3A00Z&lat=40.7128&lon=-74.006

Seen

first 35 days ago · last 17 hr ago

64 free handshakes

Payment

Pays through

x402

Offered on?

Base USDC

Listed on?

Base

Score, from free handshakes onlyweights 2026.09.6

UN
RATED

0.734 liveness verified, no letter

To a letter · 30 paid calls

0 of 30

Held down by latency p95 · gap to 1.000 is 0.266: 0.066 uncertain ? + 0.200 short ? · 0.066 to B

How the composite of 0.734 is made up, part by part
Component	Weight	Measured	Lower bound ?		Adds	Short ?	Uncertain ?
latency p95costs the most it answered as fast as its class	0.20	0.00	0.000		0.000	−0.200	0
liveness it answered at all	0.60	1.00	0.890		0.534	0	−0.066
price stability the price stayed where it was listed	0.20	1.00	1.000		0.200	0	0
Composite	1.00		0.734	gap to 1.000 = 0.266 · 0.200 short · 0.066 uncertain	0.734	−0.200	−0.066

Not measured: correctness · nobody paid; honesty · nobody paid; schema conformance · no answer had a published shape to check

The multiplication, written out

  0.200 × 0.000   latency p95    
+ 0.600 × 0.890   liveness       
+ 0.200 × 1.000   price stability
= 0.734           → UNRATED: 56 of 30 paid calls      weights 2026.09.6 · 56 samples · seed cap_01M1A59RV6D3P266JBFVWQ1Z4A|2026-09-03T19:06:19.953Z|2026.09.6

Verify it yourselfnpx teppi-check https://api.geoprimitives.dev/v1/timezone?at=2026-07-04T16%3A00%3A00Z&lat=40.7128&lon=-74.006curl -s https://api.teppi.xyz/v1/trust/cap_01M1A59RV6D3P266JBFVWQ1Z4A