medical.rxnorm

Normalize and verify drug names against RxNorm, the canonical US drug vocabulary from the NIH. Two modes: term ("tylenol 500mg", brand or generic, typos tolerated) returns ranked RxCUI candidates with normalized names and match scores; rxcui returns the canonical concept (name, term type like IN=ingredient / SBD=branded drug / SCD=clinical drug, suppression flag) plus related concepts — active ingredients, brand names, and available dose forms. Use before writing prescriptions data, drug interactions queries, or pharmacy integrations: verify the drug exists and get its stable identifier instead of trusting model memory. Sibling: /api/medical/icd10 (diagnosis codes). Public-domain NIH data.

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

Overview

The rxnorm API is a pay-per-call medical endpoint built for AI agents and autonomous software. Normalize and verify drug names against RxNorm, the canonical US drug vocabulary from the NIH.

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 rxnorm 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.

Use cases

Parameters

NameTypeDescription
termstringFree-text drug name. Provide term or rxcui, not both.
min 2 chars · max 200 chars
rxcuistring
match ^\d{1,8}$
limitinteger
min 1 · max 20

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/medical/rxnorm?term=xx&rxcui=12345&limit=5'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/medical/rxnorm?term=xx&rxcui=12345&limit=5' \
  -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/rxnorm?term=xx&rxcui=12345&limit=5'
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.medical.rxnorm({
  "term": "xx",
  "rxcui": "12345",
  "limit": 5
})

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.medical.rxnorm(term="xx", rxcui="12345", limit=5)

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": "medical.rxnorm",
    "arguments": {
      "term": "xx",
      "rxcui": "12345",
      "limit": 5
    }
  }
}

Response

FieldTypeDescription
okboolean
one of: true
itemsarray
totalintegerTotal matching rows upstream; null when unknown.
sourceobject
metaobject
Example response datajson
{
  "ok": true,
  "items": [
    {}
  ],
  "total": 1,
  "source": {
    "provider": "example",
    "url": "example",
    "license": "example"
  },
  "meta": {
    "mode": "search",
    "concept": {
      "rxcui": "example",
      "name": "example",
      "synonym": "example",
      "termType": "example",
      "suppressed": false
    },
    "related": [
      {
        "termType": "example",
        "concepts": [
          {
            "rxcui": "example",
            "name": "example"
          }
        ]
      }
    ]
  }
}

FAQ

Do I need an API key to use the rxnorm API?
No. medical.rxnorm 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 rxnorm API cost?
$0.0012 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 rxnorm 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 medical.rxnorm 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: rxnorm api · medical rxnorm api · rxnorm api for ai agents · x402 medical api · rxnorm api no api key · pay per call rxnorm api · medical api