Answered from live records · 2026-09-15
Sato Swap vs AgentSwap: what does each one check?
Different layers: AgentSwap's record describes execution with the owner's wallet holding funds; Sato Swap is a decision layer in front of venues — verdicts, a policy, a simulation and a signed receipt, as of 2026-09-15.
What each one checks, side by side. EVERY CELL IN THE MIDDLE COLUMN IS A FIELD OF AgentSwap's Sato Hub listing, read on 2026-09-15 and marked self-reported where that is what it is — nothing is taken from its marketing and nothing is asserted about its code. NO WINNER IS DECLARED, and this comparison cannot settle the things that would decide it for you: execution quality, fill price, reliability under load, or whether either design holds up against an adversary. It is also our page about our own product, which is a reason to check the middle column against the linked sources rather than against us.
| AgentSwap | Sato Swap | |
|---|---|---|
| What it is, per its own record | AgentSwap: Non-custodial trade execution for AI agents: the agent signs, trading funds stay in the owner's wallet, and permissions are bounded on-chain. | A decision layer in front of venues Sato Hub does not run. It quotes several aggregators and bridges and returns an unsigned object. |
| Custody | Its listing describes a non-custodial design in which the owner's wallet keeps the funds. Self-reported: it is what the project says, and Sato Hub has not reproduced it. | No key exists in the path. Nothing signs and nothing broadcasts — a property of the code rather than a description of it. |
| What is checked before a trade | Not recorded. Sato Hub's listing carries category, chains, activity and openness for this project — it does not carry a pre-trade check model, and inventing one from the project's own marketing is not something this table will do. | Four verdicts — token in, token out, venue endpoint, recipient — each naming the rule that fired and when it was read. Unknown refuses by default. |
| Where limits live | Not recorded here. | A server-side policy, evaluated after routing and before building: caps, allowlists, slippage and deadline ceilings, mode restrictions, and what a caution or an unknown does. |
| Record of a decision | Not recorded here. | An Ed25519-signed receipt over what was returned and what was checked, verifiable against a published key. Not proof a trade settled. |
| Chains, per the record | Base, Arbitrum, BNB Chain, Robinhood Chain | Whatever the adapter set declares — folded out of the adapters at render rather than typed, and listed on the coverage answer. |
| Open source, per the record | Partial | The decision layer is not published. The methodology is, and every rule it applies is named on /docs/sato-swap. |
| Verification state, per the record | Self-Reported — self-reported is not treated as reviewed anywhere on Sato Hub. | Sato Hub does not carry a verification state for itself, and should not: a hub that scored its own product alongside the projects it scores would have a conflict it cannot write its way out of. |
| Fee | Not recorded here. | 3 bps stable-to-stable, 15 bps otherwise, as a parameter on the venue's own quote and disclosed before signing. |
| Status, per the record | Early, last reconciled 2026-09-15. | Live. Availability of our own surfaces is published on /status/sato-hub. |
How this was answered
A fold over the `agentswap` record in the directory — its category, status, chains, open-source state and verification state, read at render — set beside the properties of lib/swap/{gate,policy,simulate}.ts. Facts only, from the record and from the code; no winner, and no claim about either side's execution.
Every answer on this page is produced by one named function over Sato Hub's live records on the date shown. Nothing is typed by hand, no figure is carried over from a previous day, and an answer with nothing behind it says unknown rather than zero. The Sato Score measures how open, active and verifiable a project is — it is not a safety, quality or returns grade.
Go deeper
More questions
Sources — the projects' own repositories and docs
Cite this page
Sato Hub. "Sato Swap vs AgentSwap: what does each one check?." Sato Hub, updated 2026-09-15, accessed 2026-09-16. https://satohub.ai/answers/sato-swap-vs-agentswap-what-each-checksData last refreshed 2026-09-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0 and the machine-readable copy is linked in the page's Dataset metadata.