us geographies derived

api.geoprimitives.devIdentity derived

GET https://api.geoprimitives.dev/v1/us/geographies

passlisted in Coinbase#3 by calls of 3 on this host

0.01 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-10-13 14:08 UTC · method · pinnable

Validation state: pass; as of 2026-10-21 08:32 UTC · method · pinnable · sweep daily-2026-10-21
Uptime, 7 / 30 / 90 days: 100% / 100% / 100%; as of 2026-10-21 08:32 UTC · method · pinnable · 7 of 7 in 7d, 27 of 27 in 30d, 38 of 38 in 90d
Calls, trailing 30 days: 2; as of 2026-10-13 14:08 UTC · method · pinnable
Unique payers, trailing 30 days: 2; as of 2026-10-13 14:08 UTC · method · pinnable
Last called: 2026-10-08 05:32 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.01 USDC; as of 2026-10-13 14:08 UTC · method · pinnable · on eip155:8453
Networks: 1; as of 2026-10-13 14:08 UTC · method · pinnable

Counters

122 observations, 5 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

us geographies is a GET endpoint at api.geoprimitives.dev, listed in the Coinbase registry and filed by TOLL under identity.

us geographies is priced at 0.01 USDC on Base.

Its declared inputs are the query parameters lat and lon.

us geographies returns json; the example shows cell, found, notes, query, state, county and 2 others.

us geographies answered the sweep of 2026-10-21 with a valid 402, as at every sweep since 2026-09-11.

us geographies is one of 3 listed endpoints on api.geoprimitives.dev, 3rd by calls among them.

us geographies takes 1% of the calls counted across api.geoprimitives.dev.

The registry's counters give us geographies 2 calls and 2 unique payers over 30 days, every call from a different payer.

us geographies was last called 5 days before the snapshot.

Closest in price to us geographies within identity: br pix parse at api.losbeto.xyz and verify job at livecheck.fly.dev.

us geographies is priced above 34% of comparable listings in identity.

Its payee wallet receives for 21 listed endpoints on one host.

The seller's tags on us geographies are census, fips, geoid and united-states.

The price of us geographies is declared by 707 other listings in identity 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
registry	network	asset	amount	scheme	pay to
Coinbase	eip155:8453	USDC	0.01 USDC	exact	0x76A51b…968FCe

Preflight checks at the last sweep

the checks, as of 2026-10-21 08:32 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-10-21 08:32 UTC	pass	daily-2026-10-21
2026-10-20 08:43 UTC	pass	daily-2026-10-20
2026-10-19 06:18 UTC	pass	daily-2026-10-19
2026-10-18 08:30 UTC	pass	daily-2026-10-18
2026-10-17 18:31 UTC	pass	daily-2026-10-17
2026-10-16 04:44 UTC	pass	daily-2026-10-16
2026-10-15 06:19 UTC	pass	daily-2026-10-15
2026-10-14 04:41 UTC	pass	daily-2026-10-14
2026-10-13 09:08 UTC	pass	daily-2026-10-13
2026-10-12 06:33 UTC	pass	daily-2026-10-12
2026-10-11 04:55 UTC	pass	daily-2026-10-11
2026-10-10 13:06 UTC	pass	daily-2026-10-10
2026-10-09 05:04 UTC	pass	daily-2026-10-09
2026-10-08 06:42 UTC	pass	daily-2026-10-08
2026-10-07 05:51 UTC	pass	daily-2026-10-07
2026-10-06 06:47 UTC	pass	daily-2026-10-06
2026-10-05 06:25 UTC	pass	daily-2026-10-05
2026-10-04 09:13 UTC	pass	daily-2026-10-04
2026-10-03 04:26 UTC	pass	daily-2026-10-03
2026-10-02 13:37 UTC	pass	daily-2026-10-02
2026-10-01 06:48 UTC	pass	daily-2026-10-01
2026-09-30 06:05 UTC	pass	daily-2026-09-30
2026-09-29 18:26 UTC	pass	daily-2026-09-29
2026-09-28 04:17 UTC	pass	daily-2026-09-28
2026-09-25 20:00 UTC	pass	daily-2026-09-25
2026-09-23 05:41 UTC	pass	daily-2026-09-23
2026-09-22 05:50 UTC	pass	daily-2026-09-22
2026-09-21 06:14 UTC	pass	daily-2026-09-21
2026-09-20 18:52 UTC	pass	daily-2026-09-20
2026-09-19 04:15 UTC	pass	daily-2026-09-19
2026-09-18 10:00 UTC	pass	daily-2026-09-18
2026-09-17 04:13 UTC	pass	daily-2026-09-17
2026-09-16 04:14 UTC	pass	daily-2026-09-16
2026-09-15 04:11 UTC	pass	daily-2026-09-15
2026-09-14 04:10 UTC	pass	daily-2026-09-14
2026-09-13 04:09 UTC	pass	daily-2026-09-13
2026-09-12 06:25 UTC	pass	daily-2026-09-12
2026-09-11 09:53 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-10-08 05:32 UTC · method · live

