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

Missing models, timeouts and stand-ins

What happens when a model is slow, refuses or fails: why it is never counted as disagreement, how stand-ins work on Free, and how to retry with all models.

Updated October 3, 20262 min read

On this page
  1. The shared time budget
  2. What a missing model looks like
  3. Stand-ins on the Free plan
  4. Retries and fallbacks
  5. Failed calls and credits
  6. Why it matters

A multi-model answer depends on several providers being up and quick. Sometimes one is not. Keplar's rule is simple: an absence is never evidence.

The shared time budget

A run has one latency budget (60 seconds by default). The panel may use a bit over half of it. Once a quorum has answered (at least two models and at least half the panel), models still working get a short extra window: the longer of six seconds or three quarters of the time taken so far. A model that misses its window is a timeout. Classification, drafting, review and synthesis then share what remains, each with a small minimum. A stage that runs out of time says so.

What a missing model looks like

Under the answer, a plain sentence such as: "2 of 3 models answered (A and B). C ran out of time. It is not counted as a vote for or against the answer." A Retry with all models button re-runs the question.

EventShown asCounted as dissent?
TimeoutMissingNo
Refusal or declineMissingNo
Provider errorMissingNo
Off-topic responseMissingNo
A different stanceA positionYes, as a disagreement

Stand-ins on the Free plan

Free-model hosts are rate limited and can stall. On Free, if one model has answered and another seat is still silent after about half the first answer time (and at least three seconds), Keplar starts a different free model in parallel. Whichever answers first fills the seat. The answer then lists it under its own name with a note such as "Stood in for X, which was slow to answer." Paid plans do not do this, because a second paid call costs real money; they use fallbacks instead.

If every free panel model is busy you see: "The free models are busy right now. Try again in a minute, or upgrade for the paid model panel."

Retries and fallbacks

A rate limit (429) or server error (5xx) is retried with backoff, honoring the provider's Retry-After header. If retries fail, the request goes to another route when one exists. A refusal is not retried elsewhere.

Failed calls and credits

Failed calls count nothing. A run that produces no reliable answer is not charged. Costs are recorded from what providers actually billed.

Why it matters

If missing votes counted as dissent, a slow server could turn a consensus into a false split. If they were ignored silently, you could believe three models agreed when two answered. The answer states who answered.

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.
  • Free plan limits and behavior: Up to 50 questions a day, free open models only, the three-model cap, stand-ins when models are busy, refunded daily counts and what Free cannot do.
  • Messages and what to do: The messages you may see in Keplar, such as busy free models, too-large questions, attachments, no vision models and generic failures, with causes and fixes.
PreviousHow the final answer is writtenNextExact checks for counting and arithmetic

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 shared time budget
  2. What a missing model looks like
  3. Stand-ins on the Free plan
  4. Retries and fallbacks
  5. Failed calls and credits
  6. Why it matters