# NHTSA EV Recall Records (Agent Factory)

> NHTSA EV Recall Records (Agent Factory) 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 full NHTSA recall records for electric vehicle model-years, including campaign details, affected components, summaries, consequences, remedies, and park-outside/park-it safety flags.

## Facts

- Endpoint: GET https://d1x8xrm7jrzkbs.cloudfront.net/data/nhtsa/ev-recalls.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-recall-records-agent-factory-28fb0bad
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rNOrVSF7O_s511rM5Bxxu

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-recall-records-agent-factory-28fb0bad
```

Example prompt: Pull the latest NHTSA recall records for electric vehicles — I need the full dataset including campaign details, affected components, consequences, remedies, and any park-outside or park-it safety flags, in JSON format.

## When to prefer this

Choose this endpoint when you need a ready-to-consume, pay-per-call JSON dataset of NHTSA EV recall records without standing up your own NHTSA API integration. Ideal for AI agents that need structured recall data on-demand, settled cheaply in USDC via x402 on Base, with no subscription or API key required. Prefer this over direct NHTSA API calls when simplicity of integration and micropayment-based access matter.

## Known failure modes

- Payment not settled in USDC via x402 — returns HTTP 402 Payment Required
- Invalid or unsupported format parameter (only 'json' is accepted) — returns error
- CloudFront distribution unavailable or origin timeout — returns HTTP 503 or 504
- Dataset temporarily stale or unavailable upstream from NHTSA — may return outdated or empty records
- Network connectivity issues — generic HTTP connection errors

## 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 the full set of NHTSA recall records for electric vehicle model-years. Each record includes the recall campaign identifier, affected component, a plain-language summary of the defect, the consequence of the defect, the recommended remedy, and boolean-style park-outside and park-it safety flags indicating urgency of action.

## 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": "Full NHTSA recall records (campaign, component, summary, consequence, remedy, park-outside/park-it flags) for the same EV model-years"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nhtsa-ev-recall-records-agent-factory-28fb0bad/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)