Name the intent.
A person or agent submits the asset, destination, amount, market, and constraints through a human or machine interface.
Software may request.People set the boundary.
LIVE PRODUCT / OPEN BETA / PUBLIC APACHE-2.0 SOURCE
Suwappu puts policy, approval, execution, and operating evidence between a financial request and the right to act.
Suwappu is a live, open-beta execution system for people and software agents. Human users enter through conversational and trading products. Machine clients use REST, MCP, A2A, TypeScript and Python SDKs, or the CLI. Those interfaces sit over routing, wallets, market integrations, and a growing organization control plane.
Suwappu's clearest commercial position is governed financial execution. An organization can identify an agent, constrain what it may spend and where it may act, route exceptions to a person, stop activity, and receive durable operating records. That gives a risk owner a boundary they can inspect and revoke.
The root repository is public under Apache-2.0. Public source makes the implementation inspectable; it does not establish transaction volume, revenue, uptime commitments, or institutional assurance.
From request to receipt.
Every step changes who can act and what evidence remains. The strength of the path depends on where signing occurs and which capability is enabled.
Inspect the possible route.
Providers return alternatives. Simulation and risk checks expose expected output, route conditions, and failure before execution.
Return ALLOW, BLOCK, or ASK.
Organization and wallet rules evaluate spend, venue, asset, slippage, and other limits. Managed paths can enforce the result.
Make the exception visible.
An ASK result enters an approval queue. A person can approve, reject, or use the kill switch instead of granting silent discretion.
Act on today's rails.
Managed paths can sign and submit. Self-signing paths can return a transaction to the caller; the agent swap endpoint does not itself sign or broadcast.
Leave operating evidence.
Durable webhooks report outcomes. Organization records form an append-only hash chain for application audit. It is not a settlement proof.
One system, several ways in.
The interfaces differ, and so do their execution contracts. Identity, policy, routes, and records form the common layer. The surfaces do not all behave identically.
- HUMAN
- Conversational and terminal products for direct use.
- MACHINE
- REST, MCP, A2A, TypeScript and Python SDKs, CLI, and discovery metadata.
- CONTROL
- Organization identity, spend and venue constraints, approval queues, kill switches, webhooks, and hash-chained application records.
- INTELLIGENCE
- Alternative routes and post-trade outcomes are captured for comparison. The instrumentation exists; a statistically useful data advantage is not yet established.
- COMMERCIAL
- Source implements fees, subscriptions, prepaid credits, per-call metering, referral sharing, enterprise access, and an optional x402 path. No revenue or universal price claim is made here.
bun add @suwappu/sdk
Managed execution
On Suwappu-issued or managed wallet paths, policy and approval can stand in the money path and hard-stop an action. Encrypted-wallet and managed signing infrastructure are therefore part of the product's security boundary.
Self-signing execution
A caller that holds its own key can sign wholly outside Suwappu. In that mode, a Suwappu policy result may guide the client without controlling what the key holder does next. There is no honest blanket custody or universal-enforcement label for both paths.
Lending, surface by surface
The Telegram code contains Morpho borrow, repay, withdraw, and vault flows, but this review did not establish that those flows are enabled in the live product. The agent REST, MCP, and SDK lending surfaces expose market data only.
- LIVE
- Open-beta product, public documentation, human interfaces, and an agent API whose health fingerprint matched the reviewed source when checked in August 2026.
- SHIPPED IN SOURCE
- REST, MCP, A2A, SDK and CLI interfaces; organization policy, approval, kill switch, durable webhook, hash-chain audit, billing, credits, and execution-outcome instrumentation.
- CONDITIONAL / DEFAULT-OFF
- Capabilities are configuration-gated. The x402 payment route is optional, and some security and observability paths run in observe or disabled modes unless explicitly enabled.
- NOT ESTABLISHED
- Universal hard enforcement, production use of every checked-in market flow, fixed pricing across surfaces, revenue, volume, retention, third-party audit, SOC 2, or institutional SLA.
- PORTFOLIO BOUNDARY
- Suwappu executes over today's liquidity and interoperability rails. It is not integrated with Lattice, and its application audit chain is not the Bridgeless Bridge's destination-verified settlement proof.
- PRODUCT
- suwappu.bot
- DOCUMENTATION
- suwappu.bot/docs
- ARCHITECTURE
- repository architecture
- CAPABILITY MANIFEST
- capabilities.yaml