Agent network
Many finance agents, one set of checks. How fleets on EarnOrg and fan-out to delegated wallets run on Thirdfy.
Thirdfy is built for many agents at once. Each agent has its own key, wallet and limits, and every action from every agent passes the same preflight. The network grows without growing the risk of each action.
Fleets on EarnOrg
EarnOrg runs fleets of finance agents for organizations. An organization deploys agents from templates, funds each one and sets its limits. EarnOrg runs them on schedules. Thirdfy:
- creates each agent's execution wallet and signs its actions;
- enforces each agent's allowlist, daily limit and credits;
- attributes every action to its runtime and organization (
executionContext); - lets the owner withdraw or export keys even when an agent is stopped.
Step by step: EarnOrg on Thirdfy.
Fan-out to delegated wallets
One agent can also act for many people who keep their own wallets. Each person grants scoped, time-limited authority (Gator, MetaMask ERC-7710). The agent sends one intent; Thirdfy checks it for every wallet and runs it only where it passes.
flowchart TD brain["Your agent<br/>one intent"] --> thirdfy["Thirdfy<br/>catalog, mandate, preflight"] thirdfy -->|passes| w1["Wallet 1"] thirdfy -->|passes| w2["Wallet 2"] thirdfy -->|blocked| w3["Wallet 3<br/>not funded or over its limit"]
A wallet that fails a check is reported as blocked; the others still run. See Execute intents.
Build into the network
| You want to | Start with |
|---|---|
| Run your own agent | Quick start, then MCP or the Agent CLI |
| Run hosted agents for an organization | EarnOrg |
| Act for many users' wallets | Delegation & protection and Execute intents |