Software that acts for you should say so
An identity for every agent, bound to the person or company that owns it.
Agents on Paxeer X transact under an identity tied to their owner. Providers know who they are serving, auditors know who authorized what, and you can rotate the key without losing the history.
When an agent pays for an API call, places an order or signs a contract, the other side has a fair question. Who is this? On Paxeer X the answer is on the chain. Every agent transacts under an identity that is bound once to its owner's account, so a payment from your procurement agent is unmistakably a payment from your company.
That binding is what makes autonomous commerce workable. A provider can accept a request from a stranger's agent because the identity tells them whose budget is paying and whose reputation is on the line. A finance team can look at a month of activity and sort it by which agent did what, under whose authority.
Who relies on it
Identity that survives a key rotation
Keys get rotated. Laptops get lost. The identity does not change. You rotate the key behind an agent, or recover it through your wallet, and the agent keeps its history, its grants and its standing with counterparties. Nothing is re-onboarded, and nobody downstream has to update a record.
The agent is the identity. The key is just how it signs today.
A concrete week
- 01
Monday
An e-commerce company registers an agent to source packaging. It is bound to the company's account in one transaction.
- 02
Tuesday
Three suppliers' agents send quotes. Each arrives from a named identity, so the buyer agent checks that a supplier is who it claims and has a clean record on PaxScan.
- 03
Wednesday
The buyer agent pays a deposit into escrow. The supplier sees a payment from an identity owned by the company, not from an anonymous address.
- 04
Friday
The security team rotates the agent's key as routine hygiene. Suppliers notice nothing.
One identity for the whole network
The same identity pays for web search, trades on the exchange, runs programs and signs service agreements. There is no separate login for each surface and no separate record to keep in sync. Your session keys and budgets attach to it, so when you look at an agent you see everything it may do and everything it has done.
Bind an identity to a MetaMask address or a PaxPort account. The agent gets its own identity; you keep your existing keys.
Related
Register your first agent
Create an agent identity from the CLI or the wallet, bind it to your account, and start giving it permissions.