Spiral gives your agent every tool with one account. Browse the tools →

Muse · Public Records

How to Use NHTSA vPIC vehicle decoder Decode vin in Muse

Returns vehicle identity and available specifications decoded from manufacturer-reported VIN patterns, including engine and assembly information. Use it to check one vehicle against an inventory or listing record.

Prompts to try with NHTSA vPIC vehicle decoder Decode vin in Muse

Copy an example into Muse, or ask in your own words.

Use NHTSA vPIC vehicle decoder Decode vin to look this up and give me the result as a table.

NHTSA vPIC vehicle decoder Decode vinMuse
Try asking
  • Pull the latest numbers from NHTSA vPIC vehicle decoder Decode vin and tell me what changed since last week.

  • Check NHTSA vPIC vehicle decoder Decode vin and summarize what you find in three bullet points.

  • Pull the newest data from NHTSA vPIC vehicle decoder Decode vin and give me the result as a table.

  • Check NHTSA vPIC vehicle decoder Decode vin every morning and tell me only when something changed.

How to set up NHTSA vPIC vehicle decoder Decode vin in Muse

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

Use the Muse connector

  1. Create an API key

    Create one under API keys in the Spiral console.

  2. Send Muse this message

    Muse reads Spiral's skill and asks for an API key.

    set up https://spiral.ai/SKILL.md
  3. Give Muse the key

    Paste the key when Muse asks for it, never in the chat itself.

Use the Spiral skill

  1. Send Muse 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.

    npx -y spiral-cli@latest init

Call the Spiral API

  1. Create an API key

    In the console, under API keys.

  2. Run NHTSA vPIC vehicle decoder Decode vin

    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/decode_vin",
        "input": {
          "vin": "<vin>"
        }
      }'

Then paste one of the prompts above: Muse finds NHTSA vPIC vehicle decoder Decode vin on Spiral, shows the price and runs it.

NHTSA vPIC vehicle decoder Decode vin providers and prices

Spiral runs NHTSA vPIC vehicle decoder Decode vin through Alexandria. Open a card for today's price, with every fee included.

AlexandriaPublic Records
NHTSA vPIC vehicle decoder · Decode vin
vpic-nhtsa-dot-gov/vehicles/decode_vin

Settings you can ask for

Ask Muse for any of these in your prompt.

SettingAllowed valuesDefaultDescription
Extendedon or off

Use DecodeVinValuesExtended, which adds NCSA mapping fields and additional error details.

Model year1900 to 2100

Model year hint sent as vPIC's modelyear; improves partial decodes and disambiguates the 10th VIN character.

Every API field of NHTSA vPIC vehicle decoder · Decode vin is on its tool page: open its card above.

What can you do with NHTSA vPIC vehicle decoder Decode vin in Muse?

Get a readable vehicle or manufacturer research brief from NHTSA's public records. A chat app can explain returned specifications, manufacturing entities, and reference definitions without requiring you to interpret the raw response.

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.

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.

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.

Questions about NHTSA vPIC vehicle decoder Decode vin in Muse

Can Muse use NHTSA vPIC vehicle decoder Decode vin?

Yes. Add Spiral to Muse as an MCP server, and Muse can find and run NHTSA vPIC vehicle decoder Decode vin like any built-in tool.

How much does NHTSA vPIC vehicle decoder Decode vin cost in Muse?

$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 plan is separate.

Do I need an Alexandria account to use NHTSA vPIC vehicle decoder Decode vin in Muse?

You need no Alexandria account. Muse uses one Spiral API key for every tool, and Spiral runs NHTSA vPIC vehicle decoder Decode vin on its own Alexandria account.

How long does it take to set up NHTSA vPIC vehicle decoder Decode vin in Muse?

About two minutes: create an API key, then send Muse this message, then give Muse the key.

Does Muse wait while NHTSA vPIC vehicle decoder Decode vin runs?

NHTSA vPIC vehicle decoder Decode vin runs in the background. Muse 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.

Get started

Start using NHTSA vPIC vehicle decoder Decode vin in Muse

One Spiral account for every tool your agent needs. No subscription; you pay per run.

Paste this into Muse:

Set up Muse

set up https://spiral.ai/SKILL.md
Are you an AI agent? See setup options