FDA medical-device recalls — the enforcement record of devices removed or corrected in the US market because they could pose a health risk. Search by device name (product description), recalling firm (manufacturer), recall classification (I = most serious / reasonable probability of serious health consequences, II, or III), status (Ongoing, Completed, Terminated, Pending), or state of the recalling firm — or omit all filters for the most recent recalls nationwide. Each record returns the FDA recall number, classification, status, product description and quantity, the reason for the recall, code/lot information, the recalling firm and location, distribution pattern, whether it was voluntary or FDA-mandated, and the recall-initiation, classification, and report dates — newest report first, with the total matching count. Free, public-domain US government data. Which devices are under recall right now is fresh post-training data with real patient-safety stakes; distinct from medical.device-510k (clearances), medical.device-classification (risk class), medical.device-udi (device identifiers), and medical.device-event (adverse-event reports). Point-in-time public records, not medical or regulatory advice.
/api/medical/device-recallPAYMENT-SIGNATURE.The device recall API is a pay-per-call medical endpoint built for AI agents and autonomous software. FDA medical-device recalls — the enforcement record of devices removed or corrected in the US market because they could pose a health risk.
There is no signup and no API key. An agent (or any HTTP client) hits the endpoint, receives an x402 "402 Payment Required" challenge, signs a sub-cent USDC payment on Base or Solana, and retries — the data comes back on the paid request. That makes it a drop-in device recall data source for an agent tool-use loop, an MCP host, or a backend that needs medical data on demand without onboarding to yet another vendor portal.
| Name | Type | Description |
|---|---|---|
device | string | Device name / product-description substring. min 2 chars · max 120 chars |
firm | string | Recalling firm (manufacturer) name substring. min 2 chars · max 120 chars |
classification | string | Recall classification: I, II, or III. one of: I | II | III |
status | string | Recall status. one of: Ongoing | Completed | Terminated | Pending |
state | string | 2-letter state of the recalling firm. min 2 chars · max 2 chars |
limit | integer | min 1 · max 100 |
# 1. Probe with no auth → 402 envelope with PaymentRequirements curl -sS 'https://2s.io/api/medical/device-recall?device=xx&firm=xx&classification=I&status=Ongoing&state=xx&limit=10' # 2. Sign + retry with PAYMENT-SIGNATURE: curl -sS 'https://2s.io/api/medical/device-recall?device=xx&firm=xx&classification=I&status=Ongoing&state=xx&limit=10' \ -H 'PAYMENT-SIGNATURE: <base64-json-payload>' # Or use the canonical runner (handles probe → sign → retry): # EVM_PRIVATE_KEY=0x... node --env-file=.env.local \ # --experimental-strip-types scripts/x402-pay.ts \ # 'https://2s.io/api/medical/device-recall?device=xx&firm=xx&classification=I&status=Ongoing&state=xx&limit=10'
import { TwoS } from '@2sio/sdk'
const client = new TwoS({
privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})
const result = await client.medical.deviceRecall({
"device": "xx",
"firm": "xx",
"classification": "I",
"status": "Ongoing",
"state": "xx",
"limit": 10
})
console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)import os
from twosio import TwoS
client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])
result = client.medical.device_recall(device="xx", firm="xx", classification="I", status="Ongoing", state="xx", limit=10)
print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)// 1. Add @2sio/mcp to your MCP host config (Claude Desktop example below).
// EVM_PRIVATE_KEY funds x402 payments per call.
// claude_desktop_config.json
{
"mcpServers": {
"2sio": {
"command": "npx",
"args": ["-y", "@2sio/mcp"],
"env": { "EVM_PRIVATE_KEY": "0x..." }
}
}
}
// 2. Once the server is running, agents call this tool via standard MCP:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "medical.device-recall",
"arguments": {
"device": "xx",
"firm": "xx",
"classification": "I",
"status": "Ongoing",
"state": "xx",
"limit": 10
}
}
}| Field | Type | Description |
|---|---|---|
query | object | |
totalCount | number | |
returned | number | |
recalls | array | |
source | object |
{
"query": {
"device": "example",
"firm": "example",
"classification": "example",
"status": "example",
"state": "example",
"limit": 1
},
"totalCount": 1,
"returned": 1,
"recalls": [
{
"recallNumber": "example",
"status": "example",
"classification": "example",
"productType": "example",
"productDescription": "example",
"productQuantity": "example",
"codeInfo": "example",
"reasonForRecall": "example",
"initialNotification": "example",
"voluntaryMandated": "example",
"recallingFirm": "example",
"city": "example",
"state": "example",
"country": "example",
"distributionPattern": "example",
"recallInitiationDate": "example",
"centerClassificationDate": "example",
"reportDate": "example"
}
],
"source": {
"provider": "example",
"url": "example",
"license": "example"
}
}