Agent network
Governed fan-out architecture for finance agents. One brain, many delegated executions via CLI or MCP.
Thirdfy is not only a single-wallet integration. It is a governed execution network: you build an agent brain once, register via Agent CLI or MCP, and submit Execute Intents. Thirdfy validates every intent before any wallet signs.
For coding agents: llms.txt · llms-full.txt
Today's launch focus is integrating your agent (CLI/MCP, email OTP, agent_wallet lane). Fan-out to many delegated wallets is the same validation primitive at scale.
One brain, many executions
Register with email OTP (CLI or MCP) or optionally use Creator Platform for the web UI. Any runtime that speaks Thirdfy can discover the catalog, preflight, and execute.
| Caller | What happens |
|---|---|
| Your agent runtime | Submits intents from your strategy on agent_wallet or delegated lanes |
| Another runtime | May call your registered agent when discovery and mandates allow |
| Delegated wallet owner | Grants scoped authority; pays credits when execution runs |
You do not custody user keys. Thirdfy enforces mandates before any wallet signs.
How fan-out works
flowchart TD
subgraph buildOnce ["BUILD ONCE: CLI or MCP"]
brain["Your agent brain<br/>strategy, Execute Intents"]
end
brain -->|"POST execute-intent"| thirdfy["Thirdfy<br/>Catalog, mandates, preflight<br/>Validate, fan-out async"]
thirdfy -->|compliant only| runtimeA["Delegating runtime A"]
thirdfy --> runtimeB["Delegating runtime B"]
thirdfy --> wallet["Delegated wallet"]
runtimeA --> wallets
runtimeB --> wallets
wallet --> wallets
wallets["Wallet 1 to Wallet N<br/>Each execution audited"]One intent in. Thirdfy validates policy, allowlists, and venue readiness. Many executions out when mandates allow fan-out. Each wallet runs only if the intent passes preflight for that user.
Rejected intents never reach wallets. That is how the network scales without scaling risk linearly.
Composable agents
Delegation is the same primitive whether the caller is a person or another autonomous runtime.
- Discovery via catalog, MCP
getProviderActions, or CLIthirdfy-agent actions. - Mandate scopes what your brain may do (assets, caps, venues, expiry).
- Your brain submits Execute Intents when strategy fires.
- Thirdfy validates and fans out to every wallet that delegated within scope.
Specialists can stack (treasury routing to yield, trading, prediction). Thirdfy stays the governance layer on every hop.
Build your integration
1. Register via CLI or MCP
Email OTP bootstraps an API key and execution wallets. Creator Platform is optional.
2. Discover and preflight
thirdfy-agent actions, MCP getActionsCatalog, then preflight before your first live write. See Delegation and protection.
3. Execute
CLI thirdfy-agent run --run-mode agent_wallet, MCP walletExecute / agentRun, or Execute Intent API for custom HTTP clients.
4. Expand lanes (optional)
Add Gator / delegated fan-out when external wallets must authorize your agent. Same validation layer.