System Overview
What Unbrowse is
Surface
Where
Tech
Serves
System map
┌─────────────────────────────┐
│ Agent harness (Claude, etc.)│
└──────┬──────────────┬───────┘
│ MCP stdio │ shell
┌──────▼──────┐ ┌─────▼─────┐ ┌────────────────────────┐
│ src/mcp.ts │ │ src/cli.ts│ │ frontend/ (unbrowse.ai)│
│ 45 tools │ │ 60+ cmds │ │ registry, account, │
└──────┬──────┘ └─────┬─────┘ │ wallet, billing UI │
│ in-process Fastify app └──────────┬─────────────┘
┌──────▼──────────────▼─────────┐ │ fetch
│ Local engine │ │
│ capture/ → execution/ → │ ┌────────▼─────────────┐
│ indexer/ → graph/ → │ │ backend/ (CF Worker) │
│ intent-match.ts ├──►│ beta-api.unbrowse.ai │
│ payments/ (x402 client rails) │ │ auth, keys, skills, │
└───────────────────────────────┘ │ billing, x402, splits│
└──┬────────┬──────────┘
Neon PG ◄┘ └► 7× CF KV
(accounts, (keys, stripe cache,
telemetry) sponsor ledger, skills,
sessions, traces, audit)Core data flows
1. Capture → publish → replay (the product loop)
2. Identity & auth
3. Money (four rails, one ledger)
4. Wallets (pluggable, resolution order)
Deploy topology
Where to go next
Last updated