NHTSA vPIC Vehicle Variable Allowed Values
Use the NHTSA vPIC Vehicle Variable Allowed Values API to list accepted lookup values for a selected vPIC vehicle variable. Supply the complete variable name or its numeric identifier as the path value and request JSON output. The response returns the available value IDs, names and variable reference information. Use the results to label encoded vehicle attributes, build controlled selection menus, or interpret values produced by VIN decoding. This operation applies to lookup variables rather than arbitrary free-text or numeric attributes. 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...
| Seller | Pricing | Requests · 30d | Performance | Access |
|---|---|---|---|---|
nhtsa-vpicCurrent NHTSA vPIC Vehicle Variable Allowed Values · GET · View API reference | $0.001 / call | — | —successP50— |
Run sends a real API request. Charges follow the published API contract.
Response structure
CountintegerMessagestringResultsobject[]ElementNamestringIdintegerNamestring
SearchCriteriastring
// Inferred from response examples. Fields are optional and other fields may be returned.
export type ApiResponse = {
Count?: number;
Message?: string;
Results?: Array<{
ElementName?: string;
Id?: number;
Name?: string;
}>;
SearchCriteria?: string;
};- Method
- GET
- Endpoint
https://api.openany.si/v1/agent-apis/nhtsa-vpic/api/vehicles/GetVehicleVariableValuesList/{variable}- Content type
- application/json
- Authentication
Authorization: Bearer $OPENANY_API_KEY
curl \
'https://api.openany.si/v1/agent-apis/nhtsa-vpic/api/vehicles/GetVehicleVariableValuesList/2?format=json' \
-X GET \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json'Input parameters
Fields in this listing; additional options and input encoding can vary by provider.
| Parameter | Location | Type | Required | Description |
|---|---|---|---|---|
variable | URL path parameterspath | string | Yes | Complete lookup variable name or numeric variable ID represented as text. minLength: 1 · maxLength: 200 |
format | URL query parametersquery | string | Yes | Required output format for this OpenAny product. Use json; XML and CSV are not exposed by this configuration. enum: "json" |
Required markers inside a nested object or variant apply when that object or variant is used.
Sample response
Sample response · Documented HTTP 200 Example from the provider's documentation. Field values in your results will differ.
{
"Count": 9,
"Message": "Results returned successfully",
"Results": [
{
"ElementName": "Battery Type",
"Id": 1,
"Name": "Lead Acid/Lead"
},
{
"ElementName": "Battery Type",
"Id": 2,
"Name": "Nickel-Metal-Hydride/NiMH"
},
{
"ElementName": "Battery Type",
"Id": 3,
"Name": "Lithium-Ion/Li-Ion"
},
{
"ElementName": "Battery Type",
"Id": 4,
"Name": "Cobalt Dioxide/Cobalt"
},
{
"ElementName": "Battery Type",
"Id": 5,
"Name": "Nickle-Cobalt-Manganese/NCM"
},
{
"ElementName": "Battery Type",
"Id": 6,
"Name": "Nickle-Cobalt-Aluminum/NCA"
},
{
"ElementName": "Battery Type",
"Id": 7,
"Name": "Manganese Oxide Spinel/MnO"
},
{
"ElementName": "Battery Type",
"Id": 8,
"Name": "Iron Phosphate/FePo"
},
{
"ElementName": "Battery Type",
"Id": 9,
"Name": "Silicon"
}
],
"SearchCriteria": "Variable:2"
}Agent integration
Copy the resource contract without sharing an API key.
View API Markdown
# NHTSA vPIC Vehicle Variable Allowed Values
Use the NHTSA vPIC Vehicle Variable Allowed Values API to list accepted lookup values for a selected vPIC vehicle variable. Supply the complete variable name or its numeric identifier as the path value and request JSON output. The response returns the available value IDs, names and variable reference information. Use the results to label encoded vehicle attributes, build controlled selection menus, or interpret values produced by VIN decoding. This operation applies to lookup variables rather than arbitrary free-text or numeric attributes. The detail page provides supported parameters, request and response examples, coverage notes, and the configured per-call price.
## Available implementations
nhtsa-vpic · NHTSA vPIC Vehicle Variable Allowed Values: https://openany.si/markets/apis/capabilities/nhtsa-vpic-vehicle-variable-allowed-values?offering=00f89ba0-2786-4504-a4a2-c49bf9c2ed3f · $0.001 / call
## Selected API contract
Documentation: https://openany.si/markets/apis/capabilities/nhtsa-vpic-vehicle-variable-allowed-values
Method: GET
Endpoint: https://api.openany.si/v1/agent-apis/nhtsa-vpic/api/vehicles/GetVehicleVariableValuesList/{variable}
Price: $0.001 / call
Provider: nhtsa-vpic
Contract revision: 1
Price source: OpenAny public API contract and documented provider unit rates. Price update time: not supplied.
Use OPENANY_API_KEY from the environment. API Key calls use your shared balance.
## Prepared request
```bash
curl \
'https://api.openany.si/v1/agent-apis/nhtsa-vpic/api/vehicles/GetVehicleVariableValuesList/2?format=json' \
-X GET \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json'
```
## API contract
```json
{
"resource_type": "api",
"name": "NHTSA vPIC Vehicle Variable Allowed Values",
"endpoint": "https://api.openany.si/v1/agent-apis/nhtsa-vpic/api/vehicles/GetVehicleVariableValuesList/{variable}",
"method": "GET",
"content_type": "none",
"execution_mode": "sync",
"authentication": {
"type": "bearer",
"environment_variable": "OPENANY_API_KEY"
},
"inputs": [
{
"description": "Complete lookup variable name or numeric variable ID represented as text.",
"location": "path",
"max_length": 200,
"min_length": 1,
"name": "variable",
"nullable": false,
"required": true,
"type": "string"
},
{
"description": "Required output format for this OpenAny product. Use json; XML and CSV are not exposed by this configuration.",
"enum_values": [
"json"
],
"location": "query",
"name": "format",
"nullable": false,
"required": true,
"type": "string"
}
],
"billing": {
"currency": "USD",
"mode": "fixed",
"priceMicroUsd": "1000",
"rounding": null,
"unit": "call",
"unitQuantity": null
},
"examples": [
{
"http_status": 200,
"name": "Official example · Verified live response",
"request": {
"body": null,
"headers": {},
"path": {
"variable": "2"
},
"query": {
"format": "json"
}
},
"response_body": {
"Count": 9,
"Message": "Results returned successfully",
"Results": [
{
"ElementName": "Battery Type",
"Id": 1,
"Name": "Lead Acid/Lead"
},
{
"ElementName": "Battery Type",
"Id": 2,
"Name": "Nickel-Metal-Hydride/NiMH"
},
{
"ElementName": "Battery Type",
"Id": 3,
"Name": "Lithium-Ion/Li-Ion"
},
{
"ElementName": "Battery Type",
"Id": 4,
"Name": "Cobalt Dioxide/Cobalt"
},
{
"ElementName": "Battery Type",
"Id": 5,
"Name": "Nickle-Cobalt-Manganese/NCM"
},
{
"ElementName": "Battery Type",
"Id": 6,
"Name": "Nickle-Cobalt-Aluminum/NCA"
},
{
"ElementName": "Battery Type",
"Id": 7,
"Name": "Manganese Oxide Spinel/MnO"
},
{
"ElementName": "Battery Type",
"Id": 8,
"Name": "Iron Phosphate/FePo"
},
{
"ElementName": "Battery Type",
"Id": 9,
"Name": "Silicon"
}
],
"SearchCriteria": "Variable:2"
}
}
]
}
```Error handling
| Status | Next step |
|---|---|
400 | Check the offering and request fields. |
401 / 403 | Verify your credentials and access permissions. |
402 | Inspect the selected access mode and returned payment requirements. |
429 | Respect the returned rate limit and retry guidance. |
5xx | Inspect the error and usage record before retrying a paid operation. |
Official example · Verified live response
Example from the provider's documentation. Field values in your results will differ.
Prepare your environment
Use a terminal with cURL installed.
Use an OpenAny API key with shared-balance access. Confirm availability and price before running; a call may charge your balance.
Set the key in your terminal using the hidden prompt below. Keep its value out of source files and logs.
Terminal · macOS / Linuxprintf 'OpenAny API key: ' read -r -s OPENANY_API_KEY export OPENANY_API_KEY printf '\n'Run the request
Paste the complete command below into your terminal.
Values to replace before running 2
Review these request fields before running. Keep the published provider and request method unchanged.
variable- Complete lookup variable name or numeric variable ID represented as text.
format- Required output format for this OpenAny product. Use json; XML and CSV are not exposed by this configuration.
Terminal · cURLcurl \ 'https://api.openany.si/v1/agent-apis/nhtsa-vpic/api/vehicles/GetVehicleVariableValuesList/2?format=json' \ -X GET \ -H "Authorization: Bearer $OPENANY_API_KEY" \ -H 'Content-Type: application/json'Check the response
Sample response · Documented HTTP 200
Sample response{ "Count": 9, "Message": "Results returned successfully", "Results": [ { "ElementName": "Battery Type", "Id": 1, "Name": "Lead Acid/Lead" }, { "ElementName": "Battery Type", "Id": 2, "Name": "Nickel-Metal-Hydride/NiMH" }, { "ElementName": "Battery Type", "Id": 3, "Name": "Lithium-Ion/Li-Ion" }, { "ElementName": "Battery Type", "Id": 4, "Name": "Cobalt Dioxide/Cobalt" }, { "ElementName": "Battery Type", "Id": 5, "Name": "Nickle-Cobalt-Manganese/NCM" }, { "ElementName": "Battery Type", "Id": 6, "Name": "Nickle-Cobalt-Aluminum/NCA" }, { "ElementName": "Battery Type", "Id": 7, "Name": "Manganese Oxide Spinel/MnO" }, { "ElementName": "Battery Type", "Id": 8, "Name": "Iron Phosphate/FePo" }, { "ElementName": "Battery Type", "Id": 9, "Name": "Silicon" } ], "SearchCriteria": "Variable:2" }
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 Variable Allowed Values with your agent
Inspect endpoint contracts and confirm availability and pricing before a paid call.