gov.fda-device-events

FDA medical device adverse event reports (MAUDE), newest first by date received. All filters optional. Each record includes report number, event type, dates received + of event, manufacturer, brand/generic device name, model + catalog numbers, listed device problems, patient outcomes, and primary narrative text. Backed by OpenFDA's /device/event endpoint; public-domain US government records.

price
$0.0024 USDC per call
method
GET/api/gov/fda-device-events
payment
x402 v2 · USDC on Base (EIP-3009) or Solana (SPL transfer)
auth
None. Sign the payment, retry with PAYMENT-SIGNATURE.

Overview

The fda device events API is a pay-per-call gov endpoint built for AI agents and autonomous software. FDA medical device adverse event reports (MAUDE), newest first by date received.

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 fda device events data source for an agent tool-use loop, an MCP host, or a backend that needs gov data on demand without onboarding to yet another vendor portal.

Use cases

Parameters

NameTypeDescription
devicestringDevice-name substring across brand_name + generic_name. Examples: "pacemaker", "insulin pump", "DePuy hip".
min 2 chars · max 100 chars
manufacturerstringManufacturer-name substring. Examples: "medtronic", "boston scientific", "abbott".
min 2 chars · max 100 chars
problemstringFDA device product code substring (advanced filter; most users want device or manufacturer).
min 2 chars · max 100 chars
limitintegerMax events (1-100). Default 20.
min 1 · max 100

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/gov/fda-device-events?device=xx&manufacturer=xx&problem=xx&limit=20'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/gov/fda-device-events?device=xx&manufacturer=xx&problem=xx&limit=20' \
  -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/gov/fda-device-events?device=xx&manufacturer=xx&problem=xx&limit=20'
TypeScript / Node — @2sio/sdktypescript
import { TwoS } from '@2sio/sdk'

const client = new TwoS({
  privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})

const result = await client.gov.fdaDeviceEvents({
  "device": "xx",
  "manufacturer": "xx",
  "problem": "xx",
  "limit": 20
})

console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)
Python — 2siopython
import os
from twosio import TwoS

client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])

result = client.gov.fda_device_events(device="xx", manufacturer="xx", problem="xx", limit=20)

print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)
MCP — Claude Desktop / AgentKit / any MCP hostjson
// 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": "gov.fda-device-events",
    "arguments": {
      "device": "xx",
      "manufacturer": "xx",
      "problem": "xx",
      "limit": 20
    }
  }
}

Response

FieldTypeDescription
okboolean
one of: true
itemsarray
totalintegerTotal matching rows upstream; null when unknown.
sourceobject
metaobject
Example response datajson
{
  "ok": true,
  "items": [
    {
      "reportNumber": "example",
      "eventType": "example",
      "dateReceived": "example",
      "dateOfEvent": "example",
      "manufacturerName": "example",
      "brandName": "example",
      "genericName": "example",
      "modelNumber": "example",
      "catalogNumber": "example",
      "deviceProblems": [
        "example"
      ],
      "patientOutcome": [
        "example"
      ],
      "eventDescription": "example"
    }
  ],
  "total": 1,
  "source": {
    "provider": "example",
    "url": "example",
    "license": "example"
  },
  "meta": {
    "query": {
      "device": "example",
      "manufacturer": "example",
      "problem": "example",
      "limit": 1
    }
  }
}

FAQ

Do I need an API key to use the fda device events API?
No. gov.fda-device-events is x402-native — there is no signup and no API key. Your client makes the call, receives a 402 with payment requirements, signs a USDC payment, and retries. Funds come from a wallet you control.
How much does the fda device events API cost?
$0.0024 USDC per call, charged per request. There are no monthly fees, seats, or minimums — you pay only for the calls you make.
Can I try the fda device events API for free first?
Yes. Add ?trial=1 (or the header X-2s-Trial: 1) to get a free real call per endpoint per hour, so you can verify the response shape before wiring payment.
Which networks and tokens are supported?
USDC on Base (via EIP-3009 transferWithAuthorization) or Solana (SPL transfer), using the open x402 payment protocol.
How do I call gov.fda-device-events from an AI agent or MCP host?
Use @2sio/sdk (TypeScript), 2sio (Python), or the @2sio/mcp server for any MCP host — each handles the probe → sign → retry loop for you. See the code samples on this page.

Discovery

Related: fda device events api · gov fda device events api · fda device events api for ai agents · x402 gov api · fda device events api no api key · pay per call fda device events api · gov api