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. Plus NHTSA tire recalls by size and a DOT check that reads the code on a sidewall.
Free plan includes 100 API calls/mo — no card required.
Key endpoints
Lookup by vehicle, by size or by UUID, tire recalls and the DOT check — 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/vehicles?size=235/45R18
|
Reverse fitment: every vehicle that runs a size, as OEM or as an accepted alternate. |
GET
/v1/tire-sizes/{uuid}/recalls
|
NHTSA tire recalls whose notice names the fitment's OEM size — brands, lines, production windows and plant codes. |
GET
/v1/tire-sizes/dot/{tin}
|
The DOT check: plant, build week and year, age and the NHTSA tire recalls covering that week and plant. |
GET
/v1/tire-sizes/plants/{code}
|
Decode a tire plant code (the characters after DOT) to the plant's name, location and status from NHTSA vPIC. |
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: 10; max 10 on Free, 25 on Pro/Developer, 100 on Enterprise) | 10 |
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": 10, "total": 2, "last_page": 1 }
}
Tire data is compiled from open and licensed sources for reference only. Confirm fitment, load and speed rating in the vehicle owner's manual or tire placard before fitting tires. VehDB is not responsible for damage resulting from tire choices. See our terms.
NHTSA tire recalls
Tire recalls and the DOT check
A tire recall covers particular brands, plants and build weeks, so the size is only half the answer. One endpoint lists the recalls that name a size; the other checks one tire's DOT code against them.
The DOT check
GET /v1/tire-sizes/dot/{tin} reads the code after DOT on the sidewall: the plant (vPIC tire plant codes), the build week and year, the tire's age, and the NHTSA tire recalls whose printed production windows cover that week and plant. Pass size and brand to narrow.
Recalls naming a size
GET /v1/tire-sizes/{uuid}/recalls lists the NHTSA tire recalls whose notice names the fitment's OEM size, with the brands, lines, production windows and plant codes each notice prints.
Free Tire DOT Code Lookup
The same check without a key: enter a sidewall code to see how old the tire is, which plant made it and the recalls that cover it.
Learn moreProduction windows are read from the recall notices, and many print no dates or plants, so no match is not "not recalled": confirm with the tire maker or nhtsa.gov/recalls. Both responses carry the tire disclaimer.
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.
Live numbers, not logos
Pulled from the production database and the NHTSA sync log, refreshed hourly.
NHTSA recalls last synced
API pricing
Start on the free tier; every plan includes the REST API and the MCP server with the same token and quota.
Full plan comparison and FAQ on the pricing page. Prices in USD, cancel anytime.
Your AI agent's vehicle-data tools —
not glue code.
VehDB ships a native Model Context Protocol server. Claude, Cursor or any MCP client looks up fitments both ways (tire_sizes_for_vehicle, vehicles_for_tire_size) and checks a tire's DOT code for recalls (tire_dot_check) as first-class tools — no wrappers, no scraping, no glue code to maintain.
- Native MCP tools — search_vehicles, recalls_for_vehicle, complaints_for_vehicle, tire_sizes_for_vehicle, my_lists — callable by Claude, Cursor or any agent.
- One-click AI connector in Claude; in any other MCP client, paste one URL and sign in: no token to copy. Scripts use an API token. Same data and quota as the REST API.
- No scraping, no function-calling boilerplate, no schema drift — the agent gets typed, documented tools.
{ "mcpServers": {
"vehdb": { "url": "https://mcp.vehdb.com/mcp" }
} }
Build with 171,100 tire fitment records.
OEM sizes, validated alternates and computed geometry across 160 manufacturers. Free tier: 100 calls/mo, no card.
100 free API calls every month · REST API + MCP server on every plan · No card to start · See pricing