Sato Hub
Token swaps

Sato Swap

An agent-native tool to swap assets onchain.

  1. 1

    Send a swap request

  2. 2

    Four checks run

  3. 3

    Read the result

  4. 4

    You sign it

Example run·4 checks·unsigned transaction only if all four allow·nothing is signed here

Swap request

intent parses · every required field present

no wallet connect
Examples
How it decides

01Four targets are read — input token, output token, venue, recipient. Each reading names its rule.

02A policy decides what those readings permit. Unknown refuses unless a stored policy says otherwise in writing.

03Venues that quote the pair are ranked within their own lane; the chosen one carries its own fee sentence.

04In build-tx the transaction is simulated first. If it reverts, you get the revert instead of the object.

the method in full →

Four checks, every quote

Example
  1. 01

    Token in

    0x833589…a02913

    A recognised stablecoin on Base, matched by address.
    rule TOK0
    go
  2. 02

    Token out

    0x420000…000006

    The wrapped native asset on Base, matched by address.
    rule TOK0
    go
  3. 03

    Venue

    example-venue

    A venue needs a current listing and a record of answering checks before it can fill.
    rule R5
    go
  4. 04

    Recipient

    0x742d35…38f44e

    The recipient is the signer, so the output comes back to you.
    rule RCPT1
    go

Unknown refuses by default. We hold no record for that target, and no record is not the same as a clear reading — a policy has to say so in writing before a swap is built on it.

Transaction

Example
Simulationok
Policydefault
Unsigned objectreturned
Signingnever

Example run. Send a swap request to see your own result.

What Sato checks

  • Token in

    Which contract you pay with

  • Token out

    Which contract you receive

  • Venue

    Who fills the trade, and whether it answers

  • Recipient

    Where the output lands

  • Signing

    Unsigned: you sign

  • Keys

    Sato never holds keys

  • Fee

    Shown before you sign

    Sato Route swaps cost 3 bps stable-to-stable, 15 bps between majors (a chain's native coin such as ETH or SOL, its wrapped form, or a stablecoin), 75 bps with any other token and 25 bps cross-chain (75 bps when either side is any other token), taken as a parameter on the aggregator's own quote inside the transaction you sign

  • Default

    Unknown refuses by default

Fee scheduleShowHide

Sato Route swaps cost 3 bps stable-to-stable, 15 bps between majors (a chain's native coin such as ETH or SOL, its wrapped form, or a stablecoin), 75 bps with any other token and 25 bps cross-chain (75 bps when either side is any other token), taken as a parameter on the aggregator's own quote inside the transaction you sign; a failed, reverted or unsigned trade pays nothing. A token launch carries a disclosed share of the creator's LP fee, stated as fee.bps on every launch response, including when it is 0. Sato OS charges 3 / 15 bps on its own spot swap rail and a 3 bps perp builder fee, with no cross-chain tier. Some venues keep a share or pay later, and every quote says which.

When Sato says no

It will not fill a trade into something it cannot identify.

Two modes

recommend · build-tx

Recommend names the venue. Build-tx adds the unsigned transaction.

Default policy

no record → no fill

A stored policy can widen or tighten this, per caller.

Modes and policy in fullShowHide

recommend never returns calldata, whatever the gate said. build-tx adds the unsigned object, and only when the policy allowed every verdict and the transaction did not revert in simulation.

A stored policy widens or tightens the default: allow caution, set per-token caps, require a Passport on the recipient. Without one, every caller gets the strict default above.

Sato Swap is not investment advice, not a broker, and not a guarantee of execution, price or outcome. Routing to a venue is not an endorsement of it. Related: Sato Route · Preflight · Trust rules · OpenAPI