One-call medication safety from openFDA public data: label highlights, shortage status, recent recalls, and active ingredients. POST /v1/med with a {drug} and get the safety summary as one JSON object. Deterministic per cached dataset. Pay per request in USDC; no account, no API key.
POST https://agent.pocket.network/v1/med-safety/v1/toolThe first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.
A real, working call — the request the service card verifies against.
curl -X POST https://agent.pocket.network/v1/med-safety/v1/tool \
-H 'content-type: application/json' \
-d '{"arguments":{"drug":"warfarin"}}'The response this call returned, captured 2026-09-21 23:48:06 UTC.
{
"portal": {
"provenance": "third-party-supplier",
"serviceId": "med-safety",
"schemaCheck": "unchecked"
},
"data": {
"active_ingredients": "Warfarin",
"adverse_events_hint": {
"note": "use SPEC-07 /v1/drug with faers window for reactions",
"status": "not_requested"
},
"as_of": "2026-09-21T23:48:05Z",
"label_highlights": {
"brand": "Warfarin Sodium",
"generic": "WARFARIN SODIUM",
"manufacturer": "Teva Pharmaceuticals USA, Inc.",
"section_found_in_first_result": true,
"sections": {
"contraindications": "4 CONTRAINDICATIONS Warfarin sodium is contraindicated in: Pregnancy Warfarin sodium is contraindicated in women who are pregnant except in pregnant women with mechanical heart valves, who are at high risk of thromboembolism [see Warnings and Precautions ( 5.7 ) and Use in Specific Populations ( 8.1 )] . Warfarin sodium can cause fetal harm when administered to a pregnant woman. Warfarin sodium exposure during pregnancy causes a recognized pattern of major congenital malformations (warfarin embryopathy and fetotoxicity), fatal fetal hemorrhage, and an increased risk of spontaneous abortion and fetal mortality. If warfarin sodium is used during pregnancy or if the patient becomes pregnant while taking this drug, the patient should be apprised of the potential hazard to a fetus [see Use in S…",
"drug_interactions": "7 DRUG INTERACTIONS Concomitant use of drugs that increase bleeding risk, antibiotics, antifungals, botanical (herbal) products, and inhibitors and inducers of CYP2C9, 1A2, or 3A4. ( 7 ) Consult labeling of all concurrently used drugs for complete information about interactions with warfarin sodium or increased risks for bleeding. ( 7 ) 7.1 General Information Drugs may interact with warfarin sodium through pharmacodynamic or pharmacokinetic mechanisms. Pharmacodynamic mechanisms for drug interactions with warfarin sodium are synergism (impaired hemostasis, reduced clotting factor synthesis), competitive antagonism (vitamin K), and alteration of the physiologic control loop for vitamin K metabolism (hereditary resistance). Pharmacokinetic mechanisms for drug interactions with warfarin sodi…",
"warnings": "5 WARNINGS AND PRECAUTIONS Tissue necrosis: Necrosis or gangrene of skin or other tissues can occur, with severe cases requiring debridement or amputation. Discontinue warfarin sodium and consider alternative anticoagulants if necessary. ( 5.2 ) Calciphylaxis: Fatal and serious cases have occurred. Discontinue warfarin sodium and consider alternative anticoagulation therapy. ( 5.3 ) Acute kidney injury may occur during episodes of excessive anticoagulation and hematuria. ( 5.4 ) Systemic atheroemboli and cholesterol microemboli: Some cases have progressed to necrosis or death. Discontinue warfarin sodium if such emboli occur. ( 5.5 ) Heparin-induced thrombocytopenia (HIT): Initial therapy with warfarin sodium in HIT has resulted in cases of amputation and death. Warfarin sodium may be cons…"
},
"setid": "b8c33971-54b3-4971-bf7f-1bec66999a29",
"source_url": "https://dailymed.nlm.nih.gov/dailymed/search.cfm?labeltype=all&query=warfarin",
"status": "ok"
},
"recent_recalls": {
"recalls": [
{
"classification": "Class II",
"reason": "CGMP Deviations: Products were exposed to temperatures outside of the products labeled storage conditions.",
"recall_date": "20240103",
"status": "Terminated"
},
{
"classification": "Class II",
"reason": "CGMP Deviations: Products were exposed to temperatures outside of the products labeled storage conditions.",
"recall_date": "20240103",
"status": "Terminated"
},
{
"classification": "Class III",
"reason": "Failed Content Uniformity Specifications.",
"recall_date": "20140924",
"status": "Terminated"
}
],
"status": "ok"
},
"shortage_status": {
"as_of": "2026-09-21T23:48:04Z",
"reason": "FDA shortages feed unreachable 09-07 (503)",
"retryable": true,
"status": "not_available",
"upstream": "dps.fda.gov/drugshortages"
}
}
}Make one real paid call from your own wallet — about $0.005 on Base (eip155:8453). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.
Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.
| Method | Effect |
|---|---|
GET /v1/health | read |
GET /v1/version | read |
POST /v1/med | read |
POST /v1/tool | read |
Published by the service itself. The example above is generated from these.
{
"type": "object",
"description": "A medication to look up. On the MCP relay route POST /v1/tool these fields are wrapped under an `arguments` object; the direct route takes them at the top level.",
"properties": {
"drug": {
"type": "string",
"description": "Drug name, e.g. warfarin."
}
},
"required": [
"drug"
]
}{
"type": "object",
"description": "For POST /v1/med, a JSON object with label highlights, shortage status, recalls, and active_ingredients. The exact shape is the service's own and is not pinned here; errors return a JSON object with an `error` field, and the GET routes return their own small JSON documents."
}