vault

Open the repair resource lane (owner + step-up)

Owner + step-up (gitvault.repair). Opens a BOUNDED reservation covering everything a repair needs — session issuance, finalized-object count, and temporary storage — so cap exhaustion by a copied writer key can never starve the owner's repair. One pending attempt per vault; the lane carries its own tighter per-day limit and its own audit trail. A grant-key context can never bind a session to a repair attempt.

post/vaults/v1/{vault_id}/repair-attempts

Request

  • Base URL: https://api.run402.com
  • URL: https://api.run402.com/vaults/v1/{vault_id}/repair-attempts
  • 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

reserved_sessionsinteger required
reserved_objectsinteger required
reserved_storage_size_bytesinteger required
preempted_maintenance_cycle_idstring nullable

Response

Repair lane opened

repair_attempt_idstring
repo_idstring
outcome'pending' | 'canonized' | 'lost' | 'reaped'
preempted_maintenance_cycle_idstring nullable
reserved_sessionsinteger
reserved_objectsinteger
reserved_storage_size_bytesstring

Decimal byte count as a string (values exceed 2^53).

used_sessionsinteger
used_objectsinteger
used_storage_size_bytesstring

Decimal byte count as a string (values exceed 2^53).

admission_idstring nullable
created_atstring date-time nullable
resolved_atstring date-time nullable

Changes

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