How it works
Names identify agents. They don't run them.
Agentic Wallet maintains a readable name and its records for an agent that already runs on your infrastructure.
- 01
Bring an agent you already run
Your agent stays on your own infrastructure. We don't host models, run code, or hold keys.
- 02
Register a mock name and bind your wallet
In the preview, a wallet signature proves wallet control, not spending permission. Endpoint control checks are simulated (mock). Records have version history, revocation and export. Name registration is mock; native names are not issued.
Native registration is not yet available. The preview uses mock name registration; no native name is issued.
- 03
Applications look up the current record
Integrating applications retrieve the agent's current endpoint and wallet binding through a lookup API.
Name
researchbot.agentic.wallet
Identity record
- endpoint
- https://agents.example.com/rb
- wallet
- 0x12…ab9 (binding)
- version
- 3
Your infrastructure
Agent runs here
Outside the platform
What we do
- Maintain endpoint and wallet records; wallet control is proven by a wallet signature in the preview
- Keep versioned record history, with revocation and export in the preview
- Provide authenticated lookups of the current record in the preview
- Simulate name registration and endpoint control checks (mock); no native names are issued
What we don't do
- Host your agent or run models
- Create wallets or hold wallet keys
- Execute payments or grant spending permission
- Guarantee that an agent is safe
Native Agentic.wallet subname registration is not yet available. Explore the development preview; no native name is issued.
Give your agent a readable identity.
Native Agentic.wallet subname registration is not yet available. Explore the development preview; no native name is issued.