Documentation
Worldwide drug data, three ways in.
The same catalogue backs all three: a console you can search, a REST API you can integrate, and an MCP server your AI client can call. Pick the door that matches what you came to do — nothing is hidden behind the other ones.
One catalogue
664k products
50 live sources
01For pharmacists, prescribers and analysts
Using the console
Look a medicine up, screen a list for interactions, compare what it costs country by country, and see where every fact came from — in the console, with a free account. No API key, no code.
- Look up a drugSearch by name, brand, substance, ATC code or pack identifier.
- Read an interaction verdictWhat each severity means, and what the verdict is not.
- Compare prices across countriesPrice per defined daily dose, and when the comparison is fair.
- Sources and freshnessWhere every fact comes from and how to check it is current.
02For engineers and data teams
Using the API
A key, a bearer token and 45 REST paths — plus GraphQL, signed webhooks and an MCP server for agent tooling. Start with the quickstart and you have a 200 in a minute.
- Endpoint referenceEvery REST endpoint, generated from the OpenAPI document we serve.
- Interactive explorerRun any endpoint against production with your own key.
- WebhooksSubscribe to register changes and verify the signature.
- ErrorsEvery status code we return and what to do about each one.
- MCP serverThe sixteen tools we expose to Claude, Cursor and Windsurf.
Common questions
Three things everyone asks.
- 01
Where does the data come from, and how fresh is it?
Public national registers and open scientific databases only — Swissmedic, BAG, the EMA, national medicines agencies across the EU, and the FDA. Every response carries a
Sources and freshness_meta.sourcesblock stamping each source with when it last synced successfully. - 02
Can I be told when something changes instead of polling?
Yes. Subscribe a URL to the change feed and we POST a batch with an HMAC-SHA256 signature whenever a register moves. Requires the
Webhookswebhooks:writescope, which starts at the Starter plan. - 03
Do you process patient data?
No. The prescription-screening endpoint accepts drug identifiers and coarse, non-identifying context only — age band, sex, pregnancy flag, eGFR band — and rejects any request carrying a patient identifier with a 422 rather than scrubbing it silently. Nothing patient-shaped is stored or forwarded.
The full answer in the FAQ
Reference
The words, and the answers.
Reading this signed out? Every page here is public. When you want to run a call against your own key, create an account — the Free plan needs no card — or open the interactive explorer and paste a key you already have.