[Integrations](https://spiral.ai/integrations) › [Devin](https://spiral.ai/integrations/devin) › [NHTSA vehicle makes](https://spiral.ai/integrations/devin/nhtsa-vehicle-makes)

# How to Use NHTSA vehicle makes in Devin

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.

|  |  |
| --- | --- |
| Model | NHTSA vehicle makes |
| Available through | Alexandria |
| Category | Public Records |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with NHTSA vehicle makes in Devin

- Use NHTSA vehicle makes to find Honda and Toyota. Create a reference table in this project with their returned make names and IDs.
- Use NHTSA vehicle makes to look this up and give me the result as a table. Save the result in ./assets.
- 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 Devin

Pick the way that suits you. Each takes about two minutes.

### Use Spiral's MCP server

1. **Add a custom MCP**: Open Customize › MCPs. Click + and choose New MCP. Fill in:

2. **Sign in to Spiral and approve**: In Customize › MCPs, open Spiral and choose Connect. Spiral opens: sign in, pick the organization and click Authorize. No API key.

3. **Check it**: On Spiral's configuration page, click Test tools. Devin lists Spiral's tools.

### Use the Spiral skill

1. **Send Devin this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run NHTSA vehicle makes**: One request; the result comes back by polling or a webhook.

```bash
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: Devin finds NHTSA vehicle makes on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/devin

## NHTSA vehicle makes tools and prices

- [NHTSA vPIC vehicle decoder · List makes](https://spiral.ai/tools/alexandria/vpic-nhtsa-dot-gov/vehicles/list_makes) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| limit | 1 to 500 | 100 | Only with `query`: maximum rows returned. |
| query |  | — | Substring to match against make names (case-insensitive) over the full make list. |
| model_year | 1900 to 2100 | — | Only with `manufacturer`: makes that manufacturer reported for this model year. |
| manufacturer |  | — | Manufacturer name fragment (`honda`) or numeric Mfr_ID (`987`). |
| vehicle_type |  | — | Vehicle type name or fragment as vPIC accepts it: `car`, `truck`, `motorcycle`, `bus`, `trailer`, `mpv`, `low speed vehicle`, `incomplete vehicle`. |

## What can you do with NHTSA vehicle makes in Devin?

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.

### 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.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Devin guides](https://spiral.ai/integrations/devin)

## NHTSA vehicle makes in other agents

- [Amp](https://spiral.ai/integrations/amp/nhtsa-vehicle-makes)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/nhtsa-vehicle-makes)
- [Claude](https://spiral.ai/integrations/claude-desktop/nhtsa-vehicle-makes)
- [Claude Code](https://spiral.ai/integrations/claude-code/nhtsa-vehicle-makes)
- [Cline](https://spiral.ai/integrations/cline/nhtsa-vehicle-makes)
- [Codex](https://spiral.ai/integrations/codex/nhtsa-vehicle-makes)
- [Cursor](https://spiral.ai/integrations/cursor/nhtsa-vehicle-makes)
- [dots](https://spiral.ai/integrations/dots/nhtsa-vehicle-makes)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/nhtsa-vehicle-makes)
- [Gemini](https://spiral.ai/integrations/gemini/nhtsa-vehicle-makes)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/nhtsa-vehicle-makes)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/nhtsa-vehicle-makes)
- [goose](https://spiral.ai/integrations/goose/nhtsa-vehicle-makes)
- [Grok](https://spiral.ai/integrations/grok/nhtsa-vehicle-makes)
- [Grok Build](https://spiral.ai/integrations/grok-build/nhtsa-vehicle-makes)
- [Hermes](https://spiral.ai/integrations/hermes/nhtsa-vehicle-makes)
- [Instinct](https://spiral.ai/integrations/instinct/nhtsa-vehicle-makes)
- [Manus](https://spiral.ai/integrations/manus/nhtsa-vehicle-makes)
- [Muse](https://spiral.ai/integrations/muse/nhtsa-vehicle-makes)
- [Muse Code](https://spiral.ai/integrations/muse-code/nhtsa-vehicle-makes)
- [n8n](https://spiral.ai/integrations/n8n/nhtsa-vehicle-makes)
- [Notion](https://spiral.ai/integrations/notion/nhtsa-vehicle-makes)
- [OpenClaw](https://spiral.ai/integrations/openclaw/nhtsa-vehicle-makes)
- [opencode](https://spiral.ai/integrations/opencode/nhtsa-vehicle-makes)
- [Perplexity](https://spiral.ai/integrations/perplexity/nhtsa-vehicle-makes)
- [Raycast](https://spiral.ai/integrations/raycast/nhtsa-vehicle-makes)
- [VS Code](https://spiral.ai/integrations/vscode/nhtsa-vehicle-makes)
- [Windsurf](https://spiral.ai/integrations/windsurf/nhtsa-vehicle-makes)
- [Zapier](https://spiral.ai/integrations/zapier/nhtsa-vehicle-makes)

## More Devin guides

- [NHTSA vehicle data dictionary](https://spiral.ai/integrations/devin/nhtsa-vehicle-data-dictionary)
- [NHTSA vehicle makes and models](https://spiral.ai/integrations/devin/nhtsa-vehicle-makes-and-models)
- [NHTSA vehicle complaints](https://spiral.ai/integrations/devin/nhtsa-vehicle-complaints)
- [NHTSA vehicle models](https://spiral.ai/integrations/devin/nhtsa-vehicle-models)
- [NHTSA vPIC vehicle decoder Decode vin](https://spiral.ai/integrations/devin/nhtsa-vpic-vehicle-decoder-decode-vin)
- [NHTSA vehicle recalls](https://spiral.ai/integrations/devin/nhtsa-vehicle-recalls)

## Questions about NHTSA vehicle makes in Devin

**Can Devin use NHTSA vehicle makes?**

Yes. Add Spiral to Devin as an MCP server, and Devin can find and run NHTSA vehicle makes like any built-in tool.

**How much does NHTSA vehicle makes cost in Devin?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Devin plan is separate.

**Do I need an Alexandria account to use NHTSA vehicle makes in Devin?**

No. Spiral runs NHTSA vehicle makes 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 makes in Devin?**

About two minutes: add a custom MCP, then sign in to Spiral and approve, then check it.

**Does Devin wait while NHTSA vehicle makes runs?**

NHTSA vehicle makes runs in the background. Devin 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.

