# ED-initiated buprenorphine ED-initiated buprenorphine Status: LIVE Price: $0.005 USDC `GET /api/calc/ed_buprenorphine` HTML: https://magentlab.com/docs/ed-buprenorphine Markdown: https://magentlab.com/docs/ed-buprenorphine.md Not a medical device. Not a diagnosis, dose, or listing recommendation. ## What it computes Return the D'Onofrio 2015 emergency-department-initiated buprenorphine milligram for protocol day 1, 2, or 3: 8 mg on day 1 and 16 mg on days 2 and 3. ## When to use When an agent needs the published D'Onofrio 2015 take-home milligram schedule for ED-initiated buprenorphine on protocol day 1, 2, or 3 and must not invent a home-induction tree, score COWS, or name a product brand. ## When not to use - Not a medical device. Deterministic published-schedule output only. - Not a prescription. magent does not name a product, route, or formulation. - Not an X-waiver or induction algorithm beyond the trial's day-1 8 mg and day-2/3 16 mg take-home schedule. - magent does not score COWS. ## Formula ``` dose_mg = (day == 1) ? 8 : 16 ``` ## Citation [Emergency Department-Initiated Buprenorphine/Naloxone Treatment for Opioid Dependence: A Randomized Clinical Trial](https://doi.org/10.1001/jama.2015.3474) D'Onofrio G, O'Connor PG, Pantalon MV, Chawarski MC, Busch SH, Owens PH, Bernstein SL, Fiellin DA JAMA. 2015;313(16):1636-1644 DOI: [10.1001/jama.2015.3474](https://doi.org/10.1001/jama.2015.3474) ## Worked example ### Protocol day 1 Given: `day=1` 1. day = 1 2. dose_mg = 8 ### Protocol day 2 Given: `day=2` 1. day = 2 2. dose_mg = 16 ### Protocol day 3 Given: `day=3` 1. day = 3 2. dose_mg = 16 ## Also searched as - ED buprenorphine - emergency department buprenorphine - D'Onofrio buprenorphine - ED-initiated buprenorphine - buprenorphine day 1 8 mg - buprenorphine take-home 16 mg - opioid dependence ED induction ## Parameters - `day` (integer, required): D'Onofrio 2015 protocol day 1, 2, or 3. Day 1 is 8 mg. Days 2 and 3 are 16 mg. Not a home-induction tree. magent does not score COWS. ## Bulk (POST) POST the same path with a JSON items array. The first item is the GET unit; each additional item is $0.002. Invalid items return HTTP 400 before settlement. Method: `POST /api/calc/ed_buprenorphine` Max items: 25 Price: unit_amount + extra_item_amount * (n - 1) (unit 5000 atomic, extra 2000 atomic) Status: PREVIEW - 1 to 25 items. Each item uses the same keys as the GET query parameters. - POST of 1 item costs the same as GET. Lists longer than 25: chunk into multiple POSTs. Extra items still execute; do not pad dummy rows. - The first invalid item fails the whole request (index in the 400 JSON). You are not charged. - HTTP 200 is {count, path, items}. Each items[i] is the GET 200 body for that row. - Catalog misses (empty matches, found=false) stay paid 200s inside that slot. - x402 resource URL is this path plus n and body_sha256. Browsers that prefer text/html get the same paywall as GET; Pay retries POST with the same items. Example request: ```json { "items": [ { "day": "1" }, { "day": "1" } ] } ``` Human paywall (two-item fixture): https://api.magentlab.com/paywall/bulk/ed-buprenorphine Example 200: ```json { "count": 2, "path": "/api/calc/ed_buprenorphine", "items": [ { "day": 1, "disclaimer": "Not a medical device. Deterministic published-formula or published-code output for autonomous agents. A licensed clinician remains responsible for patient care and billing submissions.", "citation": { "authors": "D'Onofrio G, O'Connor PG, Pantalon MV, Chawarski MC, Busch SH, Owens PH, Bernstein SL, Fiellin DA", "doi": "10.1001/jama.2015.3474", "id": "donofrio-2015", "pmid": "25919527", "source": "JAMA. 2015;313(16):1636-1644", "title": "Emergency Department-Initiated Buprenorphine/Naloxone Treatment for Opioid Dependence: A Randomized Clinical Trial" }, "formula": "donofrio_2015", "formula_expression": "dose_mg = (day == 1) ? 8 : 16", "dose_mg": 8 }, { "day": 1, "disclaimer": "Not a medical device. Deterministic published-formula or published-code output for autonomous agents. A licensed clinician remains responsible for patient care and billing submissions.", "citation": { "authors": "D'Onofrio G, O'Connor PG, Pantalon MV, Chawarski MC, Busch SH, Owens PH, Bernstein SL, Fiellin DA", "doi": "10.1001/jama.2015.3474", "id": "donofrio-2015", "pmid": "25919527", "source": "JAMA. 2015;313(16):1636-1644", "title": "Emergency Department-Initiated Buprenorphine/Naloxone Treatment for Opioid Dependence: A Randomized Clinical Trial" }, "formula": "donofrio_2015", "formula_expression": "dose_mg = (day == 1) ? 8 : 16", "dose_mg": 8 } ] } ``` ## Response fields - `formula` (string): donofrio_2015 - `formula_expression` (string): dose_mg = (day == 1) ? 8 : 16 - `day` (integer): Protocol day 1, 2, or 3 - `dose_mg` (integer): Buprenorphine milligrams: 8 on day 1; 16 on days 2 and 3 - `citation` (object): D'Onofrio 2015 JAMA citation - `disclaimer` (string): Not-a-device notice ## Example JSON Frozen fixture. Not a live lookup. ```json { "day": 1, "disclaimer": "Not a medical device. Deterministic published-formula or published-code output for autonomous agents. A licensed clinician remains responsible for patient care and billing submissions.", "citation": { "authors": "D'Onofrio G, O'Connor PG, Pantalon MV, Chawarski MC, Busch SH, Owens PH, Bernstein SL, Fiellin DA", "doi": "10.1001/jama.2015.3474", "id": "donofrio-2015", "pmid": "25919527", "source": "JAMA. 2015;313(16):1636-1644", "title": "Emergency Department-Initiated Buprenorphine/Naloxone Treatment for Opioid Dependence: A Randomized Clinical Trial" }, "formula": "donofrio_2015", "formula_expression": "dose_mg = (day == 1) ? 8 : 16", "dose_mg": 8 } ``` ## Errors - HTTP 400 `invalid_ed_buprenorphine`: ED buprenorphine day must be 1, 2, or 3 as published in D'Onofrio 2015. Returned before settlement; you are not charged. - HTTP 400 `invalid_items`: POST body must be a JSON object with only an items array Returned before settlement; you are not charged. - HTTP 400 `invalid_item_count`: items must be an array of 1 to 25 objects Returned before settlement; you are not charged. - HTTP 400 `invalid_item`: each items entry must be a JSON object Returned before settlement; you are not charged. Shared HTTP 402 and 503: https://magentlab.com/docs/payments ## Related tools - [COWS](https://magentlab.com/docs/cows) — Sum the eleven Wesson 2003 Clinical Opiate Withdrawal Scale (COWS) items from caller-assigned appendix integers and return the published total (max 48) with the published severity cutoffs. - [Naloxone infusion](https://magentlab.com/docs/naloxone-drip) — Compute a continuous intravenous naloxone infusion rate as two-thirds of the caller-assigned reversal bolus each hour, using the Goldfrank 1986 text rule. - [Morphine milligram equivalents](https://magentlab.com/docs/mme) — Compute morphine milligram equivalents from a CDC 2022 table opioid and daily dose (or transdermal fentanyl mcg/hr). ## Payment Unpaid requests return HTTP 402 even if query parameters or POST items are missing or invalid, so CDP and agents can index the path. After a PAYMENT-SIGNATURE, invalid params return HTTP 400 JSON before settlement. magent does not charge. Fix the params, then request a new 402 quote for that complete URL. Catalog misses (empty matches, found=false) are valid paid 200s. - GET the tool with Accept: application/json (do not send Accept: text/html unless you want the human paywall). - HTTP 402 means you have not paid. Decode the base64 PAYMENT-REQUIRED header. HTTP 503 is not a new quote. - Sign accepts[0] (exact, EIP-3009) with validBefore = now + maxTimeoutSeconds (600 seconds), or accepts[1] (batch-settlement deposit/voucher) on product GET. Ping and POST {items} stay exact. Magent retries transient facilitator 429/5xx before answering. - Retry the same URL with PAYMENT-SIGNATURE (base64 JSON of accepted and payload). Magent attaches canonical extensions.bazaar on CDP verify/settle; echoing 402 bazaar is optional. - Success is HTTP 200 JSON plus PAYMENT-RESPONSE. exact settles before the tool. batch-settlement verifies (and deposit-settles) before the tool and commits the charge after HTTP 2xx. HTTP 503: retry the same PAYMENT-SIGNATURE. Mint a new exact nonce only after a new HTTP 402. - offered `exact` on eip155:8453: Fixed-price USDC on Base. The buyer authorizes the advertised amount (EIP-3009). magent settles before the tool runs (paymentFlow upfront). extra.assetTransferMethod=eip3009 extra.paymentFlow=upfront. - offered `batch-settlement` on eip155:8453: Payment-channel vouchers claimed later in batches. Exact stays accepts[0]. Same-path POST {items} is still exact. extra.assetTransferMethod=eip3009 extra.paymentFlow=authorization. - not offered `upto`: Not offered. Usage-based: buyer authorizes a ceiling, seller settles the actual amount after work. Reserved for a future metered tool. Not for current calculators or code search. Same-path POST {items} is still scheme exact: one EIP-3009 authorization for GET unit plus $0.002 per extra item. That is not x402 batch-settlement (payment channels / vouchers). Shared HTTP 402 and 503 table: https://magentlab.com/docs/payments Stdio MCP (one process per host): https://magentlab.com/docs/mcp ## Guarantees - HTTP 402 is unpaid, including a missing query. After PAYMENT-SIGNATURE, invalid parameters return HTTP 400 before settlement. You are not charged. HTTP 402 never includes the tool JSON. - exact: settlement finishes before the tool (paymentFlow upfront). batch-settlement: verify/deposit before the tool; chargedCumulativeAmount commits after HTTP 2xx. Uncertain or failed settlement fails closed (HTTP 503). Retry the same PAYMENT-SIGNATURE. - HTTP 402 is unpaid only. Do not sign a second authorization because of a 503. - Execution is timeout-bounded and concurrency-capped. - Calculator inputs are stored encrypted for allowlisted operators (Magent Console). They are not in public logs, SSH lookups, catalog, or rollups. Request logs store path without query.