Contact Extraction

What it grounds

Ground agents in real contact details scraped live from a page — emails, phones and places — so outreach rests on verifiable data, not invented details.

Ways to ground with it

Ground answers in real data

Enable Contact Extraction and it becomes a tool your agent calls over MCP to check itself against live data before it answers — grounding the response instead of guessing.

On the same endpoint and key

Contact Extraction rides the one VerveContext MCP endpoint alongside 300+ other sources, so adding it to an agent is a toggle, not an integration.

Traceable and current

The agent pulls contact extraction at answer time and can carry the source with the result, so the reasoning stays current and auditable.

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

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

url
emails
phones
places
emailCount
phoneCount
placeCount
uniqueDomains

Contact Extraction, answered

How to ground an agent in it over MCP.

How do I give my agent Contact Extraction?

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

Can the agent cite Contact Extraction?

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

How many credits does a Contact Extraction call cost?

Each call costs 10 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?

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

Ground answers in real data

On the same endpoint and key

Traceable and current

Contact Extraction, answered

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

Scaling up?