# RxNorm NDC Status & Product Resolver

> 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

## Facts

- Endpoint: POST https://rxnorm-ndc-status.hergertsynthora.com/service
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/rxnorm-ndc-status-product-resolver-2e9de4df
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3c-_9e7aiThoDS4GPZwqN

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability rxnorm-ndc-status-product-resolver-2e9de4df -d '<json body>'
```

Example prompt: Can you check whether NDC 0069-3150-83 is still active and give me its RxCUI and canonical drug name from RxNorm?

## When to prefer this

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.

## Known failure modes

- 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

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

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ndc": {
   "type": "string",
   "description": "ndc"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "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"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/rxnorm-ndc-status-product-resolver-2e9de4df/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from rxnorm-ndc-status.hergertsynthora.com](https://www.zero.xyz/host/rxnorm-ndc-status.hergertsynthora.com/llms.txt)