Licence summary · commercial-use boundaries for RxAtlas
This is a plain-English summary for the US Drug Database, NDC API and Download. The binding text is the Terms, the checkout/order terms, and the per-source licence records on Sources & licences.
PRICING_SKUS, export formats from SNAPSHOT_FORMATS, source obligations from sourceCatalog, and buyer caveats from websiteContent.complianceCaveats.What paid access grants
Paid access is designed for one organisation to evaluate, load, query, and use the dataset in internal business systems. Each delivered snapshot is a versioned artifact; the API and MCP surfaces are live access paths over the same schema and provenance model.
- Load delivered snapshot files into a warehouse, lake, local database, or internal application.
- Query the REST API or MCP server for internal workflows covered by the purchased tier.
- Share results with employees and contractors acting for your organisation.
- Use provenance, source URLs, and licence fields for internal audit, procurement, and compliance review.
- Publish derived analysis when it does not expose row-level data or a substantial extract of the dataset.
Snapshot tiers
The licence summary follows the checkout SKUs so pricing and usage rights stay aligned.
Snapshot exports are published in the formats below. Buyer downloads are delivered through the authenticated portal, not as public file URLs.
- JSON snapshot
application/json
- CSV snapshot
text/csv
- SQLite snapshot
application/x-sqlite3
Sample scope
The public evaluation sample currently contains 150 rows (92.9 KB zip · 25 JSON fields · 13 flat columns). It uses the same schema, source metadata, and provenance posture as the paid snapshot, but it is an evaluation artifact and not a production licence.
Restrictions
Unless the order form or Enterprise agreement says otherwise, the standard package is licensed for internal use only.
- Do not resell, redistribute, sublicense, lease, or publish the dataset or a substantial extract as a dataset.
- Do not expose row-level records through a customer-facing product or public query interface.
- Do not remove provenance, source URLs, attribution notices, or licence fields from operational copies.
- Do not share API tokens outside your organisation or work around rate limits.
- Do not treat the dataset as professional, legal, medical, safety, financial, or regulatory advice.
Source-specific terms & flow-down
The source registry currently lists 13 commercial-use cleared sources. The downloadable snapshot and API include only records cleared for the paid release.
Commercial-use cleared
13 sourcesSources cleared in the manifest for commercial dataset redistribution and buyer-facing exports.
The full source register, homepages, jurisdictions, and licence notes live on Sources & licences. Preserve source codes so JSON-LD DataCatalog entries and docs anchors resolve to the same records.
Attribution
Keep source and provenance metadata attached to operational copies. When publishing permitted derived analysis, include a dataset-level credit and any upstream attribution required by the cited source licences.
US Drug Database, NDC API and Download: RxAtlas.
Underlying sources and per-field provenance: RxAtlas / docs / sources.AI training
Standard snapshot SKUs do not grant a separate right to train, fine-tune, distil, or build embedding corpora from the dataset. If a buyer needs AI-training rights, model-distribution rights, or a share-alike-free source variant, handle that as an Enterprise scope.
Warranty posture
These are provenance-first reference datasets, not official source authority services. The Terms control warranty, limitation of liability, and acceptable-use language. The practical buyer caveats for this dataset are:
- 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.
Enterprise rights
Redistribution, customer-facing embed, AI-training, custom refresh SLAs, indemnity, escrow, residency, and master-agreement terms belong in an Enterprise order form. Start from pricing or email data@apex-db.org.