For platform teams · AI assistants · clinical, pharmacy and benefits products
Build OmniRx into your product: records that show their receipts
Every OmniRx answer carries the facts it rests on, the edition it came from, and a list of what it cannot say. That shape is what lets an assistant or a clinical tool use the records without guessing. Below: what an answer looks like, the ways in and their honest status, and the display rules an integration keeps.
What an answer looks like
This is a real file from the static API (/api/v1/dossier/jardiance.json), trimmed for length. receipts are the recorded facts the answer rests on; each resolves to a source URL, a read date and a licence label. unknown says what the edition cannot answer. When it does, the answer stays empty rather than filled in.
{
"answer": {
"identity": {
"application_numbers": [
"NDA204629"
],
"marketing_categories": [
"NDA"
],
"labelers": [
{
"text": "BOEHRINGER INGELHEIM PHARMACEUTICALS",
"untrusted": true
}
]
},
"orphan_designation": {
"ingredients": [
{
"ingredient": {
"text": "empagliflozin",
"untrusted": true
},
"designation_count": 1,
"approved_count": 0,
"recent": [
{
"designated": "2026-11-02",
"use": {
"text": "treatment of glycogen storage disease type 1b (GSD1b)",
"untrusted": true
},
"status": "Designated",
"sponsor": {
"text": "Vitalis Scientia LLC",
"untrusted": true
},
"approved": false
}
],
"read_on": "2026-11-07T12:00:00.000Z",
"fact_id": "2bdcac1644e899b98d840283"
}
],
"reading": "a designation is not an approval and not a statement that the drug treats the condition; status is the FDA database's own"
},
"...": "13 more sections"
},
"receipts": [
{
"fact_id": "b7410c26913210a244bb57ba",
"field": "ndc.listing",
"entity": "ndc:00597015230"
},
{
"fact_id": "33e4b2235ca378fbd48d4100",
"field": "ndc.listing",
"entity": "ndc:00597015237"
},
"... 33 more"
],
"as_of": {
"newest_fact_retrieved_at": "2026-11-10T20:02:39.475Z"
},
"edition": {
"id": "2026-11",
"merkleRoot": "006ab9a329709cbe7f56a0e1a7c4a02f897655cdfecf9ca34d199690095adcb6",
"factCount": 212100,
"manifestPresent": true
},
"licence": {
"classes": [
"AMBER",
"GREEN"
],
"note": "Source records are public; this compilation is cited with attribution. See the provenance tool for each fact's licence label."
},
"unknown": [
{
"code": "NO_DATA",
"field": "supply",
"reason": "no FDA shortage row and no termination date for these packages"
},
{
"code": "NO_DATA",
"field": "policy",
"reason": "no Federal Register event in the edition names this drug or its programs"
},
"... 5 more"
],
"disclaimer": "OmniRx is a reference layer of dated public facts, not clinical advice and not a guarantee of price, coverage or eligibility. Each answer lists the facts it rests on."
}The edition's Merkle root and file checksums are published on the editions page, so an answer can be checked against a root that was published, not just one we report.
Ways in
| Way in | What it is | Status today | Good for |
|---|---|---|---|
| Embed (free, attributed) | Any OmniRx tool in one iframe; a small Powered by OmniRx link stays. | Live | A quick look inside your own pages. |
| White-label tool | The same tool with your branding and colours, pinned versions and a written availability commitment. | Live, under licence | Showing a tool as part of your product. |
| Static JSON API | Pre-rendered files over a frozen edition, 244 drug dossiers among them. No key, no rate limit, no uptime promise; the contract may still change. | Live, evaluation | Trying the shape of the data in your own code. |
| Fund status feed (JSON and CSV) | The charitable copay fund board as files: every fund with its status, the date the page gave, the date read and the source URL. See /assistance/funds. | Live, evaluation | Showing which help-paying programs are open, with the dates to prove it. |
| Medicaid by state data file | The data behind the Medicaid by state explorer: prescriptions and reimbursement by drug, state and year with completeness for each cell. See /medicaid-by-state. | Live, evaluation | Building your own view of Medicaid use by state. |
| Route ladders (JSON twins) | For each condition and each drug its FDA label names, a page and a JSON twin at /conditions/<condition>/<ingredient>.json: six routes in a fixed order that is not a ranking (the label sentence, Medicare Part D and negotiated-price facts, manufacturer programs that list the drug, charitable funds, trial access), each with its source and read date and a receipt where one exists. See /conditions/. | Live, evaluation | Showing every dated way to look for help paying for a drug, with no ranking and no savings figure. |
| Receipt permalinks | Every fact an answer or a route page cites as a receipt has its own address, /fact/<id>, and a JSON twin: the value as stored, the source and read date, the licence label, the verifying quote, the edition root and a hash of the exact stored text. See /fact/. | Live, evaluation | Letting a reader or a model check a receipt one step from the answer. |
| Frozen editions | The library as a database and files with a Merkle root and a checksum for every file, delivered under the data licence. Roots are published. | Live, under licence | Running OmniRx records inside your own system, offline. |
| MCP server (local) | A server for AI assistants that answers the same questions from a frozen edition on your machine. | Built and tested, not yet published | Giving an assistant tools that refuse to guess. |
| Keyed gateway with answer replay | API keys, quotas, edition pinning and signed receipts you can replay later against the same frozen edition. You run it inside your own boundary, with a frozen edition delivered under licence. The mechanism is drawn on the /replay page. | Built and tested, self-hosted; no hosted instance | Running OmniRx where your questions never leave you, with proof of what an answer rested on. |
| Hosted API with accounts | Hosted and rate-limited, with an evaluation key. | Not built | Tell us if this would decide it for you. |
Prices and the licence tiers are on the licence page. A security or AI-vendor review can start from the data posture page. The static API's own page is here.
Rules an integration keeps
Some statements must travel with the figure they qualify, or the figure misleads. Each rule below is the sentence the dossier itself carries for that section; an integration shows it, or something no weaker, wherever it shows the figure.
| Section | The statement that stays with it |
|---|---|
| Generic entry | upper bound from listed dates, not a forecast. |
| Label history | a dated list of FDA supplements and their classes, not a reading of what changed in the label. |
| Substitution | raw FDA codes; the therapeutic equivalence code says whether FDA rates a generic as substitutable, and what that means for a given prescription is for a pharmacist or prescriber. |
| Recalls | FDA classifies the health hazard of a recall, not its effect on supply. |
| Supply | manufacturer-reported last-lot expiry or withdrawal date of one package; other packages and generics can remain. |
| Trials | A recruiting trial listing is not an offer of free drug and not medical advice; enrollment is decided by the study team. OmniRx has summarized and trimmed this ClinicalTrials.gov data. |
| Assistance and offers | A program that lists a drug has not decided anything about any person: each program decides who qualifies, and a status other than open means it may not take new patients. Offers change and expire; read each offer's source and stated end date. A price figure is what the page states, not a quote. |
| Spending | a drug-level aggregate of Medicare Part D claims for all manufacturers combined; not a formulary, not coverage. CMS's dataset states spending is gross drug cost and does not reflect manufacturers' rebates or other price concessions. Spending is the total paid by Medicare, plans and beneficiaries for the drug's claims, not what a patient pays. |
| Medicaid use by state | Medicaid prescriptions and reimbursement by state (CMS State Drug Utilization Data). Reimbursement is before manufacturer rebates: not a net cost, not a patient price. Suppressed managed-care cells make a state figure fee-for-service only. An absent state was suppressed or unreported, not zero. |
| REMS | what the FDA REMS@FDA files tie to the application on the read date; it does not say which prescribers or pharmacies take part or whether a patient needs the program. |
| Orphan designations | a designation is not an approval and not a statement that the drug treats the condition; status is the FDA database's own. |
| Biologic status | what the FDA Purple Book lists on its read date, a record and not a forecast of launch or substitution. |
| Part B payment limit | a Medicare Part B payment ceiling for providers billing a HCPCS code, per dosage descriptor unit; not a price a patient pays, and the presence of a code does not indicate that Medicare covers a product. |
| Safety notices | the notice as FDA published it, listed unchanged; OmniRx does not interpret it or say whether it applies to a given treatment; only the newest notice per drug is held. |
| Policy | Federal Register documents that name the drug or one of its programs: a dated record of what was published, not a reading of its legal effect. |
| DEA schedule | a federal (DEA) classification under 21 CFR Part 1308, not a statement about whether a patient can get the drug; forms and strengths can fall under different schedules. |
Clinical questions are refused with a stated reason; the records answer what was recorded, on what date, from which source. Some sources attach conditions that apply to any use of their facts, for example the ClinicalTrials.gov attribution and processing-date rules. Each fact carries its own licence label with those conditions.
Evaluate it
Open any file above and read the receipts. The DrugAccessBench page publishes a question set and a scorer, so you can test an assistant's answers against the records. When you want a specific set of drugs checked against real records, or a white-label tool, or an edition, tell us what you are building on the licence form; we reply by email.
Two more pages for integrators: how an answer is replayed against its frozen edition, and a browser-side check that an answer matches its receipt. The data tools behind the pages are the charitable copay fund board and the Medicaid by state explorer, each with a data file.
Questions
What does an OmniRx answer contain?
The answer, the receipts (the recorded facts it rests on, each with a source and a read date), the date of the newest fact, the edition, the licence classes, a list of what the edition cannot say, and a disclaimer.
Can an AI assistant use OmniRx records?
Yes. The static JSON API is live for evaluation, a local MCP server is built and tested but not yet published, and a self-hostable gateway with API keys and answer replay is built and tested. Every answer lists what it cannot say, so the assistant has nothing to guess.
Does OmniRx give clinical advice?
No. It is a reference layer of dated public US records. Clinical questions are refused with a stated reason.
How can an answer be verified later?
Each gateway answer carries a signed receipt token. Replaying it re-runs the recorded call on the same frozen edition and reports whether the answer is identical. See the replay page.