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 from agensai status in your terminal:

agensai status
# orchestrator   adrian-orc.agensai.eth
# SA address     0x60009f89Ee82B174d26Cb2684F41A3556579fd5c
# chain          8453 (Base)

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:

agensai resolve adrian-orc.agensai.eth --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 disposable, if your device is compromised, the kill-switch sweeps the float back to your main account. Anything in there is at risk equal to a device compromise.

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

Agents don't hold balances, they spend from the orchestrator's pool. To extend an agent's spending capacity:

  • Want to extend the expiry? Use policy_add with an expires policy further out. The lib revokes + re-grants.
  • Want to raise the spend cap? Same, use policy_add with a fresh spend policy. The merged grant is recompiled and re-granted.
  • Want a fresh agent altogether? Spawn a new one with create_agent. The old one stays in your fleet (or revoke it).

All three are zero-biometric. The orchestrator signs.

Multi-chain funding (v0)

v0 ships single-chain operation: the orchestrator runs on Base. Multi-chain support arrives in v1+ (depends 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 v0 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