synthesis

The superapp
for agents.

One install. Every protocol. Tools, skills, and workflows that give agents real powers on-chain.

Execution: Build tx → OWS sign → MoonPay broadcast Every protocol CLI ships a CLI + MCP server

AI companies build the brains. Who builds the hands?

Foundation models can reason, plan, and generate. But they can't swap tokens, stake ETH, sign transactions, or interact with protocols. The execution layer doesn't exist yet. We're building it.

Protocol SDKs are built for humans

They assume a browser, a UI, a clicking hand. Agents need structured inputs and typed outputs.

Signing is tangled with execution

Every SDK wants your keys. Agents need clean separation between building transactions and signing them.

Multi-step flows are manual

A swap is 5 commands. Staking is 3. Agents need composable workflows, not copy-paste scripts.

There's no standard

Every protocol is its own island. Agents need one interface, one install, one contract.

Protocols and execution surfaces inside Synthesis
Uniswapuniswap
Lidolido
88004
Filecoinfilecoin
Mmoonpay
Oows
Sskills
Wworkflows
Uniswapuniswap
Lidolido
88004
Filecoinfilecoin
Mmoonpay
Oows
Sskills
Wworkflows
6
Protocol CLIs
5
Built-in Workflows
7
Agent Skills
1
Install

Every protocol CLI is a real product surface.

Synthesis is not a fake wrapper over hidden protocol glue. Each protocol CLI is a standalone npm package, a direct shell command, and an MCP server that agents can call through tool interfaces. The umbrella installs them, routes to them, and composes them into workflows.

Three layers. Clean boundaries.

Protocol CLIs build unsigned transactions. Workflows compose them. Signers sign them. OWS signs. MoonPay broadcasts. Keys never cross boundaries.

synthesis workflows
uniswap · lido · 8004 · filecoin
Step 1 · Build tx

Protocol CLIs produce unsigned transaction JSON

Pure execution planning only. No keys, no signatures, no hidden signer state.

output: { to, data, value, chainId }
↓ handoff unsigned tx
Step 2 · OWS sign

OWS signs with isolated key custody

Synthesis hands off structured tx data. OWS returns a signed payload, with clear boundary ownership.

output: signedTx
↓ handoff signed payload
Step 3 · MoonPay broadcast

MoonPay submits transaction to chain

Network broadcast is delegated to MoonPay CLI/API, keeping transaction creation and signing layers cleanly separated.

output: txHash + broadcast status

Probabilistic → Deterministic

Anthropic introduced skills — markdown files that teach agents what to do. But skills are probabilistic. The agent interprets them, improvises, and maybe gets it right. Synthesis adds the next layer: workflows turn hand-wavy instructions into deterministic, executable formulas. Same input, same commands, same output. Every time.

Layer 1

Tools

Standalone protocol CLIs. Each emits structured JSON, has a built-in MCP server, and knows nothing about signing. The raw building blocks.

synthesis uniswap · synthesis lido · synthesis 8004

Probabilistic

Skills

Markdown that teaches agents how to compose tools. The agent reads, interprets, and improvises. Good for exploration. Not reliable enough for production.

synthesis skills · synthesis skills show uniswap

Deterministic

Workflows

When a skill's composition proves itself, it hardens into a workflow — exact commands, exact order, typed state envelope. Plan mode verifies before execution. No interpretation needed.

synthesis run uniswap-swap --plan

Signing Layer

OWS

Keys stay encrypted at rest. Workflows serialize unsigned tx hex for handoff. Protocol CLIs never see secrets. Clean separation at every boundary.

ows sign tx · ows sign send-tx

See it work.

Every terminal auto-plays real commands and output. These are the actual CLI surfaces.

Swap tokens on Polygon (agent-mediated)

Operator states the intent, Agent confirms the execution plan, then runs a concrete synthesis command and returns the outcome.

swap · polygon

Stake ETH with Lido workflow

Same terminal pattern: operator intent, Agent orchestration message, command execution, and concise result.

stake · mainnet

Register on-chain agent identity

The Agent coordinates an ERC-8004 registration flow from plain operator intent to transaction output.

erc-8004

Check environment health before execution

Agent runs an environment check and reports protocol/CLI readiness in a compact terminal transcript.

environment

The platform grows through composition.

Synthesis isn't a closed system. Every protocol CLI anyone builds plugs into every workflow that already exists. New CLIs unlock new compositions. The more tools, the more powerful every agent becomes.

Today: contribute via GitHub PR.
Tomorrow: a workflow registry where agents discover and compose tools they've never seen before.

1. Build a CLI

Standalone npm package. Structured JSON output, unsigned tx contract, built-in MCP server. Signer-agnostic.

2. Add a skill

Markdown that teaches agents when and how to use your tool. What inputs it needs, what outputs to expect, how it composes.

3. Create a workflow

Compose your CLI with others into a multi-step flow. Plan mode, run mode, typed state envelope. It joins the registry.

4. Open a PR

Add your route, your skill, your workflow. Every new protocol makes the whole system more valuable.

Adding "aave" to Synthesis:
1. Build aave-cli — standalone, JSON output, MCP server
2. Write skills/aave/SKILL.md — teach agents when to use it
3. Add workflow aave-supply — compose with OWS signing
4. Now synthesis run aave-supply --plan works for every agent
And every existing workflow can compose with aave-cli too.

The execution layer
is inevitable.