# ForgeMesh Vehicle Complaints Lookup

> ForgeMesh Vehicle Complaints Lookup 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).

Retrieves NHTSA consumer defect complaints for any US-market vehicle by VIN or year/make/model, including affected components, crash/fire involvement, injuries, deaths, and owner summaries.

## Facts

- Endpoint: POST https://x402.forgemesh.io/vehicle-complaints
- 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-complaints-lookup-8980ebb8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oQ4ZYNRcGQL8B-UjNaw6M

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-complaints-lookup-8980ebb8 -d '<json body>'
```

Example prompt: Can you pull up the most recent consumer complaints filed for a 2019 Ford F-150, specifically filtering for ENGINE issues? Show me up to 20 results including any crash or fire involvement.

## When to prefer this

Use this endpoint when you need raw NHTSA consumer complaint data for a specific US-market vehicle, especially for used car vetting, diagnostic research, or insurance claims analysis. Prefer this over generic reliability scores when you need granular incident-level detail including crash/fire flags, injury counts, and owner narratives. It supports both VIN-based lookup (for a specific car) and make/model/year queries (for broad model research), and allows filtering by component keyword for targeted diagnostics.

## Known failure modes

- No complaints found for the given VIN or make/model/year combination — returns empty array
- Invalid or unrecognized VIN format — returns error
- Ambiguous make/model combination with no NHTSA match — returns error or empty result
- Component keyword not matching any complaints — returns empty filtered result
- Request limit exceeds maximum of 50 — returns validation error

## How this service works

Consumer defect complaints on file for any US-market vehicle, by VIN or year/make/model: affected components, crash and fire involvement, injuries and deaths, incident and filing dates, and the owner's own summary — newest first, filterable by component keyword like BRAKES or ENGINE. The raw signal behind reliability scores. For used-car vetting, claims, and diagnostics agents.

## Output

Returns an array of complaint records sorted newest first, each containing: complaint ID, incident date, filing date, affected component, vehicle make/model/year, crash and fire involvement flags, injury and fatality counts, and the owner's free-text description of the problem.

## 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"
  },
  "component": {
   "type": "string",
   "description": "filter by component keyword, e.g. BRAKES, ENGINE, AIR BAGS"
  },
  "model_year": {
   "type": "string",
   "description": "4-digit year"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/forgemesh-vehicle-complaints-lookup-8980ebb8/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)