takeaway gives you the paper’s conclusion; the full_text_chunks give you the doses and study designs behind it, each labeled with the section of the paper it came from.
What people build with the API
What you can build with the Consensus API
Teams use the API to power internal research tools, field-monitoring agents, and scientific agents. Phylo calls it directly from its agents to screen about 20,000 drug targets across hundreds of diseases. Browse the use cases.
- Internal tools: paper search for scientific agents, field-monitoring agents, and literature tables that fill themselves.
- Research systems: literature review pipelines, citation-grounded writing, and recurring evidence reports.
Full text in the API
Every search reaches inside the paper. Queries are matched against full text where available, and on paid plansinclude_full_text_chunks=true returns the passages from each open-access paper that answer your query.
Full text in the API
What comes back, which papers have excerpts, plan availability, and how to use them.
Authentication
Every request must include your API key in thex-api-key header.
Don’t have a key yet? Create an API key from your API & MCP Dashboard at consensus.app/api-mcp. See plans and access for what each plan includes.
Make your first request
Pass aquery — the only required parameter. Store your key in an environment variable named CONSENSUS_API_KEY first.
Next steps
Search endpoint reference
Full parameter list, response schema, and interactive playground.
API on GitHub
Client code, examples, and issues for the Consensus API.
MCP server
Prefer a no-code path? Connect Consensus to Claude, ChatGPT, and other MCP clients.
Consensus website
Explore the Consensus research platform.