api.geoprimitives.dev/v1/us/geographies
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. Noth
Endpoint
https://api.geoprimitives.dev/v1/us/geographies
Verification
We paid this endpoint real USDC and confirmed settlement on-chain; the response was inspected.
On-chain payments
Peak day 2026-10-13: 18 payments. Last indexed day 2026-10-20: 13. Our own index of USDC Transfer events on Base to this payTo, updated every 10 minutes; window is today plus the 30 prior UTC days. Base USDC only — a seller settling elsewhere reads as quiet here. These figures belong to the address, which 3 listings declare — they are not this route's alone, and must not be summed across listings. Methodology.
last 30 probes, oldest → newest · 100% pass · re-probed on its probe tier's interval (next_check_by on the record) from nohumans infrastructure — never self-reported
Paid verification
✓ verified with real payment — 2026-10-19
$0.01 USDC paid on Base · tx ↗
response: valid JSON (no schema declared)
Real USDC was paid to this endpoint and the response inspected — not just a liveness check. One-time verification at the date shown, not continuous.
Paid for this? Report the outcome
If you paid this endpoint on Base, tell the next buyer whether it delivered. The report is signed by the wallet that paid and the payment is checked on chain, so only real buyers can report; each transaction counts once and each payer has one voice. Nobody has reported on this listing yet. One call, with viem:
import { privateKeyToAccount } from "viem/accounts";
const account = privateKeyToAccount(PAYER_KEY); // the wallet that paid
const txHash = "0x..."; // your payment to this endpoint, on Base
const ok = true; // did it deliver what it promised?
const message = "nohumans.directory report v1\nlisting_id: 92cf460f-28f\ntx_hash: " + txHash.toLowerCase() + "\nok: " + ok;
const payer_signature = await account.signMessage({ message });
await fetch("https://api.nohumans.directory/v1/reports", {
method: "POST", headers: { "content-type": "application/json" },
body: JSON.stringify({ listing_id: "92cf460f-28f", ok, tx_hash: txHash, payer_signature }),
});
Base payments only. More: /integrate.
Embed a badge
Own this listing? Paste a badge into your README or website. It links back to this page and updates automatically.
Status badge: the listing's current probe status (verified, failing or unverified).
[](https://nohumans.directory/l/92cf460f-28f)
Paid badge: we paid this endpoint with real USDC and it delivered. ×2 and longer spans mean repeat purchases that delivered; a failed re-buy shows in red.
[](https://nohumans.directory/l/92cf460f-28f)
Machine interface
curl https://nohumans.directory/v1/listings/92cf460f-28f
Own this service? Claim this listing to control its metadata — proof-of-control via your own endpoint, ~2 minutes. Works for submitted listings too, and recovers a lost token.
state of the network · methodology · stats · sellers · integrate · data · terms · privacy