NHTSA vPIC Vehicle Make Directory

Use the NHTSA vPIC Vehicle Make Directory API to retrieve the vehicle makes registered in the vPIC dataset. Request JSON output without a manufacturer or vehicle-type filter and request JSON output. The response returns make names together with their numeric identifiers for subsequent lookups. Use the results to build vehicle selection menus, normalize brand names, or connect records to make-specific model queries. The directory can be large and the documented method does not provide a page parameter. The detail page provides supported parameters, request and response examples, coverage notes, and the configured per-call price.

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
Required output format for this OpenAny product. Use json; XML and CSV are not exposed by this configuration.

Sample response

{
  "Count": 12436,
  "Message": "Response returned successfully",
  "Results": [
    {
      "Make_ID": 12858,
      "Make_Name": "#1 ALPINE CUSTOMS"
    },
    {
      "Make_ID": 4877,
      "Make_Name": "1/OFF KUSTOMS, LLC"
    },
    {
      "Make_ID": 11257,
      "Make_Name": "102 IRONWORKS, INC."
    },
    {
      "Make_ID": 12255,
      "Make_Name": "12832429 CANADA INC."
    },
    {
      "Make_ID": 13053,
      "Make_Name": "137 INDUSTRIES INC."
    },
    {
      "Make_ID": 6387,
      "Make_Name": "17 CREEK ENTERPRISES"
    },
    {
      "Make_ID": 12948,
      "Make_Name": "1955 CUSTOM BELAIR"
    },
    {
      "Make_ID": 9172,
      "Make_Name": "1M CUSTOM CAR TRANSPORTS, INC."
    },
    {
      "Make_ID": 6124,
      "Make_Name": "1ST CHOICE MANUFACTURING INC"
    },
    {
      "Make_ID": 12972,
      "Make_Name": "2 GOLDEN EAGLES"
    },
    {
      "Make_ID": 6488,
      "Make_Name": "2-G TRAILER CO LLC"
    },
    {
      "Make_ID": 11399,
      "Make_Name": "24/7 ONSITE CAMERAS INC"
    },
    {
      "Make_ID": 608,
      "Make_Name": "280 TRAILERS"
    },
    {
      "Make_ID": 10123,
      "Make_Name": "3 CUSTOM SOLUTIONS"
    },
    {
      "Make_ID": 11253,
      "Make_Name": "3 STAR MFG LTD"
    },
    {
      "Make_ID": 8792,
      "Make_Name": "3&1 ENTERPRISES, LLC DBA IMPACT TRAILERS"
    },
    {
      "Make_ID": 13576,
      "Make_Name": "321TRAILERS"
    },
    {
      "Make_ID": 7388,
      "Make_Name": "33 EAST MAINTENANCE INC"
    },
    {
      "Make_ID": 10005,
      "Make_Name": "357 GOLF CARTS"
    },
    {
      "Make_ID": 11527,
      "Make_Name": "36 FEET LLC"
    }
  ],
  "SearchCriteria": null
}

Response result

Response structure

Inferred from examples
  • Countinteger
  • Messagestring
  • Resultsobject[]
    • Make_IDinteger
    • Make_Namestring
  • SearchCriterianull

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 Vehicle Make Directory with your agent

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