AnswerUpDevelopers
PUBLIC DOCS

Documentation

Understand, try, build and troubleshoot.

Follow the current first-action path. Use the concepts, API and recovery references as you need them.

Diagnostics & Logging →Readable logs, JSONL, Trace Local and troubleshooting.

Try your first action

Run your first action, understand its result and adapt it to your application.

Follow the first integration path →

Concepts

Learn how AnswerUp checks intent, authorizes an action and verifies what happened.

Read concepts →

Build guidance

Connect your business functions, check outcomes and handle the result.

Choose a build path →

Patterns

Use established patterns for business operations, verification and recovery.

Explore patterns →

API Reference

Inspect versioned package-root signatures for Core, Runtime and Actions; Retell preview.1 signatures are historical.

Browse the API →

Diagnostics & Logging

Read execution logs, work with JSONL observations and inspect supplied evidence in Trace Local.

Explore diagnostics →

Recovery

Check an uncertain outcome in the same process or after a restart, without repeating the write.

Compare recovery paths →

Integration previews

Compare the current HTTP and Retell examples and their tested scope.

Browse integration previews →

Developer Manual

Implement, test, troubleshoot, persist, recover, and operate a host-owned integration.

Open the Manual →

Explore your path

An application

Add governed actions to an app you control.

You own the application and its backend.

Explore An application

Business workflows

Connect your organization’s systems and policies.

Your organization owns systems, policies and operations.

Explore Business workflows

A customer-facing product

Embed governed actions in a product your customers use.

You own tenant boundaries and customer-facing claims.

Explore A customer-facing product
View the full integrity boundary diagram

One reliability boundary

Keep ownership where it belongs.

Your application and systems stay yours. The @answerup/core package governs and classifies the protected lifecycle.

Request / lifecycleSeparate labeled return flowOwnership boundary
Integrity BoundaryOrigins remain with the proposing application. AnswerUp owns lifecycle authority and classification: grounding comes before authorization, and verified effect truth bounds claim permission. Provider transport, credentials, authoritative systems, persistence, and independent verifier I/O remain host-owned; Core performs none of that I/O.The diagram has a keyboard-accessible full-size view.Open desktop fileOpen mobile file

Integrity Boundary

Request / lifecycleSeparate labeled return flowOwnership boundary
Integrity Boundary showing an application proposal entering AnswerUp-owned lifecycle authority, then host-owned execution and authoritative state, with independent verification returning effect truth before a bounded claim.

Origins remain with the proposing application. AnswerUp owns lifecycle authority and classification: grounding comes before authorization, and verified effect truth bounds claim permission. Provider transport, credentials, authoritative systems, persistence, and independent verifier I/O remain host-owned; Core performs none of that I/O.

What the diagram shows

Your application retains its providers, credentials, records, authoritative systems, and verifier I/O. AnswerUp governs lifecycle authority and classification; the Core package returns bounded claim permission only from independently verified evidence.