A vehicle fitment database
for tires & wheels.
OEM and alternate tire sizes for every vehicle, with computed wheel geometry kept within ±3% of overall diameter, plus reverse tire-size search — all on the same UUID, served as clean JSON.
Free plan includes 100 API calls/mo — no card required.
What "fitment" means here
Fitment is an overloaded word in automotive data. We are precise about which kind we serve.
What we provide — tire & wheel fitment
- OEM tire size per vehicle configuration
- Alternate / plus-size options within ±3% overall diameter
- Computed geometry: overall diameter, section width, sidewall, revs/mile
- Reverse search: tire size → compatible vehicles
What we do not provide
- ACES/PIES parts fitment or part-to-vehicle applications
- An aftermarket parts catalog (brakes, filters, body panels, etc.)
- Wheel bolt patterns, offset or hub-bore lookups
Need parts context? See our parts & aftermarket solution page.
Key endpoints
All responses are JSON. Vehicles and tire sizes are addressed by UUID.
GET
/v1/cars/{uuid}/tire-sizes
|
OEM and alternate tire sizes that fit a specific vehicle configuration. |
GET
/v1/tire-sizes
|
List or reverse-search tire sizes — pass ?size=235/65R17 to find vehicles that take a size. |
GET
/v1/tire-sizes/{uuid}/geometry
|
Computed geometry for a tire size: overall diameter, section width, sidewall, revolutions per mile. |
Base URL: https://api.vehdb.com/v1
Geometry you can trust, not guess
Every alternate size is checked against the OEM overall diameter so the speedometer, ABS and ride height stay honest.
OEM + alternates
Each vehicle carries its factory tire size plus computed alternates — wider, taller or plus-sized — all kept within the ±3% overall-diameter tolerance.
Computed dimensions
GET /v1/tire-sizes/{uuid}/geometry returns overall diameter, section width, sidewall height and revolutions per mile for any size, no math on your side.
Reverse fitment search
Pass a size to GET /v1/tire-sizes and get back the vehicles that take it as OEM or alternate — built for retailers and marketplaces.
Example response
OEM, alternates and computed geometry in one consistent JSON shape.
{
"data": {
"vehicle_uuid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"make": "Honda",
"model": "CR-V",
"year": 2026,
"oem_tire_size": "235/65R17",
"alternate_tire_sizes": ["245/60R17", "255/60R18"],
"geometry": {
"overall_diameter_in": 29.0,
"section_width_mm": 235,
"sidewall_in": 6.0,
"revs_per_mile": 713,
"diameter_tolerance": "±3%"
}
}
}
Fitment data FAQ
Common questions about VehDB's tire and wheel fitment data.
Also see the Tire Sizes API, the VCdb explainer, and our parts & aftermarket solution.
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.
{ "mcpServers": {
"vehdb": { "url": "https://mcp.vehdb.com/mcp" }
} }