# Med Halowerk Device Recall Search

> Med Halowerk Device Recall Search is a paid API for AI agents from med.halowerk.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-13).

Searches the FDA medical device recall database by product name, manufacturer, or model and returns matching recalls with classification, reason, recalling firm, dates, status, and verbatim product descriptions including lot numbers and serial ranges.

## Facts

- Endpoint: POST https://med.halowerk.com/v1/device-recall?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/med-halowerk-device-recall-search-dd15d422
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QzjYaL7NV0Xt0M8AGBBas

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 med-halowerk-device-recall-search-dd15d422 -d '<json body>'
```

Example prompt: Can you check if the Medtronic MiniMed 670G insulin pump has any FDA recalls — I need the classification, reason, recalling firm, and whether any specific lot numbers or serial ranges are affected?

## When to prefer this

Use this endpoint when you need to determine whether a specific medical device, identified by product name, manufacturer, or model, is subject to an FDA recall — especially when you need to verify whether a particular unit (by lot number or serial range) is affected. Prefer this over general web search when you need structured, authoritative FDA recall data with classification severity and verbatim product scope descriptions. Choose this over the drug recall sibling endpoint when the subject is a device (not a pharmaceutical).

## Known failure modes

- No matches found for the given product, manufacturer, or model — returns empty results
- Ambiguous search term matches too many or unrelated products — requires more specific input
- FDA database unavailable or rate-limited — service returns error
- Product exists but has no recall history — empty result set that may be mistaken for a lookup failure
- Lot numbers or serial ranges not available for older recalls — product description field may be incomplete

## How this service works

Searches the device recall database for a product, manufacturer or model and returns each matching recall with the classification and its meaning, the reason, the recalling firm, the dates, the status and — the field that decides whether a specific unit is affected — the product description including lot numbers and serial ranges, quoted verbatim.

## Output

Returns an array of matching recall records, each containing: recall classification (Class I, II, or III) and its meaning, the reason for the recall, the recalling firm name, initiation and termination dates, current recall status, and the verbatim product description including specific lot numbers and serial number ranges needed to determine whether a particular unit is affected.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "limit": {
   "type": "integer",
   "default": 25,
   "maximum": 100,
   "minimum": 1
  },
  "since": {
   "type": "string",
   "maxLength": 10,
   "description": "ISO date; defaults to three years back."
  },
  "device": {
   "type": "string",
   "maxLength": 200,
   "description": "Device name or model."
  },
  "manufacturer": {
   "type": "string",
   "maxLength": 200
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/med-halowerk-device-recall-search-dd15d422/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from med.halowerk.com](https://www.zero.xyz/host/med.halowerk.com/llms.txt)