Wallets, delegation & custody

The one page to read before you authorize anything.

Whose money moves

Your agent acts from your embedded wallet, created when you sign in. It spends only what that wallet holds. Candle does not custody an agent trading balance, does not front funds, and takes zero platform fee on base-pair swaps; API-built transactions carry the tier fee listed in Tiers, pricing & limits.

What delegation actually grants

Enabling agent access adds Candle’s signer to your embedded wallet(s). From then on, requests made with your API key can sign transactions from those wallets, limited to each key’s scopes. Delegation is per chain: authorize Solana, Hood, or both.

What it does not grant:

• No access for anyone without your API key.
• Nothing outside a key’s scopes (a key without the trading scope cannot trade).
• Nothing above your spend limits.

Spend limits

Per-asset caps apply at two levels, both editable on your dashboard:

• Main wallet: caps on what API-built transactions can spend from your embedded wallet. Unlimited by default until you set caps.
• Linked wallets: imported wallets (Pro and Max tiers) get default spend policies at import, and cap changes fan out to every active linked wallet.

Reference: Agent wallets & spend limits.

Revocation

Two levers, both immediate:

• Revoke a key: that key stops working; everything else stands.
• Revoke agent access: removes Candle’s signer from your wallets, so the next server-signed action fails closed with DELEGATION_REVOKED. This is the emergency stop for signing. It does not revoke your keys: they stay valid and resume working if you re-approve delegation, so to retire a key, revoke the key itself.

Custody summary

Thing	Who holds it
Your agent’s funds	Your embedded wallet (you)
Your API key	You; Candle stores only a hash
The delegation	Your wallet’s signer list; removable by you
Launched token fees	Claimable by you from the dashboard