# ForgeMesh Car Problem Reports

> ForgeMesh Car Problem Reports 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 owner-reported NHTSA defect/complaint records for a US vehicle by VIN or year/make/model, optionally filtered by component

## Facts

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

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-problem-reports-d43ee709 -d '<json body>'
```

Example prompt: Can you pull up all the owner-reported problems for a 2019 Honda Accord — specifically any complaints about the transmission or brakes? Give me up to 30 results.

## When to prefer this

Use this endpoint when you need structured, owner-reported defect and complaint data for a specific US vehicle — especially for pre-purchase due diligence, spotting recurring mechanical failures across a make/model, or correlating a repair issue with known pattern failures. Prefer this over general web search when you need structured, queryable complaint records with component-level filtering and incident dates rather than unstructured forum posts or reviews.

## Known failure modes

- No complaints found for the specified make/model/year combination — returns empty list
- Invalid or unrecognized VIN — may fail to decode or return no results
- Component filter keyword too specific — may return zero matches even if related complaints exist
- Model year out of range or vehicle not in NHTSA database — no data returned
- Limit parameter out of range (must be 1–50) — validation error

## How this service works

Owner-reported problem lookup for US vehicles: every defect report on file for a year/make/model with component, incident date, and a plain-language description of what went wrong. VIN input is auto-identified. Use it to spot pattern failures — transmissions, airbags, brakes — before purchase or repair.

## Output

A list of owner-reported complaint records, each including the affected component (e.g. BRAKES, AIR BAGS, ENGINE), the date of the incident, and a plain-language description of what the owner experienced. Results can be filtered by component keyword and capped at a specified limit.

## 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-problem-reports-d43ee709/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)