The input and output block

{
  "input": {
    "type": "http",
    "method": "GET",
    "queryParams": {
      "lat": 33.4484,
      "lon": -112.074
    }
  },
  "output": {
    "type": "json",
    "example": {
      "cell": "8729b6d35ffffff",
      "found": true,
      "notes": [],
      "query": {
        "lat": 33.4484,
        "lon": -112.074
      },
      "state": {
        "fips": "04",
        "name": "Arizona",
        "usps": "AZ",
        "geoid": "04"
      },
      "county": {
        "fips": "013",
        "name": "Maricopa",
        "geoid": "04013",
        "stateFips": "04",
        "nameWithLegalType": "Maricopa County"
      },
      "vintage": {
        "rights": "public domain (17 U.S.C. 105, work of the US federal government)",
        "dataset": "TIGER/Line",
        "vintage": "2025",
        "congress": "119",
        "publisher": "US Census Bureau",
        "h3Resolution": 7,
        "h3FineResolution": 9
      },
      "coverage": {
        "reason": "Tract, block group, place and ZCTA are not answered. A national H3 index of any one of them is larger than this Worker's entire 3 MiB compressed code limit at the resolution those tiers need -- measured, not estimated: tract 3196 KiB gzipped and block group 5335 KiB even at the too-coarse resolution 8. They need an object store behind the Worker (EDW-1256 brings one). Until then, geocoding.geo.census.gov answers them free with a round trip, and the county GEOID this endpoint returns is the first five digits of both.",
        "answered": [
          "state",
          "county",
          "congressionalDistrict"
        ],
        "notAnswered": [
          "tract",
          "blockGroup",
          "place",
          "zcta"
        ]
      },
      "boundaryUncertain": {
        "county": false,
        "congressionalDistrict": false
      },
      "congressionalDistrict": {
        "name": "Congressional District 3",
        "geoid": "0403",
        "congress": "119",
        "district": "03",
        "stateFips": "04"
      },
      "boundaryAccuracyMetres": 610
    }
  }
}

What the listing says

