Tamper-evident usage ledgers for AI agents — every credit spent and every action taken, signed, replayable, and verifiable by your customers with open-source tools. No "trust our dashboard."
Provision an agent, grant credits, and stream usage — every grant, burn, and action is an ed25519-signed event in a hash-chained ledger. The kernel rejects overspend; nothing is a database row you could quietly edit.
One call produces a signed bundle: the full event history, public keys, action log, and manifest hashes. GET /agents/bot-1/export.zip
Your customer replays the bundle with the open-source satroot package — offline. Any edited byte, in any file, fails loudly.
Autonomous agents spend real money and take real actions. Today, the record of what they did lives in a provider's database — your customers take it on faith, and so do you.
satledger inverts that. State is computed by replaying signed events under public, frozen rules. The export verifies with pip install satroot and nothing else — not even trust in us. Auditors, enterprise customers, and insurers get evidence, not assurances.
# your customer, on their machine:
$ pip install "satroot[crypto,validation]"
$ python -c "import satroot1; \
satroot1.verify_signed_ledger_bundle('export/bundle')"
✓ 214 records · ed25519 · public-only material
✓ every file hash, every signature, every rule
✓ state: sha256:e1a2c685…49fb4e3per agent / month
ledger + on-chain commitments
anchored + dedicated namespace root
No tokens, no coins, no yields. Anchoring commits a hash of your ledger to a public chain; it does not put your data on-chain, and it creates no financial instrument.
The protocol layer is open (Apache-2.0) and stays open — satledger sells the hosted, anchored, multi-tenant operation of it, not access to the standard.