Ground agents in verifiable US state boundary geometry so mapping and geospatial answers rest on real census GeoJSON, not approximation.
Give an agent State Boundary so it resolves places, distances, and timezones from real data instead of approximating — the difference between a plausible answer and a correct one.
When a user names a location, the agent calls stateboundaries to confirm and normalize it before acting, closing off a common source of silent errors.
Every location fact the agent uses carries State Boundary as its origin, so the reasoning is auditable end to end.
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.
{
"mcpServers": {
"vervecontext": {
"url": "https://api.vervecontext.com/v1/mcp",
"headers": { "x-api-key": "vc_live_••••" }
}
}
}Each call returns structured fields your agent can read — and trace back to this source.
typefeaturesHow to ground an agent in it over MCP.
