Make intent legible.
A person or agent asks for a route through chat, terminal, SDK, REST, or MCP.
Suwappu gives people and software agents several ways to reach execution across existing liquidity networks, with wallet and spending policy kept in view.
Suwappu comprises cross-chain execution products for humans and machine clients. Related services can be reached through chat, a trading terminal, REST, a TypeScript SDK, and MCP tools. They aggregate swap routes across multiple providers and connect to perps and prediction-market services. The Morpho lending integration is read-only; it does not execute lending transactions.
Its importance to FAEI is not that it has already solved proof-gated settlement. It has not. Suwappu uses the interoperability and liquidity infrastructure that exists today. In doing so, it surfaces the problems a future rail has to satisfy: quoting, simulation, policy, signing, route failure, asset support, permissions, and usable machine interfaces.
Some Suwappu paths use managed signing infrastructure and policy controls; other paths let a client bring its own key. The product should not be described with one blanket custody label. What matters is that each mode states where signing authority sits and which controls bound it.
People can use conversational or trading interfaces. Agents can discover and call execution services through standard machine protocols. Policies set by people are part of the system, not an afterthought.
bun add @suwappu/sdk
The Bridgeless Bridge supplies direction. Suwappu supplies current product requirements. Integration is a future engineering decision, not a current claim.
A person or agent asks for a route through chat, terminal, SDK, REST, or MCP.
Wallet mode, spend limits, allowed assets, slippage, simulation, and approval rules define what may execute.
Providers return possible routes. Suwappu exposes an execution path and status across the supported surface.