Using the console

Six screens, one question each.

Nothing here needs an API key, a terminal or any knowledge of what an HTTP header is — that is the point of the distinction between this section and the API section.

The console’s six screens. Each opens the real page (sign-in required).

Which screen answers what

You want to know	Go to
Everything about one medicine — what it is, what it is for, what it costs, where it is sold	Explore
Whether a list of medicines is safe to take together	Interactions
What the same medicine costs in another country	Prices
Something open-ended, phrased as a question	Ask
What moved in the registers — new products, withdrawals, recalls	Changes
Where a fact came from and whether it is current	Sources

Guides

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.

Three habits worth having

Read the source chip, not just the number. Every value in the console carries the register it came from. A price without a source chip is not a price we hold — and where we hold nothing, the console shows nothing rather than an estimate. An empty section means “not on file”, never “none exist”.

Absence is not evidence. This runs through every screen. No interaction on file is not proof of safety. No warning text on file is not a clean safety profile. The console is explicit about this because the alternative — a blank panel that reads as reassurance — is the most dangerous thing a drug database can do.

Check freshness when it matters. Registers update on their own cadence and some upstream feeds break. Sources shows the state of every feed, and the guide explains what live, degraded and pending actually mean.

What this is not

Informational only. Not a medical device, and not a substitute for professional clinical judgment. Verify against primary sources before clinical use. That line appears under every clinical answer in the console and it is not boilerplate — the underlying data is a faithful copy of public registers, which are themselves incomplete, lagging and occasionally wrong.

If you outgrow the console

Everything on these screens is the same data the API returns — the console calls the same resolvers. When you want it in your own product, the quickstart is a minute long, and there is a Playground in the console where you can run a real call without leaving the app.