NHTSA vPIC Manufacturer Details

Use the NHTSA vPIC Manufacturer Details API to retrieve registration details for one or more manufacturers. Supply an exact numeric manufacturer ID or a full or partial name, and a page when needed and request JSON output. The response provides the manufacturer details recorded in the source registry. Use the results to inspect registration records, reconcile organization identities, or enrich a manufacturer directory before querying its brands or WMIs. A name search can match several manufacturers, while a numeric ID targets one registered entity. 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.
One-based page number. Manufacturer endpoints return up to 100 records per page.

Sample response

{
  "Count": 1,
  "Message": "Response returned successfully",
  "Results": [
    {
      "Address": "2-3, Toranomon 2-Chome",
      "Address2": null,
      "City": "Minato-Ku",
      "ContactEmail": "[email protected]",
      "ContactFax": null,
      "ContactPhone": "+81 80 4888 7109",
      "Country": "JAPAN",
      "DBAs": null,
      "EquipmentItems": [],
      "LastUpdated": "/Date(1781312583703-0400)/",
      "ManufacturerTypes": [
        {
          "Name": "Completed Vehicle Manufacturer"
        }
      ],
      "Mfr_CommonName": "Honda",
      "Mfr_ID": 987,
      "Mfr_Name": "HONDA MOTOR CO., LTD.",
      "OtherManufacturerDetails": null,
      "PostalCode": "105-8404",
      "PrimaryProduct": null,
      "PrincipalFirstName": "Toshihiro Mibe",
      "PrincipalLastName": null,
      "PrincipalPosition": "President & CEO",
      "StateProvince": "Tokyo",
      "SubmittedName": "Liza Copeland",
      "SubmittedOn": "/Date(1750910400000-0400)/",
      "SubmittedPosition": "Administratiive Assistant",
      "VehicleTypes": [
        {
          "GVWRFrom": "Class 1A: 3,000 lb or less (1,360 kg or less)",
          "GVWRTo": "Class 1: 6,000 lb or less (2,722 kg or less)",
          "IsPrimary": false,
          "Name": "Motorcycle"
        },
        {
          "GVWRFrom": "Class 1B: 3,001 - 4,000 lb (1,360 - 1,814 kg)",
          "GVWRTo": "Class 1: 6,000 lb or less (2,722 kg or less)",
          "IsPrimary": false,
          "Name": "Passenger Car"
        },
        {
          "GVWRFrom": "Class 1: 6,000 lb or less (2,722 kg or less)",
          "GVWRTo": "Class 2: 6,001 - 10,000 lb (2,722 - 4,536 kg)",
          "IsPrimary": false,
          "Name": "Multipurpose Passenger Vehicle (MPV)"
        }
      ]
    }
  ],
  "SearchCriteria": null
}

Response result

Response structure

Inferred from examples
  • Countinteger
  • Messagestring
  • Resultsobject[]
    • Addressstring
    • Address2null
    • Citystring
    • ContactEmailstring
    • ContactFaxnull
    • ContactPhonestring
    • Countrystring
    • DBAsnull
    • EquipmentItemsunknown[]
    • LastUpdatedstring
    • ManufacturerTypesobject[]
      • Namestring
    • Mfr_CommonNamestring
    • Mfr_IDinteger
    • Mfr_Namestring
    • OtherManufacturerDetailsnull
    • PostalCodestring
    • PrimaryProductnull
    • PrincipalFirstNamestring
    • PrincipalLastNamenull
    • PrincipalPositionstring
    • StateProvincestring
    • SubmittedNamestring
    • SubmittedOnstring
    • SubmittedPositionstring
    • VehicleTypesobject[]
      • GVWRFromstring
      • GVWRTostring
      • IsPrimaryboolean
      • Namestring
  • SearchCriterianull

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

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