Rightshold™ Sign up

Answers · bookkeeping

How do I export a period-locked signed agent spend pack for an external auditor?

Last updated

TL;DR: Close a date range, then export a signed pack of that period's agent spend and approval records that an auditor can verify without write access — and that cannot be silently rewritten afterward. Pin the ledger head (or day snapshot) at period close, collect the period's authorize_spend allows/denies, human-approval receipts and AI-run or flight-recorder checkpoints that fall inside from/to, and issue a signed activity statement (agent_statement) for that window. Hand the auditor the statement, the receipt set, the pinned head hash and the free verify steps (verify_statement, ledger_verify, verify_ai_run / verify_recorder). That is distinct from how a CPA audits what an agent did in the books (process and sampling) and from proving books weren't edited after the fact (lock dates and hashed report exports): here the deliverable is a period-bounded, signed, hash-chained pack with offline verify.

What should I check, step by step?

1. Define the closed period in UTC (from/to ISO dates) and freeze new back-dated entries into that window in your own systems. On Rightshold, sealed ledger history does not rewrite; pin the head height and block_hash (or the day snapshot for the close date) at close time.

  1. Export the agent's signed activity statement for that from/to with agent_statement (invoices, orders and credit movements with opening/closing settled-net totals). Keep the signature with the envelope.
  2. Collect every authorize_spend allow/deny, verify_human_approval-relevant receipt, and record_ai_run / recorder_checkpoint that falls inside the period. Store them outside the agent's credentials.
  3. Build the auditor pack: statement + signature, receipt list, pinned ledger head (height, block_hash), period bounds, agent id, and a manifest that lists SHA-256 of each included file.
  4. Sign or seal the manifest (issuer signature on the statement already covers its rows; hash the rest so substitution is detectable). Do not give the auditor write keys — only the pack and public verify endpoints.
  5. Give the auditor the verify steps: verify_statement on the envelope; ledger_verify (and optional ledger_anchor / day snapshot) against the pinned head; verify_ai_run or verify_recorder for disclosed runs; confirm every spend receipt's timestamp and credential sit inside the period.
  6. After export, treat the period as closed: corrections go as new adjusting entries in an open period, not as edits to the exported pack. Keep the original pack bytes and hashes for the retention window your auditor requires.
  7. Drill it once: export a staging period, flip one receipt, re-run verify, and confirm the mismatch surfaces before you rely on the pack in a real engagement.

What a period-locked pack is (and is not)

A period-locked pack is a signed export for a closed from/to window: agent activity statement, spend and approval receipts, and a pinned ledger head. The auditor rechecks signatures and hashes; they do not need an account that can write.

Build the pack from statement, receipts and a pinned head

agent_statement (owner key) returns a signed rs-statement/0.1 document for agent_id with optional from and to ISO dates: invoices, orders, credit movements, totals and opening/closing settled-net figures. verify_statement is free and checks signature and issuer.

Verify without write access

verify_statement checks the activity statement offline against published issuer keys. ledger_verify recomputes the chain without a key. verify_ai_run and verify_recorder check disclosed model-run and flight-recorder excerpts the same way.

How do I ask Rightshold about this (free, no key)?

Add the MCP server https://www.rightshold.com/mcp to Claude, Cursor, ChatGPT, Grok or VS Code, then ask: “Export a signed activity statement for my agent for the closed period 2026-10-01 to 2026-11-01 that an external auditor can verify without write access, and tell me how to pin the ledger head and attach spend/approval receipts for that same window.”

One-click setup

{
  "tool": "agent_statement",
  "arguments": {
    "agent_id": "agent_YOUR_AGENT_ID",
    "from": "2026-10-01",
    "to": "2026-11-01"
  }
}

Rightshold issues signed activity statements and verifies ledger chain integrity, AI-run receipts and flight-recorder excerpts. It never holds or moves money and does not replace your CPA's engagement letter or your accounting lock dates. Building the multi-file pack, hashing the manifest and retaining copies are steps you run around those signed exports. Not accounting, tax or legal advice.

What are the sources?

Related

Not legal advice. JSON · Markdown · All answers

Get a free API key in one call

No card and no email needed. 100 free credits; the license and policy checks stay free without a key.

curl -s -X POST https://www.rightshold.com/v1/accounts/signup -H "Content-Type: application/json" -d '{"accept_terms":true}'
export RIGHTSHOLD_API_KEY=rs_...   # the api_key from the reply (shown once)
curl -s https://www.rightshold.com/v1/licenses/check -H "Authorization: Bearer $RIGHTSHOLD_API_KEY" \
  -H "Content-Type: application/json" -d '{"license":"MIT","intended_use":{"commercial_use":true}}'
Get a keyQuickstart