Answer "will it fit?"
with math, not guesswork.
OEM and alternate tire sizes per vehicle — plus a computed geometry endpoint that returns diameter, revs-per-mile and each alternate's diameter delta against the industry ±3% rule.
Free plan includes 100 API calls/mo — no card required.
Key endpoints
Lookup by vehicle, by size, or by UUID — plus helper endpoints for cascading selectors.
GET
/v1/tire-sizes
|
List tire size records with filtering — make, model, year, OEM size, submodel. Paginated JSON. |
GET
/v1/tire-sizes/{uuid}
|
Single record by UUID — OEM size, all alternates and vehicle details. |
GET
/v1/tire-sizes/{uuid}/geometry
|
Computed diameter and revs-per-mile, with each alternate's diameter_delta_pct vs the ±3% rule. |
GET
/v1/tire-sizes/makes
|
All vehicle makes in the tire dataset — for dropdowns and type-ahead selectors. |
GET
/v1/tire-sizes/models?make=Toyota
|
All models for a given make — chain with /makes for cascading vehicle selectors. |
Base URL: https://api.vehdb.com/v1
Query parameters
Filter by vehicle or reverse-search by tire size — all parameters combine.
| Parameter | Type | Description | Example |
|---|---|---|---|
make |
string | Filter by vehicle manufacturer name | Toyota |
model |
string | Filter by vehicle model name | Camry |
year |
integer | Filter by exact model year | 2024 |
year_min |
integer | Minimum year for range filtering | 2020 |
year_max |
integer | Maximum year for range filtering | 2025 |
tire_size |
string | Filter by OEM tire size specification | 235/45R18 |
submodel |
string | Filter by vehicle trim or submodel | XLE |
page |
integer | Page number for paginated results (default: 1) | 2 |
per_page |
integer | Results per page (default: 20) | 25 |
Fitment math, done for you
Sizes are strings; fitment is geometry. The API computes the engineering values so your product doesn't have to.
Computed geometry
Overall diameter, sidewall height and revs-per-mile derived from any size string — pure math, consistent for every record.
The ±3% rule, built in
Each alternate size carries diameter_delta_pct against the OEM diameter — flag anything outside the industry ±3% tolerance automatically.
Reverse lookup
Filter by tire_size to find every vehicle a given size fits — the query behind tire shop search boxes and plus-sizing tools.
Example response
OEM and alternative sizes per trim — different trims of the same model can run different sizes.
{
"data": [
{
"uuid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"year": 2024,
"make": "Toyota",
"model": "Camry",
"submodel": "XLE",
"tire_size_oem": "235/45R18",
"alternate_tire_sizes": "225/50R17, 245/40R19, 225/45R18"
},
{
"uuid": "b2c3d4e5-f6a7-8901-bcde-f12345678901",
"year": 2024,
"make": "Toyota",
"model": "Camry",
"submodel": "LE",
"tire_size_oem": "215/55R17",
"alternate_tire_sizes": "225/50R17, 205/60R16, 225/45R18"
}
],
"meta": { "current_page": 1, "per_page": 20, "total": 2, "last_page": 1 }
}
Tire Sizes API FAQ
Common questions about the VehDB Tire Sizes API, data coverage, and integration.
Also see the Cars, Motorcycles and Boats APIs, or the API overview.
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" }
} }