FAQ / current scope
Frequently asked questions
Find clear answers about AnswerUp Core, Private Preview access, packages, integrations, and using the developer portal.
Frequently asked questions
What is AnswerUp Core?
A provider-neutral reliability layer for consequential agent actions. It separates proposal, protected execution, verification, reconciliation, and safe claims.
Who is it for?
Builders, organizations applying agents internally, and product teams embedding agent-powered experiences.
Does AnswerUp replace my model, agent framework, or provider?
No. Your model, agent framework, interfaces, providers, and authoritative systems remain yours.
Does AnswerUp perform provider I/O?
The portal does not. The product boundary separates provider and verifier responsibilities; this local preview makes no live provider call.
What does provider-neutral mean?
The reliability boundary is not tied to one model, agent framework, or provider. Planned adapter surfaces remain planned.
Why is provider acknowledgment not effect truth?
An acknowledgment describes what a provider reported. Effect truth comes from reading authoritative state after the attempt.
What happens when an outcome is UNKNOWN?
Treat it as unresolved. Reconcile the exact live handle and do not make a success or failure claim or blindly redispatch.
Does AnswerUp automatically retry?
No. Automatic blind retry is not part of this boundary.
Is AnswerUp a hosted execution service?
No. This portal does not provide hosted execution or a hosted control plane.
What is available in the private preview?
The frozen package chain is Core 1.0.0-rc.1, Runtime 0.2.0-preview.1, Actions 0.2.0-preview.2, and Retell 0.2.0-preview.1. Documentation and enrollment are separate from package access.
Does enrollment grant package access?
No. Enrollment and package access remain separate decisions. The portal does not issue credentials or package access.
Are packages publicly downloadable?
No public download or registry claim is made here.
What is the current process-loss certification limitation?
Abrupt process-loss cleanup remains unproven, so the current evidence is not a production-readiness certificate. See Current release status for the technical boundary.
What support is currently available?
Documentation and self-service guidance are available. No production support channel is configured in this portal; see Support for the safe way to ask for help.