Insurance & Underwriting

Vehicle data for insurance & underwriting

Rating and claims teams need consistent make/model/year specs, body class, fuel type and open recall status keyed to one stable identifier — not five vendors stitched by hand.

Free plan includes 100 API calls/mo — no card required.

api.vehdb.com
# Insurance & Underwriting — one call, real answers
GET /v1/cars?make=Toyota&year=2024
{ "data": [ {
  "uuid": "550e8400-e29b-…",
  "make": "Toyota", "model": "Camry", "year": 2024 } ] }
# Same UUID, the data you need
GET /v1/cars/{uuid}/recalls → "recall_count": 2
GET /v1/cars/{uuid}/tire-sizes "235/45R18"

Datasets that solve it

The exact data this segment leans on — all on the same UUID, all queryable by API or MCP.

Specifications (make, model, year, body, drivetrain, fuel)

Live NHTSA recalls & NCAP safety ratings

EPA fuel economy & CO₂

Tire fitment for repair/replacement costing

Base URL: https://api.vehdb.com/v1

What teams build

Real workflows insurance & underwriting ship on top of VehDB.

  • Risk scoring by body class, drivetrain and safety rating
  • Open-recall flags at quote and renewal
  • Total-loss & repair-cost inputs from fitment and class
  • Clean VIN-grade specs for policy admin systems

Why vehdb

The same advantages, whichever segment you sit in.

Enriched, not just listed

Specs carry EPA fuel economy on cars and live NHTSA recalls plus NCAP ratings — the next question is already answered inline.

Multi-asset on one UUID

Cars, motorcycles, boats and tire fitment share a model. The record your analyst sees is the record your backend queries.

MCP server built in

Expose VehDB as native tools to Claude, Cursor or any agent — no glue code, no scraping.

Transparent pricing

Quota-based plans, no per-seat surprises. The free tier is real: 100 calls/mo, no card.

Government-sourced provenance

Enrichment comes from U.S. federal public-domain data (EPA, NHTSA) — clean licensing, transparent origins.

Built for production

Stable UUIDs, JSON responses with pagination, and saved searches that notify you when new records match.

See the full provenance on the data sources page.

AI-NATIVE · MCP SERVER

Your AI agent's vehicle-data tools —not glue code.

VehDB ships a native Model Context Protocol server. Claude, Cursor or any MCP client queries cars, recalls, fuel economy and tire fitment as first-class tools — no wrappers, no scraping, no glue code to maintain.

  • Native MCP tools — search_vehicles, tire_sizes_for_vehicle, recalls, my_lists — callable by Claude, Cursor or any agent.
  • OAuth2 for AI providers plus simple Bearer tokens. Same auth, same data as the REST API and workspace.
  • No scraping, no function-calling boilerplate, no schema drift — the agent gets typed, documented tools.
claude_desktop_config.json
{ "mcpServers": {
    "vehdb": { "url": "https://mcp.vehdb.com/mcp" }
  } }
# the agent calls a typed tool, not your scraper
tool search_vehicles(make="Toyota", year=2026)
tool tire_sizes_for_vehicle(uuid) → "235/65R17"

Solve insurance & underwriting on VehDB.

Rating and claims teams need consistent make/model/year specs, body class, fuel type and open recall status keyed to one... Start free, then scale by usage — not by seat.

Operated by Savas OÜ (Tallinn, Estonia — EU) · GDPR-compliant · Billing by Stripe · Terms · Privacy