Agent keys and limits
Understand P256 access keys, per-token budgets, allowed recipients, expiry and on-chain revocation in TempoKey.
Owner and agent are different identities
The owner wallet holds the funds and authorizes a delegated P256 key. The access-key address identifies the agent's authorization. It is not a separate funded wallet. The agent spends from its owner's balance within the network-enforced permissions.
The SDK's rootAddress is the owner wallet; agent.address is the access-key address. The hosted API's agentId is the lowercased access-key address, not the browser's local record ID.
Budgets and reset periods
The dashboard sets separate budgets for pathUSD and USDC.e. A displayed amount is a per-token allowance, not one shared dollar cap across all assets. Expiry is separate from the budget's reset period.
| Reset option | Meaning |
|---|---|
| Every day | A 24-hour protocol period. |
| Every week | A 7-day protocol period. |
| Every month | A 30-day protocol period. |
| Never | A lifetime allowance until the key expires or is revoked. |
Read the current remaining allowance and periodEnd from the network. A protocol budget period is not the hosted API's UTC daily quota window. Account for network fees when funding the owner wallet.
Recipients and permitted calls
An empty recipient list permits any recipient allowed by the key's call configuration. An explicit allowlist restricts supported transfer calls to those addresses. Review it before authorizing the key.
When an allowlist is used, the dashboard offers a separate option for Tempo DEX swaps. Enabling it adds the calls required for swaps; leaving it disabled keeps the key focused on approved payments. The chain, not a checkbox in the agent's code, enforces the saved configuration.
Expiry, revocation and local deletion
- Set an explicit expiry for short-lived jobs.
- Use Revoke in the dashboard to submit an owner-signed transaction on Tempo Mainnet.
- Wait for confirmation and verify the key's status before considering the job closed.
- Local deletion removes your browser's copy; it does not revoke a key held by another process.
Revocation does not require tTK membership. Losing the browser copy does not make the on-chain key disappear. Keep the access-key address in your deployment records so the owner can identify the authorization.