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

Manus · Public Records

How to Use NHTSA WMI decoder in Manus

Returns manufacturer, make, and vehicle-type information associated with a World Manufacturer Identifier. Use it to identify a VIN prefix before researching a complete vehicle.

Prompts to try with NHTSA WMI decoder in Manus

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

Use NHTSA WMI decoder to look up 1FD. Explain the manufacturer, make, and vehicle type returned.

NHTSA WMI decoderManus
Try asking
  • Use NHTSA WMI decoder to look this up and give me the result as a table.

  • Pull the latest numbers from NHTSA WMI decoder and tell me what changed since last week.

  • Check NHTSA WMI decoder and summarize what you find in three bullet points.

  • Pull the newest data from NHTSA WMI decoder and give me the result as a table.

How to set up NHTSA WMI decoder in Manus

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

Use the Manus connector

  1. Add a custom MCP connector

    In Manus open Settings › Connectors (or the connectors icon under the chat box), then Add connectors › Custom MCP and Add MCP by URL. Name it Spiral, set Transport to HTTP and paste this Server URL:

    https://api.spiral.ai/mcp
  2. Sign in to Spiral and approve

    Manus asks you to sign in the first time it uses Spiral. Spiral opens: sign in, pick the organization and click Authorize. No API key. Spiral gives the connection its own key; Manus never sees it, and you can remove it under Settings › Connected apps in the console.

Use the Spiral skill

  1. Send Manus 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 WMI decoder

    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_wmi",
        "input": {
          "wmi": "<wmi>"
        }
      }'

Then paste one of the prompts above: Manus finds NHTSA WMI decoder on Spiral, shows the price and runs it.

NHTSA WMI decoder providers and prices

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

AlexandriaPublic Records
NHTSA vPIC vehicle decoder · Decode wmi
vpic-nhtsa-dot-gov/vehicles/decode_wmi

What can you do with NHTSA WMI decoder in Manus?

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.

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.

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 WMI decoder in Manus

Can Manus use NHTSA WMI decoder?

Yes. Add Spiral to Manus as an MCP server, and Manus can find and run NHTSA WMI decoder like any built-in tool.

How much does NHTSA WMI decoder cost in Manus?

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

Do I need an Alexandria account to use NHTSA WMI decoder in Manus?

No. Spiral runs NHTSA WMI decoder 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 WMI decoder in Manus?

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

Does Manus wait while NHTSA WMI decoder runs?

NHTSA WMI decoder runs in the background. Manus 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 WMI decoder in Manus

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

Paste this into Manus:

Set up Manus

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