# NHTSA Vehicle Complaints Lookup

> NHTSA Vehicle Complaints Lookup is a paid API for AI agents from autoscrape-api-seven.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Retrieves consumer-submitted vehicle safety complaints from the NHTSA database, filterable by make, model, year, and component

## Facts

- Endpoint: GET https://autoscrape-api-seven.vercel.app/x402/v1/nhtsa-vehicle-complaints
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/nhtsa-vehicle-complaints-lookup-ed5ad78c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RunoSzi1w0eojwlb4atvC

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 nhtsa-vehicle-complaints-lookup-ed5ad78c
```

Example prompt: Can you pull up NHTSA consumer safety complaints for the 2020 Toyota Camry, specifically ones related to the ENGINE component — show me up to 5 results?

## When to prefer this

Use this endpoint when an agent needs to query NHTSA's official consumer complaint database for a specific vehicle, especially when researching used car safety history, investigating recall-related issues, or enriching automotive data pipelines. Prefer this over general web search when structured, machine-readable complaint records with ODI numbers are needed. Best suited for point lookups on a specific make/model/year rather than bulk analysis.

## Known failure modes

- No complaints found for the specified make/model/year combination returns empty results array
- Invalid or misspelled vehicle make/model may return zero results without an explicit error
- maxResults is capped at 10 regardless of the value provided
- Missing all query parameters defaults to Toyota results only
- Network or upstream NHTSA API outage may cause timeout or 5xx error
- Payment failure via x402 protocol returns 402 Payment Required

## How this service works

No-key evaluation APIs for public data and utilities: business filings, permits, bankruptcy dockets, NPI providers, HTTP status checks, sitemap URL extraction, SEC EDGAR, IRS 990, WHOIS, and validation. Paid x402 access is live.

## Output

Returns a JSON object with a count of matching complaints and an array of complaint records, each containing the vehicle make, model, model year, ODI complaint number, and evidence type (e.g. consumer_submitted_complaint), plus a setupStatus field indicating whether results were found.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "count": 1,
  "results": [
   {
    "make": "TOYOTA",
    "model": "CAMRY",
    "modelYear": 2020,
    "odiNumber": 12345678,
    "evidenceType": "consumer_submitted_complaint"
   }
  ],
  "setupStatus": "found"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nhtsa-vehicle-complaints-lookup-ed5ad78c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from autoscrape-api-seven.vercel.app](https://www.zero.xyz/host/autoscrape-api-seven.vercel.app/llms.txt)