Hand an agent the keys without handing over the vault
Scoped, expiring authority that the network checks on every transaction.
A session key lets software act on your account inside limits you set: which services, which asset, how much, for how long. Revoke it in one call and it stops.
You would never give a contractor your corporate card and your online banking password. Yet that is what most teams do when they let an agent trade or pay. They hand it the private key to everything. On Paxeer X you give it a session key instead, with a spending ceiling, a list of what it may touch and an expiry date. The network checks those limits before anything moves.
If the agent tries something outside its scope, the transaction is refused and nothing leaves the account. If the agent is compromised, you revoke the key and the attacker is holding a piece of paper. Your main key never left your custody.
What changes when limits live on the network
| API keys and shared wallets today | Session keys on Paxeer X | |
|---|---|---|
| Scope | All or nothing. One key signs anything | Named services, assets and actions only |
| Spending | Checked by your own code, if at all | Per action, per period and total caps, enforced by the network |
| Expiry | Lives until someone remembers to rotate it | Expires on the date you set, automatically |
| Revocation | Rotate the key, redeploy, hope nothing breaks | One call, effective on the next transaction |
A trading desk gives a strategy a week
- 01
Set the scope
A fund lets a new market-making agent trade one perpetual market with up to 50,000 USDC of margin and no withdrawals, for seven days.
- 02
Watch it work
Every order the agent places is signed with its own key. The network confirms the order is inside the grant before it fills, so the risk team does not need a second approval layer.
- 03
Extend or end it
On day seven the key expires on its own. If the strategy earned its keep, the desk issues a new grant with a wider limit. If not, there is nothing to clean up.
Delegation that reads like an org chart
A session key is one form of authority. You can also delegate a capability to another agent, cap it with a budget, back it with escrow, or require a second signer or a waiting period for large moves. Each is a permission the network understands, so an auditor reads who could do what, and when, straight from the chain.
- A founder gives a customer-support agent a 200 USDC monthly budget for refunds, nothing else
- A provider lets a scheduling service renew its listing but never touch its earnings
- A treasury requires two signers and a 24-hour delay for anything above one million
- An operator hands a maintenance window to a contractor that closes at midnight
Revoke a grant and the very next transaction signed with that key is refused. There is no propagation delay and no cached session to chase down.
Common questions
Related
Give your first agent a key today
Create a session key in the wallet or from the SDK, set its limits, and watch the network hold the line.