# ForgeMesh Vehicle Complaint Search

> ForgeMesh Vehicle Complaint Search 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).

Search the NHTSA consumer complaint database by VIN or year/make/model to retrieve defect reports with severity flags and owner narratives

## Facts

- Endpoint: POST https://x402.forgemesh.io/vehicle-complaint-search
- 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-complaint-search-d67e786c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RBzCXqSFgvnYTQrl6z8oB

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-complaint-search-d67e786c -d '<json body>'
```

Example prompt: Can you pull up all the NHTSA consumer complaints for a 2018 Honda Accord, filtering for brake issues — I want to see severity flags like crashes or injuries and read what owners reported?

## When to prefer this

Choose this endpoint when you need structured, severity-flagged complaint data from the official NHTSA consumer complaints database, especially when researching a specific vehicle by VIN or when you want to filter by component type. It is ideal for pre-purchase due diligence, fleet safety assessment, or any agent workflow that needs to quantify reported safety issues with crash/fire/injury/death flags and verbatim owner narratives. Prefer this over general web search for vehicle safety because it returns structured, authoritative government data with quantified severity indicators.

## Known failure modes

- Invalid or unrecognized VIN returns no results or a decoding error
- No complaints found for the specified vehicle returns an empty result set with count 0
- Invalid component keyword may return zero results if it doesn't match NHTSA taxonomy
- Missing both VIN and make/model/year combination results in a validation error
- NHTSA upstream API downtime may cause service unavailability

## How this service works

Search the official consumer defect-complaint file for any vehicle: pass VIN or year/make/model plus an optional component filter and get matching reports with severity flags (crash, fire, injuries, deaths) and owner narratives. Total matched count included — high counts are themselves a buying signal.

## Output

Returns a list of matching consumer complaint records (up to the requested limit) each containing: complaint details, severity flags indicating whether a crash, fire, injuries, or deaths were involved, and the owner's narrative description of the defect. Also includes the total count of matched complaints, which itself serves as a safety signal — high counts suggest a systemic issue.

## 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-complaint-search-d67e786c/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)