# Datamancer NHTSA Recall Campaign Lookup

> Datamancer NHTSA Recall Campaign Lookup is a paid API for AI agents from agents.datamancer.io, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-16).

Retrieves detailed information about a specific NHTSA vehicle recall campaign by its campaign number

## Facts

- Endpoint: GET https://agents.datamancer.io/api/v1/paid/recalls/campaign
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/datamancer-nhtsa-recall-campaign-lookup-fee5beef
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_T_GurbOu9jUN7DkFWnO7O

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 datamancer-nhtsa-recall-campaign-lookup-fee5beef
```

Example prompt: Can you pull up the details for NHTSA recall campaign number 23V123000? I want to know what vehicles are affected and what the defect is.

## When to prefer this

Use this endpoint when you have a specific NHTSA campaign number and need structured recall details programmatically, especially within an automotive data pipeline. Prefer this over manual NHTSA web lookups when building automated vehicle safety checks, VIN decoders, or fleet compliance workflows. This is ideal when paired with VIN decode results that surface campaign numbers requiring further investigation.

## Known failure modes

- Invalid or non-existent campaign number returns an error or empty result
- Missing required 'id' query parameter returns a 400 bad request
- Payment not provided or invalid results in 402 Payment Required
- NHTSA upstream service unavailability causes timeout or 503

## How this service works

Datamancer agents API. Public-records warehouse.

## Output

Returns a JSON object with recall campaign details sourced from NHTSA, including information about the campaign such as affected vehicle makes/models/years, the nature of the defect, potential safety risk, and the remedy or corrective action associated with the recall.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "headers": {
     "type": "object",
     "additionalProperties": {
      "type": "string"
     }
    },
    "queryParams": {
     "type": "object",
     "required": [
      "id"
     ],
     "properties": {
      "id": {
       "type": "string",
       "description": "NHTSA campaign number"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/datamancer-nhtsa-recall-campaign-lookup-fee5beef/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agents.datamancer.io](https://www.zero.xyz/host/agents.datamancer.io/llms.txt)