Give it a longitude and latitude inside the United States and it answers with the Census FIPS codes for that point: the 2-digit state code, the 5-digit county GEOID, and the GEOID of the congressional district. Parameters go in the query string: this is a GET, there is no body. The codes are the product and the names are a courtesy. A county GEOID is the join key to essentially every geography-keyed federal dataset -- the American Community Survey, BLS Local Area Unemployment Statistics, BEA regional accounts, CDC WONDER, HUD, USDA, FEMA -- and the state code is its first two digits, so one call gives you both keys already in the form those tables expect. County GEOID is also the first five digits of a tract GEOID (11 digits) and of a block group GEOID (12), so it is the prefix you would filter a tract-level extract down with. COVERAGE, stated up front because the shortfall is the point: this endpoint answers state, county and congressional district, and it does NOT answer tract, block group, place or ZCTA. That is a size limit, not an oversight, and it was measured rather than guessed. A national compacted H3 index of tracts is 3196 KiB gzipped and of block groups 5335 KiB, at a resolution already too coarse for either; the whole Worker has 3 MiB compressed to spend and most of that was gone before this route existed. Those four tiers need an object store behind the Worker and will arrive with one. Every response repeats this under `coverage`, so an agent never has to infer it from a missing field. In the meantime geocoding.geo.census.gov answers all seven tiers, free, authoritative, at the cost of a round trip and a dependency. VINTAGE: TIGER/Line 2025, congressional districts for the 119th Congress. It is on every response under `vintage` and it matters more here than almost anywhere else in this catalog, because TIGER is re-cut annually and districts move with redistricting, so a stale district code is a wrong answer a caller cannot detect from the outside. Nothing here self-updates; a new vintage means a rebuild. The data is a work of the United States government and is in the public domain (17 U.S.C. 105) -- no attribution clause and no redistribution terms. ACCURACY, and this is the part to read before you trust a code. The boundaries themselves are full-resolution TIGER, the same geometry the Census Geocoder answers from, not a simplified copy. What is approximate is the lookup: the polygons are indexed as compacted H3 cells at resolution 7, about 1.22 km across, so a point within roughly 610 m of a boundary may be attributed to the neighbour. County equivalents and districts too small to describe at that resolution -- Falls Church city, the other Virginia independent cities, the congressional districts inside New York City -- carry a second index at resolution 9, about 87 m, and `boundaryAccuracyMetres` says which one answered you. Because a 610 m index is only useful if you know when not to trust it, every response carries `boundaryUncertain.county` and `boundaryUncertain.congressionalDistrict`. They are true when a neighbouring cell resolves to a different code, which means the boundary is close enough that the index cannot settle which side you are on. Measured against geocoding.geo.census.gov on 650 coordinates: on 400 population-weighted points the county code was right 389 times and the district code 383, and every one of the 11 and 17 disagreements was flagged; on 250 points drawn deliberately 100 m to 1500 m from a county line the county code was right 183 times, and every one of the 67 wrong county codes and 25 wrong district codes was flagged. Across all 650 it never returned a wrong code with the flag clear. It is generous in the other direction -- it flagged 74 of the 400 correct-heavy sample -- so treat `true` as "verify this one if it matters" rather than as "this is wrong". Outside the United States the answer is `found: false` with null codes and a paid 200, because "this coordinate is not in the US" is the answer you asked for. County polygons include their legal water area out to the three-mile limit and across the Great Lakes, so harbours, piers and lake coordinates resolve normally and only genuinely foreign or high-seas points fall out. Coverage is the 50 states, DC, Puerto Rico, American Samoa, Guam, the Northern Mariana Islands and the US Virgin Islands. A small amount of water is inside a county but inside no congressional district, which TIGER publishes as a real polygon; that answers with a district whose number is null rather than with a guess. 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. TIGER publishes in NAD83, which this reads as WGS 84; the two differ by under two metres, which is a fortieth of the index's own resolution.

the record, 2026-10-08 05:32 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 Identity

counted above34%

of 2,150 that carry counters

cheaper than34%

of 2,153 with a comparable price

2,199 endpoints are in this category. 707 declare exactly this price.

the comparison, 2026-10-13 14:08 UTC · method · live

Nearest on price

br pix parseapi.losbeto.xyz0.01 USDCpass
verify joblivecheck.fly.dev0.01 USDCpass
screening matchapi.relaystation.ai0.01 USDCpass
icypeas resultvaaya.ai0.01 USDCpass
perp screenerapi.nansen.ai0.01 USDCpass

Same category, nearest declared price, one per payee wallet (method). the list, 2026-10-13 14:08 UTC · method · live

Elsewhere in the record

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, "us geographies on api.geoprimitives.dev", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/api-geoprimitives-dev-v1-us-geographies-23cdcc/at/2026-10-13T14-08Z. Accessed [access date].

BibTeX

@misc{toll-e-api-geoprimitives-dev-v1-us-geographies-23cdcc-2026-10-13T14-08Z,
  author = {TOLL},
  title = {us geographies on api.geoprimitives.dev},
  howpublished = {\url{https://tollindex.com/e/api-geoprimitives-dev-v1-us-geographies-23cdcc/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 us geographies, or reply as the named seller