[Integrations](https://spiral.ai/integrations) › [Muse Code](https://spiral.ai/integrations/muse-code) › [NHTSA manufacturer directory](https://spiral.ai/integrations/muse-code/nhtsa-manufacturer-directory)

# How to Use NHTSA manufacturer directory in Muse Code

Returns manufacturer IDs, names, countries, and reported vehicle types in pages of 100 records. Use it to build a registry reference table before retrieving individual manufacturer details.

|  |  |
| --- | --- |
| Model | NHTSA manufacturer directory |
| 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 manufacturer directory in Muse Code

- Use NHTSA manufacturer directory to retrieve the first page of manufacturers. Create a sample import fixture containing business names, IDs, countries, and reported vehicle types.
- Use NHTSA manufacturer directory to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from NHTSA manufacturer directory and tell me what changed since last week.
- Check NHTSA manufacturer directory and summarize what you find in three bullet points.
- Pull the newest data from NHTSA manufacturer directory and give me the result as a table.

## How to set up NHTSA manufacturer directory in Muse Code

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

### Use Spiral's MCP server

1. **Install Muse Code**

```bash
curl -fsSL https://dev.meta.ai/install.sh | bash
```

2. **Ask Muse to add the server**: Start `muse` and ask:

```text
Add the Spiral MCP server at https://api.spiral.ai/mcp
```

3. **Sign in**: In your terminal, run:

```bash
muse mcp login spiral
```

### Use the Spiral skill

1. **Send Muse Code 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 manufacturer directory**: 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_manufacturers",
    "input": {
      "page": 1
    }
  }'
```

Then paste one of the prompts above: Muse Code finds NHTSA manufacturer directory on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/muse-code

## NHTSA manufacturer directory tools and prices

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

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| page | 1 to 10000 | 1 | 1-based page of 100 rows. |
| manufacturer_type |  | — | vPIC ManufacturerType filter, e.g. `Intermediate`, `Completed Vehicle Manufacturer`, `Incomplete Vehicles`, `Alterer`. |

## What can you do with NHTSA manufacturer directory in Muse 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.

### 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 Muse Code guides](https://spiral.ai/integrations/muse-code)

## NHTSA manufacturer directory in other agents

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

## More Muse Code guides

- [NHTSA manufacturer details](https://spiral.ai/integrations/muse-code/nhtsa-manufacturer-details)
- [NHTSA recall campaign details](https://spiral.ai/integrations/muse-code/nhtsa-recall-campaign-details)
- [NHTSA manufacturer WMI list](https://spiral.ai/integrations/muse-code/nhtsa-manufacturer-wmi-list)
- [NHTSA vPIC vehicle decoder Decode vin](https://spiral.ai/integrations/muse-code/nhtsa-vpic-vehicle-decoder-decode-vin)
- [NHTSA complaint details](https://spiral.ai/integrations/muse-code/nhtsa-complaint-details)
- [NHTSA vehicle complaints](https://spiral.ai/integrations/muse-code/nhtsa-vehicle-complaints)

## Questions about NHTSA manufacturer directory in Muse Code

**Can Muse Code use NHTSA manufacturer directory?**

Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run NHTSA manufacturer directory like any built-in tool.

**How much does NHTSA manufacturer directory cost in Muse 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 Muse Code plan is separate.

**Do I need an Alexandria account to use NHTSA manufacturer directory in Muse Code?**

No. Spiral runs NHTSA manufacturer directory 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 manufacturer directory in Muse Code?**

About two minutes: install Muse Code, then ask Muse to add the server, then sign in.

**Does Muse Code wait while NHTSA manufacturer directory runs?**

NHTSA manufacturer directory runs in the background. Muse 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.

