How to Use NHTSA vehicle data dictionary in VS Code
Returns vehicle attribute definitions and data types, or the accepted values for a lookup attribute. Use it to explain decoded specifications and translate NHTSA error codes into readable messages.
Prompts to try with NHTSA vehicle data dictionary in VS Code
Copy an example into VS Code, or ask in your own words.
Use NHTSA vehicle data dictionary to retrieve the definitions and types of vehicle attributes. Add readable descriptions for the attributes our inventory importer currently stores.
Use NHTSA vehicle data dictionary to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from NHTSA vehicle data dictionary and tell me what changed since last week.
Check NHTSA vehicle data dictionary and summarize what you find in three bullet points.
Pull the newest data from NHTSA vehicle data dictionary and give me the result as a table.
How to set up NHTSA vehicle data dictionary in VS Code
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Add the hosted server
Use Add to VS Code on the console's Agents & MCP page, or run:
code --add-mcp '{"name":"spiral","type":"http","url":"https://api.spiral.ai/mcp"}' - Sign in
VS Code asks you to sign in when it first starts the server: sign in to Spiral and click Authorize. No API key. Run MCP: List Servers from the Command Palette to check that Spiral is running.
Use the Spiral skill
- Send VS Code this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run NHTSA vehicle data dictionary
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "alexandria", "model": "vpic-nhtsa-dot-gov/vehicles/list_variables", "input": { "variable": "<variable>" } }'
Then paste one of the prompts above: VS Code finds NHTSA vehicle data dictionary on Spiral, shows the price and runs it.
NHTSA vehicle data dictionary providers and prices
Spiral runs NHTSA vehicle data dictionary through Alexandria. Open a card for today's price, with every fee included.
What can you do with NHTSA vehicle data dictionary in VS Code?
Build vehicle reference tables and inventory checks from NHTSA's manufacturer records and VIN data. A coding agent can map the returned identifiers and attribute definitions into the project's existing data structures.
Check dealer inventory descriptions
Decode inventory VINs individually or in batches, compare reported vehicle identity with listing descriptions, and explain attributes through the dictionary. Resolve unfamiliar prefixes, manufacturers, makes, and models before flagging a mismatch.
Standardize fleet vehicle records
Enrich a business fleet's VIN records with available vehicle specifications. Reconcile manufacturer entities, prefixes, make names, and model names, then use attribute definitions to build consistent reporting categories.
Build a vehicle research reference database
Create reference tables for manufacturers, makes, models, VIN prefixes, and attribute definitions. Use single and batch VIN decoding to attach vehicle characteristics to research records and investigate inconsistent identifiers.
Build vehicle catalog selection lists
Start with manufacturer records, resolve their business identities and makes, and populate model selections. Add manufacturer prefix references and dictionary definitions so catalog editors can interpret vehicle categories consistently.
Reconcile commercial trailer intake
Research trailer manufacturers and their makes, models, and WMI prefixes before matching incoming business inventory. Decode individual VIN exceptions or intake batches, using dictionary definitions to interpret trailer attributes.
Maintain vehicle reference tables
Compare successive retrievals of manufacturer, make, model, prefix, and dictionary records. Review changed business details and reference values before updating a vehicle catalog.
Explain vehicle identification results
Turn individual or batch decode results into readable vehicle summaries. Explain manufacturer prefixes, compare model names, and translate attribute definitions and decode errors for inventory reviewers.
More on NHTSA vehicle data dictionary and VS Code
Overview
NHTSA vehicle data dictionary in other agents
Questions about NHTSA vehicle data dictionary in VS Code
Can VS Code use NHTSA vehicle data dictionary?
Yes. Add Spiral to VS Code as an MCP server, and VS Code can find and run NHTSA vehicle data dictionary like any built-in tool.
How much does NHTSA vehicle data dictionary cost in VS Code?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your VS Code plan is separate.
Do I need an Alexandria account to use NHTSA vehicle data dictionary in VS Code?
No. Spiral runs NHTSA vehicle data dictionary on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up NHTSA vehicle data dictionary in VS Code?
About two minutes: add the hosted server, then sign in.
Does VS Code wait while NHTSA vehicle data dictionary runs?
NHTSA vehicle data dictionary runs in the background. VS Code starts the run, checks on it and gives you the json when it's ready.
Where does NHTSA get vPIC's information?
NHTSA codes manufacturer submissions into vPIC after reviewing them. The vehicle descriptions reflect manufacturer-reported information.
Does vPIC cover vehicles worldwide?
Its scope is vehicles intended for sale or importation into the United States. Foreign manufacturers can appear, but that does not make vPIC a complete catalog of their vehicles in other markets.
How far back does vPIC's vehicle coverage go?
NHTSA states that vPIC is intended for model years 1981 onward. Its API FAQ reports approximately 99% decoding confidence from 1995 onward for most major brands, which is a coverage estimate rather than a guarantee for every attribute.
How does new information reach vPIC?
Manufacturer submissions enter the data after NHTSA review. Freshness follows that submission and review process; a newly announced vehicle is not proof that its information has already been processed.
Does vPIC provide complete equipment information?
NHTSA explicitly says that missing decoded values do not mean a feature or technology is unavailable on the vehicle. Its records can therefore support an equipment check without establishing a complete installed-equipment list.
Start using NHTSA vehicle data dictionary in VS Code
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into VS Code:
set up https://spiral.ai/SKILL.md


