Skip to content

Reference ​

Every feature of agent-custody, how to use it, and the exact request and response of every function and endpoint. The narrative guides on agent-custody.dev explain why; these pages say what goes in and what comes out.

Reference pages ​

What each component is for, and when you need it, is on Components. Each one has a reference page:

componentpackagereference
Gateway@agent-custody/receiptsgateway
Egress witness@agent-custody/receiptsegress
ACS Guardian@agent-custody/receiptsacs
Door@agent-custody/receiptsdoor
SDK@agent-custody/receiptsTypeScript SDK
Sidecar@agent-custody/receiptssidecar
Pythonagent-custody on PyPIPython
Claude Code@agent-custody/receiptsClaude Code
Log@agent-custody/receiptslog API
Verifier@agent-custody/receiptsverify and audit
Hosted loglog.agent-custody.devhosted
Memory@agent-custody/statememory
Explain, review, pack@agent-custody/stateexplain and packs
Command lineboth packagesCLI

Install ​

bash
npm install @agent-custody/receipts @agent-custody/state
pip install agent-custody

The packages run on Node 22 or later and Python 3.10 or later. Nothing phones home; the only network calls are the ones you configure.

Conventions on these pages ​

  • Request and Response blocks are JSON exactly as sent and received. Fields marked optional may be omitted; fields marked env name an environment variable and never carry the secret itself.
  • Every signed object is a DSSE envelope: { "payloadType", "payload" (base64), "signatures": [{ "keyid", "sig" }] }. The keyid is the SHA-256 of the signer's public key in SPKI DER, so a verifier matches keys without being told which is which.
  • provenance on a receipt field is one of attested (signed by a key other than the issuer's), observed (the issuer saw it itself), or claimed (the agent said so). The proof table says what each is worth.
  • Money is integer minor units everywhere. Timestamps are ISO 8601, UTC.