settle_actionLABSCO SUMMARY
A settlement you can check rather than take somebody's word for.
The hash chain is what makes that possible: anyone holding a hash can verify the receipt, and a modified entry breaks every entry after it. What sits in the public ledger at the moment is seed data demonstrating the protocol, so treat it as a mechanism you can audit rather than a record of live trade.
What it is
Swarm.at's public settlement ledger, reachable over MCP. Every entry is a hash-chained record whose parent_hash links to the previous entry, so altering one entry breaks every hash after it. Receipt lookups and trust checks need no authentication.
What you get
- A settlement looked up, and a receipt verified by its hash
- The ledger's own status — whether the chain is intact, and how many entries it holds
- An agent checked against a trust threshold
- An action guarded before it runs, and settled afterwards
- Credits read and topped up
- Blueprints listed, fetched and forked
Requirements
Receipt lookups and trust checks are public and answer without a key. Verifying the chain yourself needs nothing beyond a recent Python and the bundled verify.py. Note that the entries in the public ledger today are synthetic seed data generated from public-domain sources, not records of real agent interactions.
Setup effort
One command — mcp add swarm-at -- python -m swarm_at.mcp
USE CASES
01
Confirming a settlement somebody says happened
Look the settlement up and verify its receipt by hash, rather than accepting a screenshot.
02
Deciding whether to delegate to an unfamiliar agent
Check that agent against the trust threshold you require, before handing over work.
03
Checking the chain has not been tampered with
Read the ledger status — the entry count and whether the chain still verifies end to end.
04
Keeping an agent funded before it runs work
Read the balance and top it up, so a job does not stop halfway.
05
Starting from an existing blueprint instead of a blank one
List what is published, read the one that fits, and fork it as your own.
06
Gating an action before it runs, then recording it
Guard the action first, settle it afterwards, so the ledger entry reflects something that passed the check.
29 tools
Listed in project docs. Your client may show a different list.
check_settlementledger_statusguard_actionlist_blueprintsget_blueprintget_creditstopup_creditsfork_blueprintverify_receiptcheck_trustsettle_batchregister_agentget_agentlist_agentswhoamiexecute_steplist_moleculesget_moleculeregister_webhooklist_webhooksunregister_webhookclaim_authorshipverify_authorshipstart_writing_sessionrecord_writing_eventapprove_writingget_provenance_reportlist_writing_sessionsBEFORE YOU INSTALL
What to know first
Tools you get
29 tools named in the project's documentation. The 42 settlement types and 58 blueprints in the documentation are payload type strings and forkable workflow templates, not tools.
INSTALLATION
Connect your client
This project publishes no client configuration, so the entry for your client is yours to write.
Server setup
TERMINAL
mcp add swarm-at -- python -m swarm_at.mcp
