URL Location

What it grounds

Ground agents in verifiable URL hosting data — country, city and coordinates — so location answers rest on real geolocation, not guesses.

Ways to ground with it

Ground security & research agents

Let an agent call URL Location to pull a domain's real records or health before it reasons about risk — verifiable signal instead of a confident guess.

Enrich a workflow with real records

Wire urllookup into a compliance or research agent so each domain it evaluates is backed by live data it can cite.

Auditable lookups

Every record the agent uses carries URL Location as its origin, so findings are traceable.

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

# “urllookup” 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.

range
country
region
city
timezone
state
zipcode
coordinates

URL Location, answered

How to ground an agent in it over MCP.

How do I give my agent URL Location?

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

Can the agent cite URL Location?

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

How many credits does a URL Location 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?

URL Location 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; URL Location is one of 300+ sources on the same key. Invoices and card statements show APIVERVE.

Ground security & research agents

Enrich a workflow with real records

Auditable lookups

URL Location, answered

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

Scaling up?