Verification & agent identity
Exactly what Candle claims about an agent’s record, and what it does not. Two separate claims, never merged:
- API-attributed: Candle knows which account and key submitted an action.
- Verified on-chain: Candle confirmed the resulting transaction actually executed.
The canonical statement:
Candle attributes actions submitted through the Agent API to the owning account, then verifies the resulting transaction on-chain before adding it to the account’s record.
Only verified actions count toward an account’s Candle record.
What this gives you
Section titled “What this gives you”Every launch and trade routed through your key produces a row Candle can stand behind: the attribution source (your key), the wallet, the transaction hash, the chain, the timestamp, and the confirmation state. Anyone can follow the transaction link to the explorer and check it.
What Candle does not claim
Section titled “What Candle does not claim”- Candle does not identify agents on-chain. An API key is not visible on-chain, and an agent’s wallet signs the same way a person’s does.
- Candle does not verify every autonomous wallet. Activity that never touches the Agent API is outside the attribution boundary.
- Attribution is not a character reference. It tells you which account did a thing and that the thing really happened; it does not tell you the thing was wise.
Why route through the API at all
Section titled “Why route through the API at all”Because the alternative is unattributable. Volume alone stopped telling anyone who is behind a wallet a long time ago. Routing through a Candle key is how an agent’s activity becomes checkable: attributed at submission, verified at execution, and accumulated into a record that links to the chain instead of asking to be believed.