Medicine facts as data
The Pestle API gives software the same structured facts as the site: what each medicine is for, who should not take it, every listed side effect with its stated frequency, and the official leaflet it came from. 454 UK medicines so far.
Try it now, without a key
Five sample medicines return full records with no key: paracetamol, ibuprofen, sertraline, atorvastatin, omeprazole.
curl https://pestle.health/api/v1/medicines/sertraline
Anything else answers with HTTP 200, empty data and a key_notice saying how to get a key, so a program or an AI agent can see what is on offer before signing up.
Endpoints
| Path | What it returns | Key | |
|---|---|---|---|
| GET | /status | Coverage, build time and whether the data is stale | No |
| GET | /offer | Plans and how to get a key, for programs and agents | No |
| GET | /medicines?q= | List or search medicines, with paging | Yes |
| GET | /medicines/{id} | One full medicine record | Sample only without |
| GET | /medicines/{id}/side-effects | Urgent side effects and the frequency groups | Sample only without |
| GET | /barcodes/{gtin} | Identify a UK pack from its barcode and link it to a record | Yes |
| GET | /changes?since= | Records whose leaflet changed or was re-checked since a date | Yes |
| POST | /access-requests | Ask for a key | No |
Send the key as Authorization: Bearer YOUR_KEY or X-API-Key: YOUR_KEY.
curl -H "Authorization: Bearer YOUR_KEY" "https://pestle.health/api/v1/medicines?q=statin"
What a record holds
- The medicine
- Name, active ingredient, what it is for, key facts, who should not take it, what to check first, how to take it, pregnancy and breastfeeding.
- Side effects
- Urgent ones listed separately. The rest grouped by the frequency the leaflet states, with the bounds as numbers: at_most 1 in 10, more_than 1 in 100.
- Source
- The exact product, its licence number, the leaflet's date and a link to the official document.
- Verification
- The date the record was checked against the leaflet, how many side effects matched its wording, and whether a pharmacist has reviewed it.
- Every response
- When the data was built, a data_stale flag, and the attribution to quote.
For AI assistants: the MCP server
The same data is available to AI assistants through the Model Context Protocol at https://pestle.health/mcp. It offers six tools: search medicines, get a medicine, get side effects, look up a barcode, list changes and feed status.
{
"mcpServers": {
"pestle": {
"type": "http",
"url": "https://pestle.health/mcp",
"headers": { "Authorization": "Bearer YOUR_KEY" }
}
}
}
Without the header it works in sample mode, the same as the API.
Rules for use
- Each record comes from one patient information leaflet approved by the UK medicines regulator (MHRA). Quote that leaflet, using source.source_url, alongside any fact you reuse.
- Frequencies are upper bounds stated by the leaflet. "at_most 1 in 10" does not mean 1 in 10 people are affected.
- Missing means unknown. If a side effect, warning or interaction is not in a record, do not infer that it does not occur.
- Other makers of the same medicine publish their own leaflets, which can differ. A record describes the product named in source.product_name.
- This is reference information, not medical advice. Do not use it to tell a person whether to take, stop or change a medicine.
Request a key
The API is in early access. Tell us what you are building and we will send a key by email. Early access keys allow 2,000 requests a day.