Census Data API

Name: Census Data API API
Brand: Census Data API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentAddress ValidationapiKey5 EndpointsREST

For Agents

Query U.S. Census Bureau demographic, economic, and housing datasets by year, dataset, variable, and geography. Discover available datasets, variables, and geographic levels.

Quickstart

Get started with Census Data API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"query US Census ACS demographic data"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Census Data API API.

Discover every public Census dataset and its vintage via /data

List the variables available in a given dataset and vintage via variables.json

List the geographic levels supported by a dataset via geography.json

Browse variable groups for ACS detailed and subject tables

GET STARTED

Start building with Census Data API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Census Data API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for the U.S. Census Bureau Data API, keeping it validated and agent-ready. The Census Data API provides access to dozens of public datasets, including the American Community Survey (ACS), Decennial Census, and County Business Patterns. Queries are scoped by dataset vintage (year) and identifier, and can request specific variables aggregated to a chosen geographic level — state, county, tract, ZIP code tabulation area, and more. Five core endpoints cover dataset discovery, variable listing, geography listing, group listing, and the data query itself.

Use Cases

Patterns agents use Census Data API API for, with concrete tasks.

★ Demographic Lookup for Geographic Analysis

Civic-tech teams, researchers, and data agents query ACS variables — population, age, race, income — for a chosen geography to feed dashboards or reports. The agent first lists variables for the dataset, then queries /data/{vintage}/{dataset} with a variable list and a geographic filter such as `for=county:*&in=state:06`.

GET /data/2022/acs/acs5 with get=B01003_001E (total population) and for=county:* in state 06 to return California county populations

Variable Discovery for Reporting

A reporting workflow needs to pick the right Census variable codes for a question like 'median household income by tract'. An agent queries variables.json for the target dataset, filters by label, and returns the variable code and concept. This eliminates the manual code lookup against Census documentation.

GET /data/2022/acs/acs5/variables.json and search for 'Median household income' to return the matching variable code and concept

Geography-Aware Address Enrichment

Companies enriching customer addresses with demographic context use the Census API to fetch tract or ZIP-code-level statistics for the geocoded address. The geography.json endpoint confirms which levels the dataset supports, and the data query returns the requested variables for that geography.

GET /data/2022/acs/acs5/geography.json to confirm tract-level support, then query variables for tract 06037201001

AI Agent Integration via Jentic

A research agent uses Jentic to discover Census datasets, load schemas for the variables and data endpoints, and execute calls without holding the API key directly. The agent can chain Census lookups with cBioPortal or CDC ReportStream context for population-normalised public-health analyses.

Use Jentic to search 'query Census ACS data', load the schema for /data/{vintage}/{dataset}, and execute against acs5 for the requested county

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for the u.

METHOD

PATH

DESCRIPTION

GET

/data

List all available Census datasets

GET

/data/{vintage}/{dataset}

Query a specific Census dataset

GET

/data/{vintage}/{dataset}/variables.json

List variables for a dataset

GET

/data/{vintage}/{dataset}/geography.json

List geographies for a dataset

GET

/data/{vintage}/{dataset}/groups.json

List variable groups

GET

/data

List all available Census datasets

GET

/data/{vintage}/{dataset}

Query a specific Census dataset

GET

/data/{vintage}/{dataset}/variables.json

List variables for a dataset

GET

/data/{vintage}/{dataset}/geography.json

List geographies for a dataset

GET

/data/{vintage}/{dataset}/groups.json

List variable groups

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Census API keys are stored encrypted in the Jentic vault and appended to each request as the `key` query parameter at execution time. Agents never hold the raw key value.

Intent-based discovery

Agents search Jentic by intent (e.g., 'query Census ACS data') and Jentic returns the /data and variables.json operations with their input schemas, so the agent doesn't need to navigate Census documentation.

Time to first call

Direct Census integration: 1-2 days mapping dataset, variable, and geography parameters and handling JSON-array responses. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

AESDirect WebLink Inquiry API

Different US government API surface for export filings

Pair with Census when an agent needs both export-filing context and population denominators for trade analyses

Complementary

Prime ReportStream

Public health data routing that pairs with Census for incidence rate calculations

Use Census denominators alongside ReportStream case counts to compute population-normalised rates

Complementary

cBioPortal Public API

Cancer cohort data that benefits from Census-derived population context

Pair with Census when a researcher contextualises cancer cohort findings against the underlying population

FAQs

Specific to using Census Data API API through Jentic.

Why is there no official OpenAPI spec for the Census Data API?

The Census Bureau publishes documentation pages but not a structured OpenAPI artifact. Jentic generates and maintains this spec so that AI agents and developers can call Census Data API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Census Data API use?

Census uses an API key passed as the `key` query parameter. Keys are issued for free at api.census.gov/data/key_signup.html and are required above a small unauthenticated threshold. Through Jentic the key is stored in the encrypted vault and appended at execution time.

Can I query American Community Survey data with this API?

Yes. GET /data/{vintage}/{dataset} with dataset paths like acs/acs5 or acs/acs1 runs ACS queries. Use the variables.json endpoint to find the right variable codes and geography.json to find supported geographic levels.

What are the rate limits for the Census Data API?

The Census Bureau allows up to 500 calls per IP address per day without a key, with no public hard cap once a key is registered. Throttle bulk pulls and back off on 429 responses; very large variable-by-tract queries should be batched.

How do I run an ACS query through Jentic?

Search Jentic for 'query Census ACS data', load the schema for GET /data/{vintage}/{dataset}, and execute with the variable list in the get parameter and the geography filter in for/in. The Census key stays in the Jentic vault.

Is the Census Data API free?

Yes. The Census Data API is free to use. Keys are also free; they exist to track and lift the unauthenticated rate cap.