vault

Submit a prune intent (owner)

Publishes the owner-signed prune_intent. Everything fallible happens before the intent's pre-I/O fence; once that transaction commits nothing refuses and the platform worker replays the remaining steps identically, so stored: false means “the create-only intent write is not yet observed”, never “this failed”. The request body is read as exact bytes — the intent is strict-parsed and signature-verified over exactly what you sent, so send it with Content-Type: application/json and do not let a client library re-serialize it.

post/vaults/v1/{vault_id}/prune-intents

Request

  • Base URL: https://api.run402.com
  • URL: https://api.run402.com/vaults/v1/{vault_id}/prune-intents
  • Auth: one of:
    • API key in header SIGN-IN-WITH-X
    • 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

object required

The complete signed prune_intent object, sent verbatim.

Response

Intent fenced (and, when observed, stored)

object_idstring
repo_idstring
statestring
gc_epochstring
candidate_countinteger
storedboolean
next_actionsobject[]

Changes

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