# Datamancer Vehicle Recalls Lookup

> Datamancer Vehicle Recalls Lookup is a paid API for AI agents from agents.datamancer.io, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).

Retrieves active safety recall information for a specific vehicle by make, model, and year

## Facts

- Endpoint: GET https://agents.datamancer.io/api/v1/paid/recalls
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/datamancer-vehicle-recalls-lookup-7db7f654
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aEj3sA1BLYI28c4y42Bb4

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-vehicle-recalls-lookup-7db7f654
```

Example prompt: Can you check if there are any active safety recalls on my 2019 Ford F-150?

## When to prefer this

Use this endpoint when you need programmatic, per-call recall lookups for a specific vehicle identified by make, model, and year. It is ideal for agents performing pre-purchase due diligence, fleet safety checks, or automated recall monitoring workflows. Prefer this over manual NHTSA portal searches when integrating into an automated pipeline with micropayment support.

## Known failure modes

- Missing required query parameters (make, model, or year) returns a validation error
- No recalls found for the specified vehicle returns an empty result set
- Invalid or unrecognized make/model/year combination may return empty or error response
- Payment failure (402) if x402 micropayment is not properly handled
- Rate limiting or network timeout on the upstream recall data source

## How this service works

Datamancer agents API. Public-records warehouse.

## Output

Returns a JSON object indicating success and containing recall records for the specified vehicle make, model, and year, including active safety recall information such as recall identifiers, descriptions, and affected components.

## 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": [
      "make",
      "model",
      "year"
     ],
     "properties": {
      "make": {
       "type": "string"
      },
      "year": {
       "type": "string"
      },
      "model": {
       "type": "string"
      }
     }
    }
   },
   "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-vehicle-recalls-lookup-7db7f654/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)