NHTSA vPIC Canadian Vehicle Dimensions

Use the NHTSA vPIC Canadian Vehicle Dimensions API to retrieve Canadian vehicle dimension specifications used in collision investigation and reconstruction. Provide a year from 1971 onward and the make, optionally narrowing by model and choosing Metric or US units and request JSON output. The response contains the available vehicle dimensions, weights and specification references. Use the results to support dimension comparisons, organize reconstruction reference data, or enrich a vehicle specification catalog. The dataset concerns vehicle measurements and should not be treated as a complete ownership or maintenance history. 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
Specification year, 1971 or later.
Vehicle make, such as Acura or Honda.
Required output format for this OpenAny product. Use json; XML and CSV are not exposed by this configuration.
Optional parameters (2)
Optional model or additional specification descriptor.
Measurement units. Metric and US were both tested and produced converted values. The response uses Results[].Specs[] name/value entries, not flat dimension keys.

Sample response

{
  "Count": 1,
  "Message": "Results returned successfully",
  "Results": [
    {
      "Specs": [
        {
          "Name": "Make",
          "Value": "ACURA"
        },
        {
          "Name": "Model",
          "Value": "MDX 4DR SUV AWD /TECH/ELITE"
        },
        {
          "Name": "MYR",
          "Value": "10"
        },
        {
          "Name": "OL",
          "Value": "485"
        },
        {
          "Name": "OW",
          "Value": "199"
        },
        {
          "Name": "OH",
          "Value": "173"
        },
        {
          "Name": "WB",
          "Value": "275"
        },
        {
          "Name": "CW",
          "Value": "2064"
        },
        {
          "Name": "A",
          "Value": "117"
        },
        {
          "Name": "B",
          "Value": "183"
        },
        {
          "Name": "C",
          "Value": "42"
        },
        {
          "Name": "D",
          "Value": "85"
        },
        {
          "Name": "E",
          "Value": "126"
        },
        {
          "Name": "F",
          "Value": "100"
        },
        {
          "Name": "G",
          "Value": "110"
        },
        {
          "Name": "TWF",
          "Value": "172"
        },
        {
          "Name": "TWR",
          "Value": "172"
        },
        {
          "Name": "WD",
          "Value": "56/44"
        }
      ]
    }
  ],
  "SearchCriteria": "Year: 2011; Make: Acura; Model: MDX; Units: Metric"
}

Response result

Response structure

Inferred from examples
  • Countinteger
  • Messagestring
  • Resultsobject[]
    • Specsobject[]
      • Namestring
      • Valuestring
  • 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 Canadian Vehicle Dimensions with your agent

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