OpenAI Software / SaaS United States

Consensus

Enterprise Knowledge Search

Consensus needed to move beyond search so researchers could plan, read, interpret, and connect millions of papers without spending most of their time manually assembling evidence.

More than 220 million papers indexed
More than 8 million researchers worldwide
Question to conclusion in minutes instead of weeks
Revenue increased 8x

Reported impact

Business outcome

Consensus now completes research tasks in minutes instead of weeks, serves more than 8 million researchers worldwide, and increased revenue 8x while preserving a strict standard for cited, low-hallucination scientific answers.

  • Productivity Improvement
  • Scalability

Solution

Consensus re-architected its science search product into Scholar Agent, a multi-agent research assistant built on GPT-5 and the Responses API. Instead of generating answers directly from search results, the system first performs context engineering: a Planning Agent decides what evidence is needed, a Search Agent gathers papers from Consensus' index, private libraries, and citation graphs, a Reading Agent interprets papers individually or in batches, and an Analysis Agent synthesizes the findings into the final structured output. Each agent has a narrow scope, which improves discipline and reduces hallucinations, and every answer is backed by a research context pack containing papers, metadata, and key findings. Consensus also tuned the system to refuse unsupported answers when evidence does not meet the quality threshold, then used evaluation pipelines for citation traceability and stylistic consistency so the assistant can grow with new models and new agent types over time.

Data flow

A researcher question enters Scholar Agent, where the Planning Agent decides the workflow. The Search Agent gathers papers and citation links, the Reading Agent interprets the material, and the Analysis Agent composes a grounded response with a research context pack so every claim traces back to source studies.

Solution architecture

7 components · 4 layers
  1. Ingest
    • Search Agent Searches Consensus' paper index, private libraries, and citation graphs for relevant evidence.
  2. Compute
    • GPT-5 Provides the long-context reasoning and tool-calling performance behind Consensus' multi-agent workflows.
    • Reading Agent Interprets scientific papers individually or in batches before synthesis.
  3. Serving
    • Scholar Agent Coordinates the end-to-end agent workflow that turns a research question into a grounded answer.
    • Analysis Agent Synthesizes evidence, determines structure and visuals, and composes the final answer.
  4. Orchestration
    • Responses API Supports multi-agent routing with better reliability and cost control than the previous interface.
    • Planning Agent Breaks down the user's question and decides which research actions to take next.

Architecture clues

  • Context engineering builds a research context pack before generation begins
  • Each agent has a narrow scope to reduce hallucinations
  • Responses API replaced Chat Completions for multi-agent routing
  • The system can decline to answer when evidence quality is insufficient

Evidence from the source

"Consensus has expanded rapidly, growing to more than 8 million researchers worldwide and increasing revenue by 8x."
"Every answer comes with a "research context pack""
"If the system can't ground an answer in real evidence, it won't make one up."
"Scholar Agent is a multi-agent system built on GPT-5 and the Responses API."
Transparency Evidence & methodology 95/100 reference value · 94% confidence · 3 sources

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value95/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence94%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency9/10
    3 source references document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. OpenAI

    Consensus customer story

    First-party
    https://openai.com/index/consensus/
    Source type
    Vendor-published customer story
    Published
    Oct 23, 2025
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date
  2. Consensus

    Learn more about Consensus & our mission

    First-party
    https://consensus.app/home/about-us/

    The official about page says, "What began as a remote-first company, Consensus now calls San Francisco home."

    Source type
    Official company website
    Supports
    • Region
  3. Built In

    Consensus Careers, Perks + Culture | Built In

    Independent secondary
    https://builtin.com/company/consensus

    The Organization JSON-LD on the profile lists "numberOfEmployees":{"@type":"QuantitativeValue","value":150}, which maps to SMB under the 0-249 rule.

    Source type
    Structured company profile
    Supports
    • Company size

Date evidence

  • Published on source page Oct 23, 2025 · OpenAI · First-party
    Open date source
Not separately sourced Industry. Treat these normalized attributes as lower-confidence until a dedicated source is added.