Earthquake

What it grounds

Ground agents in real-time worldwide seismic data so hazard and monitoring answers reflect live quake activity instead of stale figures.

Ways to ground with it

Grounded scheduling & logistics

Let a scheduling or ops agent call Earthquake before it confirms an outdoor booking or route, so decisions rest on the real forecast instead of a guess.

Support agents that don't invent forecasts

A customer-support agent asked about conditions will make something up unless it can check. Enable Earthquake and it grounds the answer in live data it can cite.

Location-aware reasoning

Feed earthquake into a multi-step agent so downstream reasoning — travel, delivery, events — starts from verified conditions.

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

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

earthquakes_LastUpdated
earthquakes_LastHour
count24h
largestMagnitude24h
avgMagnitude24h
earthquakes

Earthquake, answered

How to ground an agent in it over MCP.

How do I give my agent Earthquake?

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

Can the agent cite Earthquake?

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

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

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

Grounded scheduling & logistics

Support agents that don't invent forecasts

Location-aware reasoning

Earthquake, answered

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

Scaling up?