Consensus for enterprise

Three ways to deploy

Shape	How it works	Best for
Per-user OAuth	Each person connects an MCP client (Claude, ChatGPT, Cursor, and others) and signs in to their own Consensus account. No admin work.	Teams that already run AI tools and want individual usage and limits.
Shared gateway credential	Your AI gateway or MCP registry holds one Consensus API key server-side and proxies requests for everyone behind it. No user redirects, no token refresh.	Organizations that route all AI traffic through a gateway (TrueFoundry, LiteLLM, Azure API Management, and others).
Microsoft 365 Copilot	An admin adds Consensus as a federated connector; users connect it under Sources in Copilot Chat.	Microsoft 365 shops where users can’t add sources themselves.

All three hit the same server, the same index, and the same tools. Mixing them is fine.

Guides

Connection reference

Endpoint, transport, authentication options, discovery documents, and the firewall allowlist. Everything a gateway needs.

Microsoft 365 Copilot

For admins: add Consensus as a federated connector so it appears in your users’ Sources.

Microsoft Copilot Studio

Add Consensus as a Model Context Protocol tool in your own agents.

AI gateways

Register Consensus in TrueFoundry, LiteLLM, Cloudflare, IBM ContextForge, Azure API Management, AWS AgentCore, Portkey, Obot, and more.

Security and data handling

SOC 2 Type II compliant. What leaves your network, what comes back, and what Consensus stores.

Single sign-on

Connect Microsoft Entra ID, Okta, OpenAthens, or any SAML 2.0 identity provider, with optional SCIM provisioning.

Need help?

Enterprise plans include custom rate limits, page sizes up to 1,000 papers, DOIs and full-text excerpts in results, and setup support. Consensus is SOC 2 Type II compliant and supports SAML 2.0 single sign-on. To set up SSO, get a confidential OAuth client for your gateway, raise limits, or get help with a platform that isn’t documented here, talk to sales.

​Three ways to deploy

​Guides