01
Resolve the place
We geocode a Texas street address, find the county FIPS, and keep the county profile as the reliable first destination.
Address lookup
Start with your address
Texas-only resolver. County routing is the reliable first-class public path today. ISD and special-district cards are best-effort index resolution (not full boundary assignment). Need a bookmarkable query contract? Use `/lookup`.
01
We geocode a Texas street address, find the county FIPS, and keep the county profile as the reliable first destination.
02
When the shared entity index has a matching city, you can open city or county. When it does not, the county remains the honest baseline.
03
Once you land on a profile, you can keep going into documents, money, search, and the rest of the broader CivicData stack.
Examples
Contract
Go deeper
The landing page and address lookup are the front door. These routes are the deeper platform surfaces they feed into.
Stack
One card per jurisdiction — expand in place for a short read, then open the full entity profile.
Open route→
Meetings
Browse ingested meeting rows with links to agenda PDFs, minutes, and video when the pipeline captured them.
Open route→
Search
Move across entities, documents, and public routes when you need to investigate past the front door.
Open route→
Fiscal
Follow general funds, debt, ACFR rows, and fiscal context without leaving the CivicData platform.
Open route→
Digest
See the briefing layer that turns raw records into a place-based habit and recurring read.
Open route→
Briefing
Subscriber-facing briefings, scheduled summaries, and the publishing workflow live here as they migrate over.
Open route→
Workspace
Analyst surfaces, team workflow, and account-linked tools sit beyond the public record card.
Open route→
Place
Neighborhood and block-level layers come after the statewide entity spine, with coverage labels intact.
Open route→