Caffeine remaining after a time
API · /caffeine-api
Caffeine Calculator API
Caffeine metabolism maths as an API, computed locally and deterministically with a first-order (exponential) decay model. The level endpoint computes how much caffeine remains in the body after a given time from a dose and a half-life (about 5 hours by default), as milligrams and a percentage, and how long until it falls to a chosen threshold. The timeline endpoint returns an hour-by-hour decay curve and the time until caffeine is "sleep safe" — below a threshold (50 mg by default) — handy for working out a coffee cut-off before bed. The sources endpoint gives the typical caffeine content of common drinks (brewed coffee, espresso, tea, energy drinks, cola and more) for a single drink, or totals a list such as two coffees and a cola. Everything is computed locally and deterministically, so it is instant and private. This is informational only: real caffeine half-life varies widely between people (roughly 3–7 hours, and much longer in pregnancy or with certain medications) — it is not medical advice. Ideal for coffee, sleep and wellbeing apps, energy-drink and habit trackers, and quantified-self tools. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is caffeine pharmacokinetics; for a drug reference database use a drug API.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 91 ms
- Server probes · 24h
- Subscribers
- 3,652
- active
- Total calls
- 40
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 11,435 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 11,435 calls/month
- 2 req/sec
- Level + timeline + sources
- No credit card
Starter
€12.95 /month
- 21,050 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 21.05k calls/month
- 8 req/sec
- Sleep-safe time + drink totals
- Email support
Pro
€32.85 /month
- 260,500 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 260.5k calls/month
- 20 req/sec
- Sleep / wellbeing pipelines
- Priority support
Mega
€70.85 /month
- 1,345,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 1.345M calls/month
- 50 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
KEGG API
The KEGG molecular database as an API, powered by the official KEGG REST service. KEGG (the Kyoto Encyclopedia of Genes and Genomes) links genomes, chemistry and disease. Fetch any KEGG entry parsed to JSON — a metabolic compound, KEGG Orthology group (KO), enzyme (EC number), reaction, module, drug, disease, glycan, gene or pathway map; search any KEGG database by name; list a database's entries; cross-link entries between databases (a gene to its pathways, a pathway to its compounds, an enzyme to its reactions); and convert KEGG identifiers to and from outside namespaces (NCBI Gene/Protein, UniProt, ChEBI, PubChem). Ideal for systems-biology and metabolomics pipelines, enzyme and orthology mapping, drug and disease research, gene-to-pathway annotation and bioinformatics id conversion. KEGG ids are letter-prefixed (C compound, K orthology, D drug, H disease, M module, R reaction, G glycan) or organism-coded (hsa human, eco E. coli).
api.oanor.com/kegg-api
Reactome API
The Reactome pathway knowledgebase as an API — the open, peer-reviewed database of biological pathways and reactions, powered by the official Reactome ContentService. Search the curated archive of pathways, reactions and molecules; read any entity by its Reactome stable id (a pathway, reaction, complex or protein: name, type, species, compartments, summary and disease flag); list the events (sub-pathways and reactions) contained in a pathway; list the molecules participating in a pathway or reaction with their reference identifiers; get the top-level pathways for any model organism; map a UniProt protein to the pathways it takes part in; and list the supported species. Covers human and 15+ model organisms across metabolism, signal transduction, cell cycle, immune system, disease and more. Ideal for systems-biology and bioinformatics pipelines, pathway-enrichment and drug-target tools, biomedical research apps, teaching resources and life-science chatbots.
api.oanor.com/reactome-api
Coffee Roasting API
Coffee-roasting maths as an API, computed locally and deterministically — the roast-profile numbers a home or specialty roaster tracks batch to batch. The loss endpoint works the weight-loss relationship from any two of the green weight, the roasted weight and the loss percentage: weight loss % = (green − roasted) / green × 100, so 1 kg of green dropping to 840 g is a 16 % loss, a 15 % target leaves 850 g, and to bag 800 g of roasted you charge 952 g of green (roasted ÷ (1 − loss%)). Light roasts shed about 12–14 %, medium 15–17 %, dark 18–20 %. The development endpoint computes the development time and the Development Time Ratio (DTR) from the total roast time and the first-crack time — DTR = (total − first crack) / total × 100, with most roasters aiming for roughly 20–25 %; times accepted as seconds or mm:ss. Everything is computed locally and deterministically, so it is instant and private. Ideal for coffee-roasting, roastery, specialty-coffee and roast-logging app developers, profile and batch tools, and roasting education. Pure local computation — no key, no third-party service, instant. Weights in grams, times in seconds or mm:ss. Live, nothing stored. 2 compute endpoints. This is roast-profile maths; for brewing ratios use a coffee-brewing API.
api.oanor.com/coffeeroast-api
Coffee Brewing API
Coffee brewing maths as an API, computed locally and deterministically. The ratio endpoint works out a brew recipe from any two of the coffee dose, the water and the brew ratio — water = coffee × ratio — and reports the third value, the ratio as 1:N, the number of cups and whether the recipe sits around the SCA "golden ratio" of about 1:16–1:17. The espresso endpoint does the same for espresso from any two of the dose, the yield and the brew ratio (yield = dose × brew ratio), labelling the shot ristretto, normale or lungo. The extraction endpoint computes the extraction yield, EY% = (beverage mass × TDS%) ÷ dose, from the dose, the brewed beverage mass (or the water, estimating the mass the grounds retain) and the measured total dissolved solids, then classifies the brew as under-extracted, ideal or over-extracted and weak through very strong against the SCA brewing control chart. Masses are in grams, water in grams or millilitres. Everything is computed locally and deterministically, so it is instant and private. Ideal for specialty-coffee, café, brewing-scale and recipe app developers, pour-over and espresso tools, and barista training. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is coffee brewing maths; for cooking-unit conversions use a cooking API and for caffeine intake use a caffeine API.
api.oanor.com/coffee-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Caffeine Calculator API?
What's the rate limit for Caffeine Calculator API?
How much does Caffeine Calculator API cost?
Can I cancel my subscription anytime?
Is Caffeine Calculator API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/caffeine-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/caffeine-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/caffeine-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/caffeine-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.