vault

List every stored object in the vault

Keyset-paginated enumeration of every stored artifact under the vault's prefix — the client-uploaded kinds, the server-authored kinds (retention_cutoff tickets, prune intents/completions, maintenance issuances/cuts/terminals), AND the vault's head chain (every COMMITTED generation's head/vault_genesis object plus its admission_record, incl. genesis at generation 0000000000000000 — fetch head bytes via GET .../heads/{generation} and admission-record bytes via GET .../admissions/{generation}, not via object-reads) — each entry naming its storage key, kind, stored-bytes hash, and size: exactly what a client-side mirror reconcile needs to diff against a mirror. sha256/size_bytes on head-chain entries are always the ledger's exact stored-bytes hash/length (never estimated, never null). NOT an r402s/v0 protocol object (no format, no wire revision) — a platform-only read surface. Excludes the same tombstoned lifecycle states presigned reads exclude (DELETING / DELETED / PRUNE_AUTHORIZED_PRESENT), so every listed key is fetchable. cursor is opaque and bound to this vault; a malformed, tampered, or cross-vault cursor is a typed INVALID_CURSOR, never a silent restart. Never lifecycle-gated.

get/vaults/v1/{vault_id}/objects

Request

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

Query parameters

limitstring

Page size, 1–1000. Defaults to 1000.

cursorstring

Echo the previous page's next_cursor unchanged.

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.

Response

One page of the vault's stored objects

repo_idstring
has_moreboolean
next_cursorstring nullable
totalstring

The exact total count of stored artifacts across the whole vault (not just this page), as a decimal string (values may exceed 2^53). Always present and exact — every page materializes the full set before slicing, so it is never an estimate and never null.

Changes

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