# VIN Recall Lookup by x402.forgemesh.io

> VIN Recall Lookup by x402.forgemesh.io is a paid API for AI agents from x402.forgemesh.io, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Decodes a VIN and returns all matching NHTSA safety recall campaigns with component details, failure risks, and remedy information.

## Facts

- Endpoint: POST https://x402.forgemesh.io/recalls-by-vin
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vin-recall-lookup-by-x402-forgemesh-io-583eb157
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2U19OgiqPlb6EoQRdQj0A

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability vin-recall-lookup-by-x402-forgemesh-io-583eb157 -d '<json body>'
```

Example prompt: Can you check if my 2019 Ford F-150 has any open safety recalls? The VIN is 1FTEW1EP4KFA12345 — I especially want to know if there's a fire risk that requires parking outside.

## When to prefer this

Use this endpoint when you need structured, per-campaign recall detail for a specific vehicle identified by VIN. It is preferable to manual NHTSA web lookups when building automated vehicle safety checks, pre-purchase due-diligence agents, or fleet management workflows. Especially valuable when fire-risk flagging is needed in a single API call without post-processing.

## Known failure modes

- Invalid or malformed VIN returns an error or empty result set
- VIN not found in NHTSA database returns empty recalls array
- Limit parameter out of range (must be 1–50) returns validation error
- Network or upstream NHTSA API outage results in a 5xx error
- Very new vehicles may not yet have recalls indexed

## How this service works

Recall check straight from a VIN: the vehicle is decoded automatically, then matched against official safety recall campaigns — campaign number, component, what can fail, the risk, and the free remedy owed by the manufacturer. Fire-risk park-outside campaigns are flagged. One call, structured JSON.

## Output

Returns a structured JSON array of recall campaigns matching the decoded VIN, each containing the NHTSA campaign number, affected component, description of what can fail, the associated safety risk, and the free remedy owed by the manufacturer. Fire-risk park-outside campaigns are explicitly flagged.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "vin": {
   "type": "string",
   "description": "VIN — decoded automatically (alternative to make/model/model_year)"
  },
  "make": {
   "type": "string",
   "description": "e.g. honda"
  },
  "limit": {
   "type": "integer",
   "maximum": 50,
   "minimum": 1
  },
  "model": {
   "type": "string",
   "description": "e.g. accord"
  },
  "model_year": {
   "type": "string",
   "description": "4-digit year"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vin-recall-lookup-by-x402-forgemesh-io-583eb157/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.forgemesh.io](https://www.zero.xyz/host/x402.forgemesh.io/llms.txt)