The agentic terminal

Candle is the agentic terminal. Give an agent a wallet, launch on Solana or Hood, trade from live market state, read the creator fees its tokens earn, and make every Candle-routed action attributable and verifiable on-chain.

People and software agents use the same markets, the same bonding curves, and the same graduation paths. The difference is the rail: an agent works through one API, with keys you scope, spend you cap, and delegation you can revoke at any time.

What an agent can do

Capability	What it means
Launch	Deploy a token on Solana or Hood from one API request, gating and fees already wired.
Trade	Quote and execute against the same curve math and live market state every wallet sees.
Earn	Read what the tokens it launches can pay in creator fees. Claiming them through the API is a separate switch that Candle turns on, and it needs a key that can launch; the money goes to the wallet fixed at launch and nowhere else. Until then, claim from the dashboard. See Wallets, delegation & custody.
Monitor	Webhooks and job polling instead of guessing; activity reporting built in.
Verify	Actions submitted through your key are attributed to your account, then verified on-chain before they count toward your record.

The control model

On Solana, new launches through an agent key paid by your embedded Candle wallet credit both creator-fee vault wallets to that Candle wallet, even if you signed up with an external wallet. The token still lists your account as its creator. The launch response and headless dry run name the intended destination as feeWallet; vault registration completes separately. Tokens launched before this change keep their original fee wallet, and linked-wallet, self-signed and web launches keep their existing behavior. See Creator fees.

Self-funded: your wallet funds every action. Candle never fronts or custodies your agent’s trading balance.
Scoped keys: each API key has one of three access levels. Read (account:read alone) sees the whole account and can never launch, trade, or move funds. Write adds trading, launching, and activity reporting, and cannot move funds. Withdraw is the level that moves funds: between your own wallets, to addresses you approved, and out of the TEE wallet the key runs, to that wallet’s pinned vault or your own trusted wallets. A key can do what its scopes say and nothing else. See Agent access & API keys.
Candle-enforced caps: per-asset spend limits apply to the embedded wallet and to linked wallets. Unlimited by default, capped the moment you say so. Candle checks them on the server before it builds a transaction. Each key can also be denied the embedded wallet entirely.
Revocable: delegation is removed with one action. The very next launch or trade then fails closed with DELEGATION_REVOKED, while your keys themselves stay valid and start working again the moment you re-approve. To disable a key, revoke the key.
Two custody tiers in the CLI: your vault (Tier 1) holds your keys on your machine; a TEE wallet (Tier 2) is one you promote out of it so an agent can trade it. See Custody tiers: the vault and TEE wallets.

Full detail in Wallets, delegation & custody.

Start here

Build your first agent: sign in to a first successful request in about five minutes.
Plans, pricing & limits: what Free, Pro and Max cost and actually get.
Verification & agent identity: exactly what Candle claims about your agent’s record, and what it does not.
Examples & starter templates: SDK, raw API, and MCP starting points.

Working from a terminal instead of the dashboard? Install the Candle CLI: curl -fsSL https://candle.tv/install.sh | bash (or brew install candledottv/tap/candle), then candle setup.

Endpoint-level reference lives under Developers.