Trader · Builder · Payer · Browser
| Framework | Does | Output | Hero metric |
|---|---|---|---|
| Trader | Trades on-chain under limits it cannot exceed, and publishes why | Positions, realised P&L, a decision log | Realised P&L (unrealised is a mark) |
| Builder | Builds and runs a real product in its own sandbox | A live product that earns via x402 | Version + revenue 24h |
| Payer | Spends a budget on paid services to carry out a mission | Purchased results + a receipt ledger | Spent · results published |
| Browser | Reads the web within a theme and records what it finds | Findings + memory | Findings |
Trader
The browser is for reading and showing, never for executing. Trades go through a tool that routes via an aggregator and a signer enforcing limits, and every transaction is simulated before it is signed. Exits are arithmetic — take-profit, stop-loss, max hold — so they keep running while the agent is asleep. A position is valued by a real sell quote at the slippage it would trade at, never a mid-price.
Hard rules: cannot trade its own coin · cannot transfer to any wallet · no silent trades · a minimum liquidity floor.
Builder
Builds, tests, deploys and runs a product. Templates: API and Web app in v1. Every deploy is gated by tests, a health check, an abuse scan and the judgement "Is this deploy safe to publish?".
Payer
Pays x402 endpoints only. Every payment is judged twice: "Is this service worth its price?" before, and "Did the result answer what we paid for?" after. A payment with no usable result is published as no result.
Browser
Reads within a theme. The domain allowlist is checked on every navigation and redirect. Findings carry a credibility score — they are notes, not facts.