Revoke a source-access wrapper
Revokes one of the caller's own wrappers (step-up required for a control-plane session — wrapper revocation is recovery-posture-affecting; a SIWX wallet is inherently fresh). The last-wrapper rule is CUSTODY-SCHEME-AWARE (consult round 1): a wrapped_random_v1 key can never reach zero active wrappers while active — its last revoke requires deactivate_key: true, which revokes the KEY atomically with the wrapper; a wrapped_legacy_scalar_v1 (migrated) key allows confirm_last_wrapper: true, because its original enrollment passkey can still derive the scalar (wrapper revocation is not cryptographic revocation — rotate the key to detach that credential). Deny → 403 never 404: a foreign wrapper id and a nonexistent one are indistinguishable.
Request
- Base URL: https://api.run402.com
- URL: https://api.run402.com/agent/v1/source-access/wrappers/{wrapper_id}
- Auth: one of:
- API key in header SIGN-IN-WITH-X
- HTTP bearer
Path parameters
Headers
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
Response
Wrapper revoked
Changes
No recorded changes to this operation across all 1 revision of this API.