Skip to main content
POST
Create Agent Checkout

Authorizations

X-API-KEY
string
header
required

Client-side API key (ck_...) with the agent-checkouts.* scopes.

Authorization
string
header
required

JWT identifying the end user, issued by an external auth provider your project trusts.

Body

application/json
target
object
required
constraints
object
required
packId
string<uuid>

Optional legacy field: the id of a pack that guides the agent through this merchant's checkout. A checkout targets one merchant, so at most one pack applies. The applied pack is echoed back on the checkout view's pack field.

buyerProfileId
string<uuid>

Optional id of a saved buyer profile whose name, contact, and shipping the agent prefills instead of asking.

metadata
object

Optional string key/value pairs echoed back on the checkout.

Response

The agent checkout has been initiated.

The full checkout view, returned by create, get, and cancel.

id
string<uuid>
required

The checkout id.

status
enum<string>
required

Lifecycle state. succeeded, failed, and cancelled are terminal.

Available options:
queued,
running,
awaiting_user_action,
succeeded,
failed,
cancelled
target
object
required
constraints
object
required
progressItems
object[]
required
browser
object
required

The live browser session the agent is driving.

createdAt
string<date-time>
required
updatedAt
string<date-time>
required
pack
object

Present on the checkout view when a pack drove the run. The pack id, merchant name, and phases used are captured on the run so they survive a later edit or deletion of the pack.

pendingUserAction
object

Present when status is awaiting_user_action. Render a form from responseSchema and submit matching values.

receipt
object

Present when status is succeeded.

failure
object

Present when status is failed.

metadata
object

Optional string key/value pairs echoed back on the checkout.