# ForgeMesh Car Complaints API

> ForgeMesh Car Complaints API 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).

Returns structured NHTSA-style owner complaint records for a given vehicle year/make/model or VIN, including component, narrative, crash/fire flags, injuries, and dates.

## Facts

- Endpoint: POST https://x402.forgemesh.io/car-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-car-complaints-api-a99e20d3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_L24JdDDEpIH8p2iJzgp36

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-car-complaints-api-a99e20d3 -d '<json body>'
```

Example prompt: Pull up the 10 most recent brake complaints for a 2019 Honda CR-V and flag any that involved a crash or fire.

## When to prefer this

Use this endpoint when you need real owner-reported complaint data for a specific vehicle before purchase, during diagnosis, or for safety research. It's ideal when you have a VIN or year/make/model and want structured NHTSA-sourced complaint records with crash and fire flags. Prefer this over general web search when you need machine-readable, filterable complaint data rather than anecdotal forum posts.

## Known failure modes

- No complaints found for the given vehicle — returns empty array
- Invalid or unrecognized VIN — may return no results or an error
- Unrecognized make/model/year combination — no records returned
- Component keyword filter too narrow — returns empty results
- Exceeding limit parameter bounds (max 50) — validation error

## How this service works

Car complaint records: what real owners reported failing on a given year/make/model or VIN — component, narrative summary, crash/fire flags, injuries, and dates, newest first as structured JSON. Filter by component keyword to target a suspected problem area before buying or diagnosing.

## Output

A JSON array of complaint records sorted newest first, each containing the component name, a narrative description of the problem, crash and fire boolean flags, injury count, and complaint date. Results are limited to the requested count (up to 50) and optionally filtered by component keyword.

## 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-car-complaints-api-a99e20d3/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)