Skip to content
  • Everything in KeplarEvery feature and whether it is liveLive demoAsk a question now, no sign-upCreateDescribe or speak a site or appCreate showcaseDemos that set the barKeplar-OneThe engine behind every answerTeamsShared workspaces, roles and approvals
  • DocsHow everything worksAPI and widgetKeys, endpoints, embed scriptCommunity gallerySites people chose to shareChangelogWhat shipped, whenRoadmapWhat is next, what is not doneSecurityHow your data is protected
  • Pricing
  • Download
Sign InTry KeplarOpen Keplar→
  • Product
  • Live demo
  • Create
  • Create showcase
  • Keplar-One
  • Teams
  • Resources
  • API and widget
  • Community gallery
  • Changelog
  • Roadmap
  • Security
  • Pricing
  • Download
Sign InTry KeplarOpen Keplar→

One question. Multiple intelligences. One answer.

team@keplar.one

Product

  • Everything in Keplar
  • Overview
  • Live demo
  • How it works
  • Create
  • Create showcase
  • Community gallery
  • Keplar-One
  • Pricing
  • Download

Use Keplar

  • For you
  • For business
  • Agents
  • API and widget
  • Referral program
  • Create an account

Learn

  • AI answer engine
  • Compare AI models
  • AI study tool
  • AI slideshow maker
  • What is superintelligence?
  • Multi-model AI
  • Models we use
  • Guides
  • Docs
  • Blog
  • Changelog
  • Roadmap
  • Glossary
  • Prompt library

Company

  • About
  • Inquire
  • Help
  • Contact
  • Status

Legal

  • Privacy
  • Terms
  • Security

© 2026 Keplar One.

Theme
Keplar docs
Get started
  • Overview
  • What is Keplar?
  • Quickstart: ask your first question
  • Read a Keplar answer
  • Accounts and sign-in
  • What changes on a paid plan
  • What Keplar cannot do
How Keplar works
  • Overview
  • The pipeline, end to end
  • How Keplar understands a question
  • Which questions use more models
  • Routing and panels
  • Model families and diversity
  • Agreement and the consensus level
  • Disagreement detection
  • The verification review
  • How the final answer is written
  • Missing models, timeouts and stand-ins
  • Exact checks for counting and arithmetic
  • Sources, citations and web lookups
  • Small talk and simple questions
  • Why consensus can be wrong
  • A worked example, step by step
Using Keplar
  • Overview
  • Thoroughness modes
  • Write better questions
  • Attach images and video
  • Follow-ups and saved chats
  • Memory: what Keplar remembers about you
  • Share an answer
  • Deep Research
  • Study mode
  • Slideshow creator
  • Voice dictation
  • Use connected apps in chat
Create
  • Overview
  • Create overview
  • Build a site
  • Import a product from a link or photo
  • Generate images
  • Generate video (Beta)
  • Publish your site
  • Connect a custom domain
  • Create limits by plan
Connectors and agents
  • Overview
  • Connected apps (MCP) overview
  • Add a connection
  • Connect with OAuth (Beta)
  • Tool permissions and approvals
  • Agents overview
  • Agent guardrails
  • Agent schedules
  • Business tools: forms, CRM, inbox and dashboard
Plans, credits and limits
  • Overview
  • Plans compared
  • Credits explained
  • Rolling usage limits
  • Free plan limits and behavior
  • Upgrade, downgrade and cancel
  • When you reach a limit
Desktop app
  • Overview
  • Install the desktop app
  • Sign in on the desktop app
  • Desktop troubleshooting
Privacy and security
  • Overview
  • How Keplar handles your data
  • Free plan privacy
  • Delete and export your data
  • Account security
  • Connected app security
  • Published sites and safety
  • Report a vulnerability
Reference
  • Overview
  • The model roster and roles
  • Answer sections reference
  • Limits at a glance
  • Developers and API status
  • Messages and what to do
Docs menu
Keplar docs
Get started
  • Overview
  • What is Keplar?
  • Quickstart: ask your first question
  • Read a Keplar answer
  • Accounts and sign-in
  • What changes on a paid plan
  • What Keplar cannot do
How Keplar works
  • Overview
  • The pipeline, end to end
  • How Keplar understands a question
  • Which questions use more models
  • Routing and panels
  • Model families and diversity
  • Agreement and the consensus level
  • Disagreement detection
  • The verification review
  • How the final answer is written
  • Missing models, timeouts and stand-ins
  • Exact checks for counting and arithmetic
  • Sources, citations and web lookups
  • Small talk and simple questions
  • Why consensus can be wrong
  • A worked example, step by step
