# NHTSA EV Owner Complaints Dataset

> NHTSA EV Owner Complaints Dataset is a paid API for AI agents from d1x8xrm7jrzkbs.cloudfront.net, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Returns NHTSA owner complaints filed in the last 365 days for electric vehicle model-years, including ODI numbers, affected components, and crash/fire/injury flags.

## Facts

- Endpoint: GET https://d1x8xrm7jrzkbs.cloudfront.net/data/nhtsa/ev-complaints.json
- 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/nhtsa-ev-owner-complaints-dataset-102e4afe
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eG6axwWjLtt50IgC9LzQY

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-ev-owner-complaints-dataset-102e4afe
```

Example prompt: Can you pull the NHTSA EV owner complaint data from the last 365 days — I want to see the ODI numbers, which components are flagged, and any complaints marked as crashes, fires, or injuries?

## When to prefer this

Choose this endpoint when you need pre-packaged, pay-per-request NHTSA EV complaint data without building your own NHTSA API integration. Ideal for agents that need recent EV safety signals (last 365 days) with structured crash/fire/injury flags ready for analysis. Best suited for use cases where micropayment-per-call economics (0.005 USDC) are acceptable and you want a turnkey dataset rather than raw government API access.

## Known failure modes

- Payment not settled in USDC via x402 protocol — request rejected with 402 Payment Required
- Invalid or unsupported format parameter — only 'json' is accepted
- Upstream NHTSA data unavailable — may return empty dataset or error
- CloudFront cache miss causing elevated latency on first fetch
- Stale data if NHTSA source hasn't refreshed within the rolling 365-day window

## How this service works

Pay-per-request datasets and Amazon Bedrock inference for AI agents, settled in USDC over the x402 protocol on Base.

## Output

A JSON object containing NHTSA owner complaints from the past 365 days for EV model-years, each record including the ODI complaint number, affected vehicle components, boolean flags for crash/fire/injury involvement, and a plain-text complaint summary.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "format": {
   "enum": [
    "json"
   ],
   "type": "string",
   "description": "Response format; only json is supported"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "description": "NHTSA owner complaints filed in the last 365 days for the same EV model-years (ODI number, components, crash/fire/injury flags, summary)"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nhtsa-ev-owner-complaints-dataset-102e4afe/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from d1x8xrm7jrzkbs.cloudfront.net](https://www.zero.xyz/host/d1x8xrm7jrzkbs.cloudfront.net/llms.txt)