Documentation v1.24
Last updated 2026-10-27 Give feedback

SDK Purchase Flow

Your own agent can search, browse, and reason independently, then call Aftercard SDK to resolve a protected value or run a protected payment action.

Your runtime hands the protected step to Aftercard

When To Use The SDK

Use the SDK when your application already owns the surrounding agent, browser, worker, or MCP tool and needs a typed Aftercard client for sessions, requests, data resolution, and actions.

Flow

Your agent runs until it reaches a protected step — payment, login, identity, confirmation — then hands only that step to Aftercard.

  1. Create or reuse an Aftercard workflow session.
  2. Create a data, action, or choice request with a stable client request id.
  3. Wait for user approval or supplied data.
  4. Use the returned artifact only in the trusted browser or provider call.
  5. Resume the agent workflow after Aftercard reports the result.

Minimal SDK Shape

A typical purchase uses sessions, data resolution, action execution, and result waiting.

TypeScript
const { session } = await client.sessions.create({ type: 'payment' }); // The agent never sees raw data; it asks for a value or a use-approval.const handle = await client.memory.createRequest(session.id, input);const result = await client.memory.waitForResult(session.id, handle);
Aftercard public documentation.