How to Use NHTSA vehicle makes in dots
Returns make names and identifiers from vPIC, with manufacturer or vehicle-type discovery where requested. Use it to resolve the source's make names before building a model catalog.
Prompts to try with NHTSA vehicle makes in dots
Copy an example into dots, or ask in your own words.
Each Monday, use NHTSA vehicle makes to find make names containing Honda. Compare the returned names and IDs with the previous report and summarize additions or removals.
Every Monday at 9am: use NHTSA vehicle makes to look this up and give me the result as a table.
Pull the latest numbers from NHTSA vehicle makes and tell me what changed since last week.
Check NHTSA vehicle makes and summarize what you find in three bullet points.
Pull the newest data from NHTSA vehicle makes and give me the result as a table.
How to set up NHTSA vehicle makes in dots
Pick the way that suits you. Each takes about two minutes.
Use the Spiral skill
- Send dots 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 Spiral's MCP server
- Create an API key
In the console, open API keys and create a key for your dot. Copy it.
- Send your dot this message
Your dot reads Spiral's skill and asks for your API key.
set up https://spiral.ai/SKILL.md
- Give your dot the key
When your dot asks for the key, add it where your dot keeps secrets, never in the chat itself.
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 makes
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_makes", "input": { "manufacturer": "<manufacturer>" } }'
Then paste one of the prompts above: dots finds NHTSA vehicle makes on Spiral, shows the price and runs it.
NHTSA vehicle makes providers and prices
Spiral runs NHTSA vehicle makes through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask dots for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Limit | 1 to 500 | 100 | Only with |
| Model year | 1900 to 2100 | Only with |
Every API field of NHTSA vPIC vehicle decoder · List makes is on its tool page: open its card above.
What can you do with NHTSA vehicle makes in dots?
Produce recurring reports of changes in NHTSA vehicle reference records. An agent can compare successive retrievals of manufacturers, makes, models, prefixes, or definitions and highlight differences for catalog review.
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.
Resolve manufacturer names in supplier records
Compare a supplier's manufacturing identity with the public registry. Use business details, make associations, and WMI records to distinguish similarly named entities and explain unfamiliar VIN prefixes.
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.
More on NHTSA vehicle makes and dots
Overview
NHTSA vehicle makes in other agents
Questions about NHTSA vehicle makes in dots
Can dots use NHTSA vehicle makes?
Yes. Add Spiral to dots as an MCP server, and dots can find and run NHTSA vehicle makes like any built-in tool.
How much does NHTSA vehicle makes cost in dots?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your dots plan is separate.
Do I need an Alexandria account to use NHTSA vehicle makes in dots?
You need no Alexandria account. dots uses one Spiral API key for every tool, and Spiral runs NHTSA vehicle makes on its own Alexandria account.
How long does it take to set up NHTSA vehicle makes in dots?
About two minutes: create an API key, then send your dot this message, then give your dot the key.
Does dots wait while NHTSA vehicle makes runs?
NHTSA vehicle makes runs in the background. dots 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 makes in dots
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into dots:
set up https://spiral.ai/SKILL.md


