# ForgeMesh Vehicle Safety Recall Check

> ForgeMesh Vehicle Safety Recall Check 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).

Looks up all open NHTSA safety recall campaigns for a vehicle by VIN or year/make/model, returning defect summaries, affected components, safety consequences, remedies, and fire/do-not-drive flags.

## Facts

- Endpoint: POST https://x402.forgemesh.io/vehicle-recalls
- 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/forgemesh-vehicle-safety-recall-check-52b1220c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3fbjTEHCBRNC81i96-g2h

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 forgemesh-vehicle-safety-recall-check-52b1220c -d '<json body>'
```

Example prompt: Can you check if there are any open safety recalls on my 2018 Toyota Camry — the VIN is 4T1B11HK0JU123456? I want to know about any fire risks or do-not-drive flags especially.

## When to prefer this

Choose this endpoint when you need authoritative, NHTSA-sourced vehicle recall data with structured per-campaign detail including safety severity flags (do-not-drive, fire risk). It is ideal for pre-purchase inspections, fleet compliance workflows, and dealer agents that need to screen vehicles quickly. Prefer this over generic web search when you need structured, reliable recall data with consistent fields rather than scraped news articles or manufacturer pages.

## Known failure modes

- Invalid or malformed VIN returns a decode error or empty result
- VIN not found in NHTSA database returns zero recalls (not an error — valid answer)
- Missing both VIN and make/model/year combination returns a validation error
- Year outside supported range may return no data
- Rate limiting or upstream NHTSA API unavailability causes a 5xx error
- Limit parameter exceeding 50 is rejected with a validation error

## How this service works

Official vehicle safety recall check by VIN or year/make/model: every open recall campaign with affected component, defect summary, safety consequence, remedy, report date, and do-not-drive / park-outside fire-risk flags. Pass a VIN and the vehicle is identified automatically. Zero recalls is a real answer. For pre-purchase checks, fleet compliance, and dealer agents.

## Output

A list of open recall campaigns for the matched vehicle, each including the recall campaign ID, affected component, defect description, potential safety consequence, recommended remedy, report date, and boolean flags for do-not-drive and park-outside fire-risk advisories. If no recalls are found, a confirmed zero-recall result is returned.

## 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/forgemesh-vehicle-safety-recall-check-52b1220c/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)