Vehicle Fuel Economy

What it grounds

Vehicle Fuel Economy returns the EPA ratings of every car and light truck sold in the US since 1984, electric vehicles included. Search by make, model, year and fuel type to get city, highway and combined MPG (or MPGe), electric range, engine, drive and transmission. Paid plans add kWh per 100 miles, charge time at 240V, annual fuel cost, five-year savings, CO2 per mile and the EPA fuel economy, greenhouse gas and smog scores.

Ways to ground with it

Ground answers in real data

Enable Vehicle Fuel Economy 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

Vehicle Fuel Economy 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 vehicle fuel economy 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_••••" }
    }
  }
}

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

What it returns

Each call returns structured fields your agent can read.

count
page
pages
returned
vehicles

Vehicle Fuel Economy, answered

How to ground an agent in it over MCP.

How do I give my agent Vehicle Fuel Economy?

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

Can the agent cite Vehicle Fuel Economy?

Vehicle Fuel Economy 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 Vehicle Fuel Economy 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?

Vehicle Fuel Economy 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. It draws on 50k vehicles since 1984.

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

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

Ground alongside

Browse all sources

Ground answers in real data

On the same endpoint and key

Traceable and current

Vehicle Fuel Economy, answered

Other ways to use Vehicle Fuel Economy

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

Scaling up?