NHTSA vPIC Makes by Manufacturer

Use the NHTSA vPIC Makes by Manufacturer API to find the vehicle makes associated with a manufacturer. Supply the manufacturer ID as text or a full or partial manufacturer name and request JSON output. The response returns the make and manufacturer associations available in vPIC. Use the results to separate manufacturing entities from marketed brands, build ownership reference tables, or prepare make IDs for model searches. Name matching can return associations for multiple manufacturers, so retain their identifiers when combining results. 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
Manufacturer ID as text for an exact match, or a full/partial manufacturer name for a name match.
Required output format for this OpenAny product. Use json; XML and CSV are not exposed by this configuration.

Sample response

{
  "Count": 16,
  "Message": "Results returned successfully",
  "Results": [
    {
      "Make_ID": 474,
      "Make_Name": "HONDA",
      "Mfr_Name": "HONDA MOTOR CO., LTD."
    },
    {
      "Make_ID": 474,
      "Make_Name": "HONDA",
      "Mfr_Name": "AMERICAN HONDA MOTOR CO., INC."
    },
    {
      "Make_ID": 474,
      "Make_Name": "HONDA",
      "Mfr_Name": "HONDA OF CANADA MFG., A DIVISION OF HONDA CANADA INC."
    },
    {
      "Make_ID": 474,
      "Make_Name": "HONDA",
      "Mfr_Name": "HONDA OF THE U.K. MFG., LTD."
    },
    {
      "Make_ID": 474,
      "Make_Name": "HONDA",
      "Mfr_Name": "HONDA DE MEXICO, S.A. DE C.V."
    },
    {
      "Make_ID": 474,
      "Make_Name": "HONDA",
      "Mfr_Name": "THAI HONDA CO., LTD."
    },
    {
      "Make_ID": 474,
      "Make_Name": "HONDA",
      "Mfr_Name": "HONDA VIETNAM CO., LTD."
    },
    {
      "Make_ID": 474,
      "Make_Name": "HONDA",
      "Mfr_Name": "MOTO HONDA DA AMAZONIA LTDA."
    },
    {
      "Make_ID": 474,
      "Make_Name": "HONDA",
      "Mfr_Name": "SUNDIRO HONDA MOTORCYCLE CO., LTD."
    },
    {
      "Make_ID": 474,
      "Make_Name": "HONDA",
      "Mfr_Name": "MONTESA HONDA SA"
    },
    {
      "Make_ID": 475,
      "Make_Name": "ACURA",
      "Mfr_Name": "HONDA MOTOR CO., LTD."
    },
    {
      "Make_ID": 475,
      "Make_Name": "ACURA",
      "Mfr_Name": "AMERICAN HONDA MOTOR CO., INC."
    },
    {
      "Make_ID": 475,
      "Make_Name": "ACURA",
      "Mfr_Name": "HONDA OF CANADA MFG., A DIVISION OF HONDA CANADA INC."
    },
    {
      "Make_ID": 475,
      "Make_Name": "ACURA",
      "Mfr_Name": "HONDA DE MEXICO, S.A. DE C.V."
    },
    {
      "Make_ID": 542,
      "Make_Name": "ISUZU",
      "Mfr_Name": "HONDA MOTOR CO., LTD."
    },
    {
      "Make_ID": 7351,
      "Make_Name": "SUNDIRO  HONDA MOTORCYCLE CO. LTD",
      "Mfr_Name": "SUNDIRO HONDA MOTORCYCLE CO., LTD."
    }
  ],
  "SearchCriteria": "Manufacturer:honda"
}

Response result

Response structure

Inferred from examples
  • Countinteger
  • Messagestring
  • Resultsobject[]
    • Make_IDinteger
    • Make_Namestring
    • Mfr_Namestring
  • SearchCriteriastring

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 Makes by Manufacturer with your agent

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