Distance Calculation

What it grounds

Give AI agents precise point-to-point distance through the same real-data layer, returning miles, kilometers and bearing from coordinates.

Ways to ground with it

Anchor location reasoning

Give an agent Distance Calculation so it resolves places, distances, and timezones from real data instead of approximating — the difference between a plausible answer and a correct one.

Verify user-supplied places

When a user names a location, the agent calls distancecalculator to confirm and normalize it before acting, closing off a common source of silent errors.

Cite the source of place data

Every location fact the agent uses carries Distance Calculation as its origin, so the reasoning is auditable end to end.

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_••••" }
    }
  }
}

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

What it returns

Each call returns structured fields your agent can read.

distanceMiles
distanceKm
location1
location2
bearing
direction
estimatedDriveTime

Distance Calculation, answered

How to ground an agent in it over MCP.

How do I give my agent Distance Calculation?

Enable it on VerveContext and point your agent framework at the VerveContext MCP endpoint. Distance Calculation then appears to the model as a tool named distancecalculator, 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. Distance Calculation is exposed as a standard tool, so nothing source-specific is required.

Can the agent cite Distance Calculation?

Distance Calculation is a capability rather than a factual source, so it isn't something to "cite" — but it runs on the same real-data layer, over the same MCP endpoint and key as every grounding source.

How many credits does a Distance Calculation call cost?

Each call costs 1 credit. 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?

Distance Calculation 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.

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

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

Anchor location reasoning

Verify user-supplied places

Cite the source of place data

Distance Calculation, answered

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

Scaling up?