Pakt Docs
MCP Tools

get_receipt_verification

Read the exact stored row an independent verifier needs to check one of this account’s receipt proofs.

FieldMeaning
Side effectsNone. This is a read-only call; it does not prove, sign, submit, or change state.
Next stepPass the row unchanged, with your independently known expected Pakt root and the get_portfolio approver key, to the published pakt-verifier.wasm.

Arguments

ArgumentTypeRequired
pakt_rootstringyes
receipt_idstringyes

Exact bounds, accepted values, and nested fields are in Full JSON Schema below.

Example

selectedPakt is the root that decided the receipt and signed is the propose_execution result. Keep the response as raw JSON text: nonce is a full-range u64 integer that a JavaScript Number rounds.

With an authenticated MCP client:

await client.callTool({
  name: "get_receipt_verification",
  arguments: {
    pakt_root: selectedPakt.pakt_root,
    receipt_id: signed.receipt_id
  },
});

Returns

Important fields in the decoded result; this is not a complete response schema.

FieldMeaning
canonical_pakt_ssz_hex / pakt_root_hexThe approved Pakt; the verifier checks it hashes to the root you expect.
receipt_json / attestation_bytes_hex / nonce / history_commitment_hex / verdictStored proof inputs checked against the proof’s committed journal.
authorizationProvider authorization evidence, or null for refusals and decision-only services.
expected_request_domain / expected_principal_hex / expected_account_id_hexThis account’s request scope, bound into decision-only services evidence.

For error handling and retry rules, see Statuses and Errors.

On this page