Sundial docs
Getting started
Install @sundial/sdk and create a Sundial instance with your agent wallet address and a dedicated logging key. Keep the logging key separate from the key that moves funds, so a leak of one does not expose the other.
Wrap each action in log.run. The SDK signs an entry with the action type, amounts, a timestamp and the resulting transaction signature. Wallets such as Phantom, Solflare or Backpack can be declared as the human co-signer.
How autonomy levels work
Levels run from 0 to 3 and are recomputed from the last 30 days of transactions. Sundial looks for a declared co-signer key among the signers of each transaction. More co-signed transactions mean a lower level.
A declared co-signer shows that a second key signed. It does not show that a person reviewed the action, and the agent page says so.
What the log cannot prove
The log only covers actions that went through the SDK. An agent can still sign transactions outside it, which is why the verifier lists every unmatched transaction for the wallet.
Anchoring proves an entry existed at a given time and has not been edited since. It does not prove the entry is complete, or that the agent's stated reasons are accurate.