Skip directly to article

Local synthetic example

Generic HTTP reference preview

Connect AnswerUp to your existing HTTP workflow. Your application sends the request, and a separate verifier checks the system of record. The runnable example shows how to handle a lost response and check the original operation without sending it again.

Using the preview packages

Approved preview participants can download the selected archives from Package access. Sign in to continue, or explore the package-free guided tour while you wait for approval.

Package and historical reference boundaries

Current package set: Core rc.1, Runtime preview.5 and Actions preview.8. Try HTTP reference preview.4 or Retell adapter preview.3 with equipment example preview.4.

Version history and scope

Retell preview.1 declarations describe the older Runtime preview.1 / Actions preview.2 line. Retell preview.2 uses a mock facade; HTTP preview.1 simulates bookkeeping. The older private HTTP source uses Runtime preview.3 / Actions preview.4. These are separate from the current runnable examples.

Examples use local test systems. They do not validate live providers, arbitrary crashes or distributed durability. Approved participants can use protected downloads.

Current: start with the executable HTTP reference

Extract, install and run the HTTP example →

@answerup/generic-http-reference@0.2.0-preview.4 executes packed Actions preview.8 on actual localhost application, provider mutation and exact-effect verifier sockets. The provider saves a mutation before deliberately losing a socket response; a fresh host process rehydrates the accepted V2 record and checks without redispatch. If you already received the selected archive, follow the complete starting path. Protected Portal downloads are enabled for authorized participants; public or unauthenticated downloads remain unavailable. SHA-256: 7a95340d0cb02dc2c45ddb2f3a9a1914022cc65e8940845a723e9620fc015708.

Start with try-answerup/01-first-action and npm start; then run the full npm run demo -- .demo/first-run recovery path. Expect UNKNOWN, UNKNOWN, UNKNOWN, COMMITTED, COMMITTED, one provider mutation, three verifier reads, and zero recovery redispatches. The application accepts requestId, action, and input over HTTP. The separate recover CLI is a host operator path, and the included guide explains accepted records, finality and bounded claims. The example uses test tokens, a local test provider and single-writer JSON storage; a live provider and arbitrary-crash durability are untested.

Requires Node 22 or newer and the exact included Core rc.1, Runtime preview.5 and Actions preview.8 archives. Extract into a fresh directory and use the packed README from the extracted package root. Manual checksum verification is optional; if a check finds a mismatch, download a fresh copy before using it.

Historical preview.1 simulation

Preview.1 simulated classifications and bookkeeping; its CLI did not execute HTTP requests or the declared AnswerUp dependencies. Its counters and saved records were test data, not evidence of SDK execution or durable recovery.

Those commands are superseded by the selected preview.4 first-action and recovery instructions above. The historical archive is not part of the current package set. See version history for the compatibility context.