Back to Browse
RxNorm NDC Status & Product Resolver
x402
RxNorm NDC Status & Product Resolver is a paid API for AI agents from rxnorm-ndc-status.hergertsynthora.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).
Looks up the active/obsolete status, normalized NDC11, mapped RxCUI, and concept name for a National Drug Code via NLM RxNorm
Price / call$0.001
Success—
StatusUnknown
How this service works
Returns the active/obsolete status, normalized NDC11, mapped RxCUI, concept name and source list for a National Drug Code via NLM rxnav.nlm.nih.gov/REST/ndcstatus. Autonomous agents and agent-to-agent (A2A) claims-adjudication, inventory and pharmacy-validation systems consume it to confirm whether a packaged product code is still marketable. Ranking surface: NDC to status and canonical product. First 3 calls FREE per wallet — send header X-WALLET: 0x<addr>. No charge on upstream failure.
Output
Returns a JSON object with the drug's active/obsolete status, normalized NDC11 code, mapped RxCUI identifier, and concept name as sourced from NLM RxNorm. The response includes an 'ok' flag, the queried NDC, status string (e.g. ACTIVE), and provenance metadata indicating the NLM RxNav REST API as the underlying data source.
Example use cases
Pharmacy claim NDC validation
“Before we process this insurance claim, check if NDC 0378-5007-05 is currently active and marketable — I need the RxCUI and whether it's been discontinued.”
Inventory obsolescence check
“We have NDC 00093-0058-01 in our warehouse inventory system — can you verify whether that product code is still valid or has been marked obsolete by RxNorm?”
Drug code normalization for EHR
“I need to normalize the drug code 0002-7597-01 to its 11-digit NDC11 format and map it to the corresponding RxCUI so we can store it in our EHR system correctly.”
Technical details
Endpoint
POSThttps://rxnorm-ndc-status.hergertsynthora.com/serviceWhen to prefer
Use this endpoint when you need a fast, per-NDC lookup of drug marketability status and RxNorm concept mapping without building a direct integration to NLM's RxNav API. It is ideal for autonomous claims-adjudication, pharmacy inventory validation, and EHR data normalization pipelines that need to confirm whether a packaged drug product code is still active before processing. Prefer this over a raw NLM API call when operating in an agent or A2A context where metered, pay-per-call access via x402 is acceptable and you want a pre-normalized JSON response.
Side effects
- NDC not found in RxNorm database — returns empty or null result fields
- Malformed NDC input (wrong format or length) — may return no match
- NDC exists but has no RxCUI mapping — fields returned as null
- Upstream NLM RxNav API unavailable — service may timeout or return error
- Obsolete NDC with no active replacement — status returned as OBSOLETE with limited metadata
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| ndc | string | ndc |
Output
Schema · Response
{
"type": "json",
"example": {
"ok": true,
"niche": "rxnorm-ndc-status",
"result": {
"ndc": "0069-3150-83",
"rxcui": "1668240",
"status": "ACTIVE",
"humanDrug": null,
"description": null,
"productType": null,
"originalPackager": null,
"marketingCategory": null
},
"provenance": {
"url": "https://rxnav.nlm.nih.gov/REST/ndcstatus.json",
"source": "RxNorm NDC Status & Product Resolver"
}
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"