vault

Exchange a capture receipt for an activation token

Mints the activation_token an apply commit consumes exactly once inside its activation transaction. The receipt's own service signature is verified first, then every binding is re-checked against the operation and the vault: capture id, canonical plan digest, snapshot commitment, owning vault, and the installed authorization_epoch. A generation a repair superseded is refused. An ISSUED token for the same operation and head is returned again with 200 and reissued: true — minting is idempotent, consumption is not.

post/vaults/v1/{vault_id}/activation-tokens

Request

  • Base URL: https://api.run402.com
  • URL: https://api.run402.com/vaults/v1/{vault_id}/activation-tokens
  • Auth: one of:
    • API key in header SIGN-IN-WITH-X
    • HTTP bearer
    • HTTP bearer

Path parameters

vault_idstring required

The vault id (src_<32 hex>); the wire field is repo_id (protocol D185).

Headers

SIGN-IN-WITH-Xstring required

SIWX auth header — base64-encoded JSON payload containing a signed CAIP-122 (EIP-4361) message. See https://docs.x402.org/extensions/sign-in-with-x.

Request body

operation_idstring required

The apply operation the token binds to.

capture_receiptobject required

The signed capture_receipt returned by the admission, verbatim.

Response

Reissued — an ISSUED token for this operation and head already existed

activation_tokenobject
object_idstring
reissuedboolean
next_actionsobject[]

Changes

No recorded changes to this operation across all 1 revision of this API.