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 Keplar→
  • Product
  • Live demo
  • Create
  • Create showcase
  • Keplar-One
  • Teams
  • Resources
  • API and widget
  • Community gallery
  • Changelog
  • Roadmap
  • Security
  • Pricing
  • Download
Sign InTry 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

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.

Updated October 3, 20262 min read

On this page
  1. What counts as a disagreement
  2. What the section contains
  3. It is not invented
  4. Minority positions
  5. Why a missing model is not a disagreement
  6. Using a disagreement
  7. When you see none

The disagreement section is often the most valuable part of an answer. It tells you where the answer is soft.

What counts as a disagreement

A disagreement exists when the comparison found more than one position: two or more distinct stances on the question, each held by at least one responding model. Different wording or different level of detail is not a disagreement. Different conclusions, different recommendations, or different factual claims are.

What the section contains

For each disagreement, Keplar records:

  • the topic the models split on;
  • the positions, each with a short label and a one-sentence summary;
  • which models took each position;
  • a one-line resolution: how the final answer handled it.

The synthesis also writes a "Where the models disagree" passage in the answer text, so you do not have to open the section to learn about it.

It is not invented

Writing models like to produce a tidy "points of view" paragraph even when there is none. Keplar blocks this in code. After synthesis, the heading and text of a disagreement section are removed unless the comparison found at least two positions. Sections you asked for yourself (a counterargument, or "where economists disagree") are never touched.

Minority positions

Keplar does not treat a majority as correct. The reviewer and the synthesizer weigh the evidence and reasoning behind each position, and a minority can win if its reasoning holds and the majority's does not. When a minority view is rejected, the answer says why. When it is kept, it is labeled as dissent.

Why a missing model is not a disagreement

If a model times out or declines, nothing is learned about its position. It is a missing vote, shown separately. See Missing models and timeouts.

Using a disagreement

  1. Read the positions and their reasons. The reasons are what you can check.
  2. Find the hinge. Most splits turn on one assumption or fact ("depends on interest rates", "depends on how many users").
  3. Ask a narrower follow-up about the hinge, for example "Assume the budget is fixed at $500. Which position holds?"
  4. Check the one fact that decides it at a primary source.

When you see none

No disagreement section means the models that responded took one position. It does not mean the answer is verified. If the stakes are high, ask for the strongest counterargument explicitly: "Give the best case against your recommendation."

Related

  • 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.
  • The verification review: What the verifier or judge actually does: it reads the draft against each model's response and flags reasoning gaps, contradictions and unsupported claims. It does not browse or open sources.
  • How the final answer is written: The draft, review and final synthesis steps: weighing evidence over headcount, keeping minority views honest, and what happens if synthesis fails.
PreviousAgreement and the consensus levelNextThe verification review

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. What counts as a disagreement
  2. What the section contains
  3. It is not invented
  4. Minority positions
  5. Why a missing model is not a disagreement
  6. Using a disagreement
  7. When you see none