# FDA Device Recall Detail Lookup

> FDA Device Recall Detail Lookup is a paid API for AI agents from oracles-production.up.railway.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Returns stored detail for a single FDA medical device recall by its entityId.

## Facts

- Endpoint: GET https://oracles-production.up.railway.app/v1/fda-device-recalls/status
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fda-device-recall-detail-lookup-f5591655
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DXCsu5zjTGOWrng7m9UEn

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 fda-device-recall-detail-lookup-f5591655
```

Example prompt: Can you pull up the full details for FDA medical device recall fda-device-recalls:D-1234-2026?

## When to prefer this

Use this endpoint when you already have a specific FDA device recall entityId and need the full stored detail record for it. Prefer this over list or digest endpoints when you need structured, machine-readable data for a single known recall rather than a narrative summary or a list of recent recalls.

## Known failure modes

- Missing or invalid entityId returns empty or error response
- Entity not found if the recall ID has not been ingested or tracked
- Malformed entityId format (not matching 'fda-device-recalls:XXXX') may return no results
- Payment failure (402) if x402 payment header is not provided or insufficient

## How this service works

Stored detail for a single recall (entityId like 'fda-device-recalls:D-1234-2026').

## Output

Returns a JSON object containing the stored entity record for the specified FDA medical device recall, including recall metadata such as device name, reason for recall, classification, and status fields.

## 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"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "id": {
       "type": "string",
       "description": "entityId to look up; omit to list tracked entities"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "entity": {
       "type": "object"
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fda-device-recall-detail-lookup-f5591655/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from oracles-production.up.railway.app](https://www.zero.xyz/host/oracles-production.up.railway.app/llms.txt)