Integration guides · snapshots, APIs, warehouses, agents

These patterns follow the dataset contract: snapshot formats, REST paths, MCP tools, field catalog, sample availability, and API examples.

Choose a surface

Snapshot

Best for warehouses, offline analysis, BI tools, and repeatable audit work.

REST API

Best for app backends and services that need current records from /v1/drugs.

MCP

Best for AI agents that need read-only, source-attributed tools.

Snapshot files

Snapshot files are the lowest-friction path for warehouse loading and durable audit trails. The release page describes the current version, sample manifest, and buyer download contract.

JSON snapshot
application/json
CSV snapshot
text/csv
SQLite snapshot
application/x-sqlite3

snapshot workflowbash

# authenticated buyer flow
open /portal/download

# inspect the bundle locally after download
ls -lh *.{json,csv,sqlite,parquet} 2>/dev/null || true

Warehouse loading

Use file formats for bulk analytics. Keep provenance and source fields loaded alongside entity records so downstream users can verify each value.

duckdb / parquetsql

-- Replace dataset.parquet with the shipped file name.
SELECT *
FROM 'dataset.parquet'
LIMIT 20;

pandas / pyarrowpython

import pyarrow.parquet as pq

table = pq.read_table("dataset.parquet")
df = table.to_pandas()
print(df.shape)

REST clients

REST access runs at https://api.rxatlas.dev/v1.

curlbash

curl "https://api.rxatlas.dev/v1/drugs?limit=5" \
  -H "Authorization: Bearer rxatlas_live_····"

fetch.tsts

const res = await fetch("https://api.rxatlas.dev/v1/drugs?limit=5", {
  headers: { Authorization: "Bearer rxatlas_live_····" },
});
if (!res.ok) throw new Error(String(res.status));
const body = await res.json();

Resolve a product NDC

Resolve an FDA product NDC through authenticated production access.

manifest examplebash

curl "https://api.rxatlas.dev/v1/drugs?ndc=75834-258&limit=5" \
  -H "Authorization: Bearer rxatlas_live_····"

Fetch one canonical product

Inspect one canonical drug product with provenance and cross-source IDs.

manifest examplebash

curl "https://api.rxatlas.dev/v1/drugs/147244" \
  -H "Authorization: Bearer rxatlas_live_····"

List data sources

Inspect the source registry behind the delivered dataset.

manifest examplebash

curl "https://api.rxatlas.dev/v1/sources" \
  -H "Authorization: Bearer rxatlas_live_····"

MCP agents

MCP exposes read-only tools over https://api.rxatlas.dev/mcp. The protocol is harness agnostic, while each client wraps the HTTP URL and bearer token differently. See the MCP client configuration guide for Claude, OpenAI Codex, Google Gemini CLI, and Cursor examples.

drugs_searchSearch drug products by brand, generic, ingredient, manufacturer, dosage form, route, or free text.
drugs_getFetch one canonical drug product by id, with every source's provenance + cross-source IDs (NDC / RxCUI / SPL / application no).
drugs_lookup_by_idsBulk NDC-only product resolution with exact segmented NDC10/NDC11 normalization. Each query returns status plus matches[]. RxCUI and SPL set-id are one-to-many filters on drugs_search, not bulk identities.
drugs_coveragePer-source / per-route / per-schedule coverage counts across the canonical drug catalogue.

Field selection

Start integrations with stable, high-value fields from the generated schema catalog. For the complete table, use the data dictionary.

RxAtlas canonical drug-product id.

primary_source

Source code for the first source that created the canonical record.

ndc_list

Distinct NDCs observed across source records for this canonical product.

source_id

First-seen source identifier used to seed the canonical record, such as an NDC, RxCUI, SPL set id, or application number.

source_record_url

URL for the latest source record that contributed to the canonical row.

rxcui

RxNorm concept identifier when the product has an unambiguous redistributable mapped RxCUI.

ingredient_identifiers

UNII ingredient associations with openFDA UNII substance-name synonyms and independent NDC/UNII source versions.

shortages

Package-NDC-level Drug Shortages observations, including source status, availability, presentation, dates, company, related operational information, and reason fields.

Evaluation path

The sample bundle is published with 150 rows. Use it to validate schema, source provenance, and integration ergonomics before buying the production snapshot.

A good first production smoke test is /v1/drugs?ndc=75834-258&limit=5: Resolve an FDA product NDC through authenticated production access.

Integration caveats

RxAtlas is reference data, not medical advice, prescribing advice or reimbursement advice.
Buyers remain responsible for validating source terms and regulated use in their own workflow.

Need a stack-specific example? Email data@apex-db.org.