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

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.

Updated October 3, 20262 min read

On this page
  1. The sequence
  2. The rules the synthesizer follows
  3. If synthesis fails
  4. Streaming
  5. Quality gate
  6. What synthesis cannot do

Synthesis is the step where several responses become one answer. Done badly it averages everyone into mush or quietly copies the loudest model. Keplar's design tries to avoid both.

The sequence

  1. Draft. A stronger "judge-tier" model writes a draft from the positions and claims (with how many responses support each), not from raw transcripts. When little time is left, a structured draft is produced instead of prose.
  2. Review. The verifier, or the judge when the panel split, reads the draft against the individual responses. See The verification review.
  3. Final answer. The judge-tier model writes the answer from the positions, the claims and their support, the reviewer's findings and the draft.

The rules the synthesizer follows

  • Weigh evidence and reasoning, not headcount. A position held by one model with good reasons can outweigh two with weak ones.
  • Show disagreement only when it exists. A "Where the models disagree" section is written only if there was a split, and removed in code otherwise.
  • Label counterarguments. If you asked for the best case against something, that section is labeled as a counterargument, not presented as Keplar's own view.
  • Return a one-line resolution for each disagreement, used in the disagreement readout.
  • Do not invent sources. Only links the models cited are listed, labeled as cited by them.
  • Do not claim certainty it lacks. No confidence score or accuracy figure is produced.

If synthesis fails

If the final write-up cannot be produced, Keplar lists the positions the models took. It does not paste one model's response verbatim as if it were the combined answer.

Streaming

The answer is generated as a whole and then streamed to the page in chunks, so it appears progressively. True token-by-token streaming from the model is not in place today.

Quality gate

Before a single-model answer is shown or charged, a quality check rejects obvious failures such as repeated chunks, loops, a high ratio of non-words, or incoherent windows of text (code, JSON and non-English text are skipped). A rejected answer falls back to the next model. If every answer fails, you see "Keplar couldn't produce a reliable answer this time, and nothing was charged. Please retry."

What synthesis cannot do

It cannot add knowledge the models lack, and it cannot make a wrong consensus right. It can only organize, weigh and present what they said, plus the review.

Related

  • 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.
  • 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.
  • The pipeline, end to end: The eight steps between your question and one answer: understand, select, compare, disagree, verify, synthesize, and answer, with where each can stop early.
PreviousThe verification reviewNextMissing models, timeouts and stand-ins

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. The sequence
  2. The rules the synthesizer follows
  3. If synthesis fails
  4. Streaming
  5. Quality gate
  6. What synthesis cannot do