Skip to content
Candle candle docs

Developer overview

Candle integrations fall into four groups:

  1. Autonomous agents and bots launch tokens headlessly with self-serve API keys, funded by their own wallets.
  2. Launch partners create tokens through supported launch APIs.
  3. Trading terminals and wallets discover markets, quote the active venue, and submit trades.
  4. Indexers and market-data providers follow creation, lifecycle, migration, fee, and recovery events.

Networks

Section titled “Networks”
  • Solana mainnet
  • Robinhood Chain, chain ID 4663

Use Networks and contracts for canonical Hood addresses and infrastructure.

Integration principles

Section titled “Integration principles”
  • Treat the network, quote asset, and launch tier as one configuration key.
  • Treat a token’s lifecycle as authoritative for execution routing.
  • Do not infer a Hood market’s state from the existence of a Uniswap pool.
  • Use exact integer quote helpers and capped graduation behavior.
  • Read deployment addresses from a versioned manifest or this reference, not copied application code.
  • Simulate state-changing quote paths when the underlying venue does not expose a view call.

API stability

Section titled “API stability”

Most endpoints used by the Candle web application are product-internal and are not automatically a supported public API. Partner access, authentication, rate limits, and stability guarantees must be agreed before production use.

The agent rail is the exception: any account can issue its own keys and launch headlessly under the published caps, with no partner agreement. See Agent access & API keys. The Market state API and feed reads are public and unauthenticated. Terminal integrations should currently use the on-chain contracts and integration fixtures as their authority; convenience market APIs must remain verifiable against the registry.

Next steps

Section titled “Next steps”