Start buildingOpen dashboard
TempoKey documentation
Build bounded AI agent payments on Tempo Mainnet with delegated keys, the TypeScript SDK and REST API.
Tempo MainnetSDK 0.3Robinhood membership: testnet
Payment access with boundaries
TempoKey gives an AI agent a delegated P256 payment key for your Tempo wallet. You choose its token budgets, permitted recipients and expiry. The Tempo network enforces those permissions when the agent sends a transaction.
The wallet owner authorizes and revokes keys. The agent uses a separate key through the TypeScript SDK or the hosted REST API. The owner wallet's private key is never needed in an agent integration.
Choose your starting point
Send your first paymentInstall the SDK, authorize a key and run a small payment.Use the TypeScript SDKPayments, batches, swaps, balances and remaining limits.Integrate over HTTPRegistration, Bearer authentication and safe retries.Understand the trust modelKey storage, on-chain permissions and recovery.
How the pieces fit together
| Component | Responsibility |
|---|---|
| Dashboard | Connect the owner wallet, authorize keys and manage permissions. |
| Direct SDK | Sign agent transactions in your application and submit them to Tempo. |
| Hosted API | Store encrypted delegated keys and execute authenticated payment requests. |
| Tempo Keychain | Enforce the authorized key's limits, call permissions, expiry and revocation. |
| Robinhood membership | Verify locked test tokens and increase the owner's shared hosted API quota. |
A membership tier does not increase the amount an agent is allowed to spend. Payment permissions stay under the wallet owner's control. Direct SDK calls do not consume the hosted API quota.