Evipedia API

We made it as easy as possible to integrate Evipedia and its knowledge into your projects, both via a ready-made JavaScript widget and a simple HTTP API.

Website Integration

To integrate Evipedia directly in your own website, we created a small, embeddable JavaScript widget that automatically surfaces Evipedia evidence reviews inside any web page. Super simple to install.

<script src="https://evipedia.ai/widget.js"></script>
<script>evipedia.init()</script>

Source & Demo: https://github.com/forever-healthy/evipedia-widget

HTTP API

The whole API is a plain HTTP GET — no keys, no SDK. Stable URLs for linking, raw and structured formats for machines, and whole-catalog indexes. Every response ships with open CORS (Access-Control-Allow-Origin: *), so browser-side code can fetch it directly.

OpenAPI

The entire API is also described in a machine-readable OpenAPI 3.1 spec. Point a code generator at https://evipedia.ai/openapi.yaml and you have a typed Evipedia client in seconds — no manual wiring, no keys.

Stable Permalinks

Every intervention has a short, stable URL — /{permalink}, for example /rapamycin — that never changes. Ideal for linking a compound in a supplement stack, or wiring a reference into your own product. Should a permalink need to change for some reason, the old URL will always redirect to the new one, so you can rely on it.

Stable Deep Links

Every evidence review shares the same fixed section structure, so section anchors are identical across all reviews and stable over time. Link straight to a section of any review with /{permalink}_er#{anchor} — for example, /rapamycin_er#conclusion jumps to the conclusion, and #mechanism-of-action, #potential-risks--side-effects, or #therapeutic-protocol work the same on every review. The full list of anchors is published in /llms.txt.

Raw Markdown

Every review is also available as raw Markdown at /{permalink}.md — for example /rapamycin.md — the complete review with no HTML to parse. Just append .md to any review URL. The reviews.json index provides a direct link to each review in its permalink_md field.

Medical Metadata (JSON)

Every review also exposes its medical metadata as JSON at /{permalink}.meta.json — for example /rapamycin.meta.json — the review’s dates and primary-source citations (with PMIDs), flat with no schema.org to parse. Just append .meta.json to any review URL. The reviews.json index provides a direct link to each review in its permalink_meta field.

Reviews Index

/reviews.json is the full catalog as JSON — every review with its canonical name, alternate names, category, permalink, and conclusion. One request gives you the whole library.

Search Index

/search.json is a lightweight search index with one entry per review — each carrying the review’s name, alternate names, keywords, category, and URL. Because it indexes synonyms and drug classes, a query for a brand name, synonym, or class resolves to the right review. It’s the same index that powers the search box on this site.

Hosted Search

If you’d rather not run the query yourself, the hosted search endpoint does it for you: https://mcp.evipedia.ai/search?q={query} — for example, https://mcp.evipedia.ai/search?q=rapamycin — returns the matching reviews (topic, permalink) ranked by relevance, capped at 20, as a small JSON payload. It’s a discovery endpoint — it tells you which reviews exist for a query; to read one, append .md or .meta.json to its URL. It uses the same synonym- and class-aware ranking as the search box and the MCP server. Unlike the static endpoints above, this one is served by the hosted MCP server (mcp.evipedia.ai); it’s rate-limited to 60 requests/minute per IP.

Full Corpus

/evipedia-corpus.jsonl is the entire catalog in a single file — one JSON object per line per review, each with its metadata (topic, URL, category, dates, synonyms, conclusion, citations) and the full Markdown. One request pulls the whole library (~25 MB); it’s newline-delimited, so you can stream it line by line. Ideal for datasets, RAG pipelines, and AI training.

Updates Index

/updates.json is the Updates page as JSON — every live evidence review newest first (including reviews with no QRS), each with its short title, permalink, whether it is new or updated, and the date. Same catalogue and order as the page (production omits hidden reviews).

RSS Feed

/feed.xml is an RSS feed of new and refreshed reviews — subscribe to receive them automatically as they go live.

AI4L Persona

/persona.md is a system prompt for interactive conversations using Evipedia’s & AI4L’s style, features and knowledge — the same file AI4L ships as prompts/PERSONA.md, served as raw Markdown.

Limitations

Please be aware of the “Limitations of evipedia, AI4L & AI”