ZIP Demographics

What it grounds

Ground agents in verifiable US Census data across 33k+ ZIP areas so market and location answers rest on real ACS estimates, not guesses.

Ways to ground with it

Resolve identifiers to real detail

Let an agent call ZIP Demographics to expand an ID into full, structured detail from live data — grounding enrichment steps in fact, not recall.

Enrich mid-workflow

Wire zipdemographics into an agent so it pulls the fields it's missing at the moment it needs them, each traceable to the source.

Auditable enrichment

Every detail the agent adds carries ZIP Demographics as its origin, keeping the pipeline verifiable.

Connect over MCP

Point your agent framework at the VerveContext endpoint. Every enabled source — this one included — becomes a tool the model can call. No per-source plumbing.

context.json

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp",
      "headers": { "x-api-key": "vc_live_••••" }
    }
  }
}

# “zipdemographics” is now a tool your agent can call

Facts your agent can cite

Each call returns structured fields your agent can read — and trace back to this source.

zip
name
acsYear
population
income
housing
education
employment

ZIP Demographics, answered

How to ground an agent in it over MCP.

How do I give my agent ZIP Demographics?

Enable it on VerveContext and point your agent framework at the VerveContext MCP endpoint. ZIP Demographics then appears to the model as a tool named zipdemographics, which it calls when a task needs it — no per-source plumbing.

Which agents and frameworks can use it?

Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol. ZIP Demographics is exposed as a standard tool, so nothing source-specific is required.

Can the agent cite ZIP Demographics?

Yes. ZIP Demographics is verifiable factual grounding — every value the agent pulls can carry ZIP Demographics as its source, so a person (or another system) can trace where the fact came from.

How many credits does a ZIP Demographics call cost?

Each call costs 5 credits. Scoped keys let you grant an agent only the sources it should reach, and usage logs show exactly what was pulled to ground each answer.

How current is the data?

ZIP Demographics is served live from APIVerve's production data engine and pulled at the moment the agent calls it, so answers reflect the world now rather than the model's training cutoff. It draws on 33k+ ZIPs.

Where does the data come from, and what shows on my bill?

VerveContext runs on APIVerve, our production data engine; ZIP Demographics is one of 300+ sources on the same key. Invoices and card statements show APIVERVE.

Resolve identifiers to real detail

Enrich mid-workflow

Auditable enrichment

ZIP Demographics, answered

Ground your agents in ZIP Demographics. Connect over MCP, enable the source, and every answer carries its receipts.

Scaling up?