Using Keplar
  • Overview
  • Thoroughness modes
  • Write better questions
  • Attach images and video
  • Follow-ups and saved chats
  • Memory: what Keplar remembers about you
  • Share an answer
  • Deep Research
  • Study mode
  • Slideshow creator
  • Voice dictation
  • Use connected apps in chat
Create
  • Overview
  • Create overview
  • Build a site
  • Import a product from a link or photo
  • Generate images
  • Generate video (Beta)
  • Publish your site
  • Connect a custom domain
  • Create limits by plan
Connectors and agents
  • Overview
  • Connected apps (MCP) overview
  • Add a connection
  • Connect with OAuth (Beta)
  • Tool permissions and approvals
  • Agents overview
  • Agent guardrails
  • Agent schedules
  • Business tools: forms, CRM, inbox and dashboard
Plans, credits and limits
  • Overview
  • Plans compared
  • Credits explained
  • Rolling usage limits
  • Free plan limits and behavior
  • Upgrade, downgrade and cancel
  • When you reach a limit
Desktop app
  • Overview
  • Install the desktop app
  • Sign in on the desktop app
  • Desktop troubleshooting
Privacy and security
  • Overview
  • How Keplar handles your data
  • Free plan privacy
  • Delete and export your data
  • Account security
  • Connected app security
  • Published sites and safety
  • Report a vulnerability
Reference
  • Overview
  • The model roster and roles
  • Answer sections reference
  • Limits at a glance
  • Developers and API status
  • Messages and what to do

Docs/How Keplar works

Agreement and the consensus level

How Keplar groups responses into positions, weights them by support, and turns that into a consensus level, and what the number does and does not mean.

Updated October 3, 20262 min read

On this page
  1. From responses to positions
  2. Weighting by support
  3. The levels
  4. Counts, not a percentage
  5. Missing votes are not dissent
  6. How to use the number

"Consensus" in Keplar means one specific, limited thing: how much the models that responded agree with each other. It is not a probability that the answer is right.

From responses to positions

After the panel answers, one classification call reads the responses and does three things:

  1. Labels each response as answered, declined or off-topic. Declines become missing votes.
  2. Groups the answered responses into positions: a short label and a one-sentence summary for each distinct stance.
  3. Extracts up to eight load-bearing claims and records which responses make each one.

If that output cannot be read reliably, agreement is shown as not scored. Keplar does not fill the gap with a guess.

Weighting by support

Each position is weighted by how well supported its claims are across the responses, not simply by how many models hold it. A position backed by claims several models make independently counts for more than one resting on a claim only one model made. This is why the final level can differ from a naive head count.

The levels

LevelMeaning
ConsensusThe positions agree strongly once weakly supported claims are set aside
PartialThe models mostly agree but one or more meaningful differences remain
No majorityThe models are split without a dominant position
Not applicableA single model answered, so there was nothing to compare
Not scoredThe comparison could not be read reliably

Internally these map to a score with cut-offs (a score of about 80 and above is consensus, about 60 and above is partial). The thresholds can change, so the app shows the level and the counts rather than a number.

Counts, not a percentage

Under the answer you see how many models agreed, how many disagreed and how many responded. Keplar chose counts over a percentage because a percentage looks like a measure of truth. Three of three is not three times as true as two of three, and neither is a statement about the world.

Missing votes are not dissent

A model that times out, fails or declines is excluded from the comparison, and the answer says "n of m responded". It is never counted against the answer. See Missing models and timeouts.

How to use the number

  • Strong agreement from different families is mild reassurance on a question where models are likely to know the answer.
  • Strong agreement on a recent or niche fact deserves suspicion; models share training gaps.
  • A split is the most useful result: it tells you exactly what to check. Read Disagreement detection.

Related

  • Disagreement detection: How Keplar finds where models split, how the Disagreements section is built, why it appears only when the split is real, and how to use it.
  • Why consensus can be wrong: The limits of agreement between models: shared training data, shared blind spots, stale knowledge and leading questions, and what to do about each.
  • Read a Keplar answer: A tour of the six sections under every multi-model answer, what each one means, and what it does not mean.
PreviousModel families and diversityNextDisagreement detection

Questions this page does not answer? Write to team@keplar.one, or try Keplar on your own question.

Try Keplar freeOpen Keplar→

On this page

  1. From responses to positions
  2. Weighting by support
  3. The levels
  4. Counts, not a percentage
  5. Missing votes are not dissent
  6. How to use the number