Examine APIexamine.com ↗
Access supplement profiles, health conditions, outcomes, evidence grades, and study summaries from Examine.com via 9 structured endpoints.
What is the Examine API?
The Examine.com API provides access to evidence-based supplement and health data across 9 endpoints, covering supplement profiles, health categories, conditions, outcomes, and study summaries. The get_supplement_overview endpoint returns dosage tables, safety information, research snapshot counts (references, trials, meta-analyses), and A–D evidence grades per outcome. The search endpoint queries across supplements, conditions, guides, and categories in a single call.
curl -X GET 'https://api.parse.bot/scraper/7ed39348-ef4b-4a1a-a262-dc5a2d3a8570/search?query=creatine&type_filter=Supplement' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace examine-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Examine.com SDK — bounded, re-runnable; every call capped."""
from parse_apis.examine_com_api import Examine, Supplement, SupplementOverview, Category, Condition, Guide, ResourceNotFound
examine = Examine()
# List all health categories
for category in examine.categories.list(limit=5):
print(category.name, category.slug)
# Get a specific category and explore its conditions
brain = examine.categories.get(slug="brain-health")
for condition in brain.conditions.list(limit=3):
print(condition.name, condition.slug)
# Get a condition's details
depression = examine.conditions.get(slug="depression")
print(depression.title, depression.description)
# Search for supplements
for result in examine.supplements.search(query="vitamin d", limit=3):
print(result.title, result.type, result.url)
# Get a supplement's full overview via the sub-resource
supp = examine.supplement(slug="creatine")
overview = supp.overview.get()
print(overview.title, overview.summary)
print(overview.research_snapshot.trials, overview.research_snapshot.participants)
for grade in overview.evidence_grades[:3]:
print(grade.grade, grade.label, grade.extra)
# Get a guide
try:
guide = examine.guides.get(slug="how-to-read-a-study")
print(guide.title, guide.content[:100])
except ResourceNotFound as exc:
print(f"Guide not found: {exc}")
print("exercised: categories.list / categories.get / conditions.list / conditions.get / supplements.search / overview.get / guides.get")
Full-text search across Examine.com content including supplements, conditions, outcomes, guides, and categories. Returns matching results with type classification. Results are not paginated; the server returns a single page of top matches.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Search keyword (e.g., 'creatine', 'vitamin d', 'immunity'). |
| type_filter | string | Filter results by type. Passed as the 'type' query parameter to the search page. |
{
"type": "object",
"fields": {
"results": "array of search result objects, each containing title, url, type, and slug"
},
"sample": {
"data": {
"results": [
{
"url": "https://examine.com/supplements/creatine/",
"slug": "creatine",
"type": "Unknown",
"title": "Creatine"
},
{
"url": "https://examine.com/outcomes/creatinekinase/",
"slug": "creatinekinase",
"type": "Unknown",
"title": "Creatine Kinase"
}
]
},
"status": "success"
}
}About the Examine API
Supplement Data
The get_supplement_overview endpoint is the most data-dense in the API. Given a slug from list_supplements, it returns the supplement's summary, structured dosage data (both text paragraphs and table rows), a safety content block, and an array of evidence_grades — each grade object carrying a letter (A–D), the associated outcome label, and an extra field indicating additional outcomes grouped under that grade. The research_snapshot object surfaces aggregate counts: total references, participant counts, number of trials, and number of meta-analyses, all as strings.
Health Categories and Conditions
list_health_categories returns all category slugs and names (for example, brain-health or cardiovascular-health). Passing a category slug to get_health_category returns the category title plus an array of condition objects, each with a name and slug. Individual conditions can then be fetched via get_health_condition, which returns the condition's display title and a description string sourced from Examine.com's meta description for that condition. list_conditions gives a flat list of every tracked condition without needing to traverse categories first.
Outcomes and Search
list_outcomes returns all health outcomes tracked on Examine.com — each with a name and slug — giving you the full vocabulary Examine.com uses to classify what a supplement may affect. The search endpoint accepts a query string and an optional type_filter parameter, and returns an array of result objects each containing title, url, type, and slug. This makes it straightforward to resolve a free-text user query into structured slugs for downstream lookups.
Study Summaries
The get_study_summary endpoint accepts a study slug and returns the study's title and full content string, covering methodology, results, and conclusions as presented on Examine.com. Study slugs must be known in advance from Examine.com study URLs; there is no listing endpoint for studies in this API.
The Examine API is a managed, monitored endpoint for examine.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when examine.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official examine.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a supplement research tool that surfaces evidence grades and trial counts from
get_supplement_overviewfor any compound a user queries. - Populate a health condition database using
list_conditionsandget_health_conditionto retrieve descriptions for each condition slug. - Create a category-browsing feature using
list_health_categoriesandget_health_categoryto map conditions to body systems. - Resolve natural-language supplement queries to structured slugs via the
searchendpoint before fetching detailed profiles. - Build a dosage reference tool using the structured dosage tables returned by
get_supplement_overview. - Aggregate all tracked health outcomes from
list_outcomesto build a taxonomy for tagging or filtering supplement content. - Deliver study methodology and conclusion text in a research digest app using
get_study_summary.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Examine.com have an official developer API?+
What does the `evidence_grades` field in `get_supplement_overview` actually contain?+
grade field (a letter from A to D), a label naming the outcome (for example, 'Muscle Mass'), and an extra field that indicates how many additional outcomes are grouped under that grade entry. This gives a quick summary of which outcomes have stronger or weaker evidence for a given supplement.Does the API return full per-study data for every study referenced in a supplement profile?+
get_supplement_overview returns aggregate research snapshot counts (references, participants, trials, meta-analyses) rather than individual study records. get_study_summary fetches a single study's full content by slug, but there is no endpoint to list all studies linked to a supplement. You can fork this API on Parse and revise it to add an endpoint that enumerates study slugs for a given supplement.Are there any notable gaps in what the search endpoint can filter?+
search endpoint accepts a type_filter parameter to narrow results by type, but it does not support sorting, pagination, or field-level filtering (for example, filtering by evidence grade or category). Results are returned as a flat array of title, url, type, and slug. You can fork this API on Parse and revise it to add pagination parameters or additional filter logic.