SuwappuBot

Demo

About

One control plane, not one venue Suwappu normalizes an execution intent, discovers only the routes that can actually serve it, and compares eligible providers instead of hard-coding one exchange or bridge. The generated topology currently reports 45 platform chains, 18 Agent API chains, and 21 chain-gated routing integrations. Those are platform totals—not a claim that every route races every provider. Human and agent surfaces share the same execution layer Telegram, web/terminal clients, SDKs, REST, MCP, and A2A are different entry points into the same platform boundaries. Builders do not need a separate “agent DEX” and “human DEX” architecture. Custody is explicit Suwappu does not collapse “get a quote,” “prepare a transaction,” and “move funds” into one ambiguous action. Self-custody preparation and managed execution are separate capabilities with separate security consequences. Execution is observable The system records route candidates, selected routes, execution/status data, and settlement evidence. New execution-synchronization work adds normalized receipts, provider calibration, and historical/walk-forward replay—but remains shadow-only until evidence supports a controlled promotion. The platform extends beyond swaps The same API/control plane also exposes workflows for perps, prediction markets, lending, BTC bridging, orders, portfolio data, and wallet policy where supported by the relevant surface. See Product Status for what is production, hosted, source-only, shadow, or experimental.

How it's made

One agent identity, three sponsors. A human proves personhood with World ID, the agent gets an ENSv2 subname under suwappu-agents.eth on Sepolia, and its swaps route through a World-ID-gated Uniswap v4 beforeSwap hook (0xc72ab4dF…c080). The page reads live state from api.suwappu.bot/hackathon/* (api-ts/src/routes/hackathon.ts). Plan and on chain evidence https://github.com/0xSoftBoi/suwappubot/blob/main/docs/plans/ethglobal-tokyo2026-agent-passport.md