vin_decode
Decode a 17-character Vehicle Identification Number: offline structure check (allowed characters, ISO 3779 check digit, region and WMI, model-year code) plus NHTSA vPIC decoding (make, model, model year, trim, body class, vehicle type, doors, drive type, engine cylinders/displacement/fuel, transm...
This record as markdown: /tools/com-it-scorptech-x402/vin-decode.md
What vin_decode does on ScorpTech x402 API
AI agents call vin_decode to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
vin | string | Yes | 17-character VIN (I, O and Q are not allowed) |
year | integer | — | Optional model year hint (resolves the 30-year cycle of the 10th-character year code) |
recalls | boolean | — | Include NHTSA recalls for the decoded make/model/year (default false) |
Parameters from the server's own tool schema.
Why vin_decode is rated Low
Even though vin_decode only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs vin_decode safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vin_decode, this is the rule to start with:
vin_decode is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every vin_decode call is checked against it from then on.
Questions about vin_decode
Decode a 17-character Vehicle Identification Number: offline structure check (allowed characters, ISO 3779 check digit, region and WMI, model-year code) plus NHTSA vPIC decoding (make, model, model year, trim, body class, vehicle type, doors, drive type, engine cylinders/displacement/fuel, transmission, manufacturer, plant city/country, GVWR, safety equipment) and optional open NHTSA safety recalls for that make/model/year. Public US government data. Price: $0.01 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/vin-decode. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
vin_decode accepts 3 parameters: vin, year, recalls. Required: vin. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for vin_decode: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches ScorpTech x402 API. Nothing to install.
vin_decode is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the vin_decode rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for vin_decode. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
vin_decode is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue