NHTSA vPIC Models by Make ID, Year and Vehicle Type

Use the NHTSA vPIC Models by Make ID, Year and Vehicle Type API to find vehicle models for an exact make ID, model year and vehicle type. Supply a positive numeric make ID, a model year after 1995, and the vehicle type and request JSON output. The response includes model identifiers, model names and their available brand or vehicle-type references. Use the results to create precise vehicle selection menus, organize fleet categories, or compare model availability within a selected year. This configured route uses all three filters and does not silently substitute the manufacturer ID for the make ID. See the detail page for parameters, examples, coverage notes, and pricing.

Selected price
$0.001 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Exact numeric vPIC make ID. A specific positive ID avoids the expensive all-makes query.
Model year for the model lookup. The documented filtered-model method accepts years greater than 1995.
Full or partial vehicle type name, such as car, truck or motorcycle.
Required output format for this OpenAny product. Use json; XML and CSV are not exposed by this configuration.

Sample response

{
  "Count": 1,
  "Message": "Results returned successfully",
  "Results": [
    {
      "Make_ID": 474,
      "Make_Name": "HONDA",
      "Model_ID": 1866,
      "Model_Name": "Ridgeline",
      "VehicleTypeId": 3,
      "VehicleTypeName": "Truck"
    }
  ],
  "SearchCriteria": "Make ID:474 | ModelYear:2015 | VehicleType:truck"
}

Response result

Response structure

Inferred from examples
  • Countinteger
  • Messagestring
  • Resultsobject[]
    • Make_IDinteger
    • Make_Namestring
    • Model_IDinteger
    • Model_Namestring
    • VehicleTypeIdinteger
    • VehicleTypeNamestring
  • SearchCriteriastring

Loading related APIs…

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use NHTSA vPIC Models by Make ID, Year and Vehicle Type with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.