Skip to content

Funding the orchestrator

Your orchestrator is a smart account. To spawn agents and let them act, fund it.

How

Send tokens to the orchestrator address. Get the address from the dashboard, or ask the chat:

What's my orchestrator address on Base?

The dashboard's Top up panel shows a QR + address for each supported chain. The address is a normal smart-account address. send ETH or USDC from any wallet (Coinbase, Rainbow, Metamask, any other JAW account, doesn't matter).

You can also resolve the orchestrator's ENS from the chat via the resolve MCP tool:

Resolve adrian-orc.agensai.eth on chain 8453.

0x60009f89Ee82B174d26Cb2684F41A3556579fd5c

ENS resolution returns the chain-appropriate address, so the same name resolves correctly on Base, Optimism, Ethereum, etc.

How much

The orchestrator is the working float for your agents. Typical sizing:

Use caseSuggested float
One DCA bot, $50/week$200
3 trading agents, $50/day each$500
Subscription payer, $9.99/month each, 5 services$100
Single research agent, read-only$20 (gas only)

Don't park your bank in the orchestrator. The orchestrator is the working float, recoverable but exposed. Your main account is auto-installed as a co-owner the first time you spawn an agent, so you can drain it back from any device. Anything sitting in the orchestrator during a device compromise is at risk until you retire from elsewhere. Keep the float bounded.

The boundary is intentional: keep the float bounded, and you keep your damage bounded.

Gas

JAW supports both native ETH gas and ERC-20 gas natively, with no AGENSAI infrastructure or paymaster.

  • ETH gas: default. If your orchestrator holds ETH, it pays gas in ETH.
  • USDC (or other ERC-20) gas: built-in to JAW. User selects the token in the wallet dialog at signing time.

Cite: gas-sponsoring.md lines 7-11: "Built-in, user selects token in dialog."

AGENSAI ships no paymaster. No sponsorship, no fee collection, no third-party paymaster relationship. You pay your own gas in whatever token you fund with. This is a non-negotiable architectural commitment.

If you want full gas sponsorship for your own product built on AGENSAI primitives, the lib accepts an optional user-supplied paymaster URL. Default is "user pays in whatever they hold."

Topping up an agent's window

In the per-agent-SA model, each agent has its own SA seeded at create time. The orchestrator can top it up at any time:

  • Need more working capital? Use fund_agent to push USDC or ETH from the orchestrator to the agent. No permission constraint — orch owner key signs directly.
  • Want to extend the expiry or change the spend cap? Permissions are immutable per ERC-7715. drain_agent to sweep balance back, revoke the permission, then create_agent with the new bundle.
  • Want a fresh agent altogether? Spawn a new one with create_agent. The old one stays in your fleet (or revoke it).

All four are zero-biometric. The orchestrator signs as co-owner of the agent SA.

Multi-chain funding

AGENSAI ships single-chain operation today: the orchestrator runs on Base. Multi-chain support arrives in a later release, dependent on JAW shipping cross-chain primitives.

Your orchestrator's smart-account address is the same on every EVM chain thanks to CREATE2 determinism. You can fund the address on Optimism or Arbitrum, but the daemon won't operate there yet. Don't park float on a chain the daemon isn't running on. You'll need to bridge later.

Further reading