NHTSA vPIC WMI Decode

Use the NHTSA vPIC WMI Decode API to identify the manufacturer information associated with a World Manufacturer Identifier. Supply either a three-character WMI or the documented six-character low-volume identifier and request JSON output. The response provides the manufacturer, available vehicle type, and related registry information. Use the results to recognize VIN prefixes, validate supplier reference data, or organize manufacturer records. The six-character form combines VIN positions one through three and twelve through fourteen. 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
Three-character WMI, or the documented six-character WMI assembled from VIN positions 1-3 and 12-14.
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": [
    {
      "CommonName": "Ford",
      "CreatedOn": "2015-03-23",
      "DateAvailableToPublic": "2015-01-01",
      "Make": "FORD",
      "ManufacturerName": "FORD MOTOR COMPANY",
      "ParentCompanyName": "",
      "URL": "http://www.ford.com/",
      "UpdatedOn": null,
      "VehicleType": "Incomplete Vehicle"
    }
  ],
  "SearchCriteria": "WMI:1FD"
}

Response result

Response structure

Inferred from examples
  • Countinteger
  • Messagestring
  • Resultsobject[]
    • CommonNamestring
    • CreatedOnstring
    • DateAvailableToPublicstring
    • Makestring
    • ManufacturerNamestring
    • ParentCompanyNamestring
    • URLstring
    • UpdatedOnnull
    • VehicleTypestring
  • 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 WMI Decode with your agent

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