Add vehicle fuel economy to your app
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. You switch it on with a single toggle — no SDK and no endpoint wiring — and it answers over MCP or REST using the same key as every other skill.
A real response from the Vehicle Fuel Economy Skill — exactly what your agent gets back when it makes the call.
{
"make": "Tesla",
"model": "Model 3",
"year": "2024"
}Enable Vehicle Fuel Economy and your app or agent can add vehicle fuel economy to your app on demand — no SDK, no endpoint wiring. It answers over MCP or REST using the same key as every other skill.
Over MCP, Vehicle Fuel Economy appears to your model as the vehiclefueleconomy tool it invokes whenever a task needs it — you don't write the glue, the agent reaches for it.
Prefer to call it directly? Any language that can send a GET can hit Vehicle Fuel Economy to add vehicle fuel economy to your app inline in your own server-side code.
Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.
It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.
vehiclefueleconomyCall it from your server with one request and your key. Node, Python, Go — anything that can send a GET.
GET /v1/vehiclefueleconomyHow to connect it over MCP or REST.
Same data, same VerveKit account, same credit balance — one key works on all of them.
The same key runs from your first prototype to millions of calls — on APIVerve's rails, 99.9% uptime.
See pricing