Lookup contract

Use the same civic journey in a bookmarkable form.

/lookup keeps the resolver portable for integrations, bookmarks, and shared links. Pass ?q= or ?query= and the address-first experience still lands in the same profiles.

Start with your address

Enter a Texas street address — you will land on your block view (identity chips, this week, representatives, meetings) with honest coverage notes, then you can open county, city, or ISD profiles.

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

Resolve the place

We geocode a Texas street address, find the county FIPS, and keep the county profile as the reliable first destination.

02

Choose the right profile

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

Move into the platform

Once you land on a profile, you can keep going into documents, money, search, and the rest of the broader CivicData stack.

Examples

Start from a familiar place, then move deeper.

  • Harris County for the county scorecard, documents, and money tab.
  • /county/48201 to preserve the legacy county redirect contract.
  • /lookup?q= for bookmarked integrations and prefilled search flows.

Contract

Same civic journey, explicit limits.

This route is the same resolver as /address; the only difference is that it supports prefilled query params for integrations and durable links.

Go deeper

Broader platform

The landing page and address lookup are the front door. These routes are the deeper platform surfaces they feed into.