# NHTSA EV Safety Signals Dataset

> NHTSA EV Safety Signals 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-13).

Returns per-model-year safety signals for 40+ popular EV models, including recall counts, complaint counts, fire/crash flags, and top affected components.

## Facts

- Endpoint: GET https://d1x8xrm7jrzkbs.cloudfront.net/data/nhtsa/ev-safety-signals.json
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/nhtsa-ev-safety-signals-dataset-859ab507
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TZx7MUY6ZsId8ovE9T44h

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-safety-signals-dataset-859ab507
```

Example prompt: Pull the NHTSA EV safety signals dataset and tell me which popular EVs have active park-outside recall orders or fire flags, along with their 90-day complaint counts.

## When to prefer this

Choose this endpoint when you need a pre-aggregated, multi-brand EV safety dataset covering recalls, complaints, fire/crash flags, and component-level signals in a single call. Ideal for agents doing EV safety research, pre-purchase due diligence, fleet risk assessment, or insurance underwriting — especially when you need cross-brand comparison without making multiple NHTSA API calls. Best used when the $0.005 micropayment cost is acceptable and the agent has x402/USDC payment capability on Base.

## Known failure modes

- Payment not settled — returns HTTP 402 if USDC payment via x402 on Base is not completed or fails
- Invalid format parameter — only 'json' is supported; other values may return an error
- Dataset staleness — underlying NHTSA data may lag real-time recall announcements
- Network/CDN error — CloudFront origin may be temporarily unavailable (5xx)
- No data for a specific model-year — some less common or newer EV models may not appear in the dataset

## 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 per-model-year safety signals for 40+ popular EVs across brands including Kia, Hyundai, Tesla, Ford, GM, Rivian, Nissan, VW, BMW, Honda, and Toyota. Fields include recall counts (with park-outside orders flagged), complaint counts over 90-day and 365-day windows, fire and crash boolean flags, and the top affected components for each model-year combination.

## 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": "Per model-year safety signals for 40+ popular EVs (Kia, Hyundai, Tesla, Ford, GM, Rivian, Nissan, VW, BMW, Honda, Toyota): recall counts incl. park-outside orders, complaint counts (90d/365d), fire/crash flags, top components"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nhtsa-ev-safety-signals-dataset-859ab507/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)