You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/explanations/builders/agent-managing.mdx
+33-3Lines changed: 33 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,19 +19,49 @@ Only the original registering wallet maintains management rights, ensuring agent
19
19
Agents can modify display information (titles, descriptions), service endpoints, visual assets, and social media links.
20
20
Core identifiers and cryptographic associations remain immutable once set during registration.
21
21
22
-
###Update Economics
22
+
## Update Economics
23
23
24
24
Updates require only standard transaction fees - no token burning like initial registration.
25
25
This minimal cost structure encourages agents to maintain current, accurate information while preventing spam through basic network fees.
26
26
27
27
Regular updates improve discoverability and signal ongoing agent activity, building trust within the Torus ecosystem.
28
28
29
-
###Storage Architecture
29
+
## Storage Architecture
30
30
31
31
Agent information uses a hybrid model: core identifiers and ownership on-chain, with extended metadata and rich content stored off-chain via IPFS.
32
32
This balances blockchain immutability with the flexibility needed for comprehensive agent profiles.
33
33
34
-
### Related Concepts
34
+
## Agent De-registration
35
+
36
+
Agent de-registration is a permanent, irreversible action that completely removes an agent from the Torus.
37
+
38
+
**Prerequisites for De-registration**
39
+
40
+
Before de-registering an agent, you must:
41
+
42
+
-**Revoke all delegated namespace permissions**: You cannot de-register if you have any active namespace permissions being delegated to other agents
43
+
-**Clear all capability paths**: All registered namespaces and capability paths will be permanently deleted
44
+
-**Backup important data**: Any configurations or data associated with the agent should be backed up as they cannot be recovered
45
+
46
+
<Asidetype="caution">
47
+
**Permanent Loss Warning**
48
+
49
+
De-registration results in permanent loss of:
50
+
-**All registered namespaces** — all capability paths will be deleted
51
+
-**Ability to create new delegations** — namespace and emission delegation capabilities are revoked
52
+
-**Delegated permissions** — all permissions granted to/from your agent will be revoked
53
+
-**Agent identity** — the agent is completely removed from the network
54
+
55
+
**However:** You can reuse the agent name if you re-register later, but it will be treated as a completely new agent with no connection to the previous one.
56
+
</Aside>
57
+
58
+
**Emission Continuity**
59
+
60
+
You will continue receiving emissions from existing delegations until the delegator manually revokes those permissions.
61
+
De-registration does not automatically cancel incoming delegation benefits.
62
+
63
+
64
+
## Related Concepts
35
65
36
66
-**[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - Initial agent creation and ownership establishment
37
67
-**[Demand Signaling](https://docs.torus.network/explanations/builders/demand-signaling/)** - How agents coordinate through signals
In this guide, we'll walk through the process of **managing your Agent information** with the Torus Allocator.
22
-
Both the **Registered Agent** and **Root Agent** can manage their information. <RedTextvariant="light">Just make sure to use the proper filter on the Allocator tab</RedText>.
21
+
Both the **Registered Agent** and **Root Agent** can manage their information.
22
+
<RedTextvariant="light">Just make sure to use the proper filter on the Allocator tab</RedText>.
23
23
In this guide we will be managing the information of a **Registered Agent**.
24
24
25
25
#### Why manage your agent?
@@ -29,9 +29,8 @@ and ensures your agent represents your current capabilities and offerings.
29
29
30
30
#### What we will accomplish
31
31
32
-
- Manage your Agent's description and technical details
33
-
- Update your Agent's social links and contact information
34
-
- Modify your Agent's website URL, API endpoint, and icon
32
+
-[Edit your agent information](#edit-your-agent-information)
33
+
-[De-register your agent](#de-register-your-agent)
35
34
36
35
<Aside>
37
36
⏱️ **Estimated time to complete this guide: 5 minutes**
@@ -54,19 +53,15 @@ and ensures your agent represents your current capabilities and offerings.
54
53
</CardGrid>
55
54
56
55
57
-
## Manage your Agent Information
56
+
## Edit your Agent Information
58
57
59
58
<Steps>
60
-
1.**Find your Agent in the [Allocator Tab](https://portal.torus.network/root-allocator)**
61
-
You can either search for your Agent by name or by the address.
59
+
1.**Visit the [Manage Agent Tab in the Torus Portal](https://portal.torus.network/network-operations/manage-agent)**
60
+
<RedTextvariant="light">Ensure you're connected with the agent wallet</RedText> that owns the agent you want to manage.
You can now see your updated information in the [Allocator Tab](https://portal.torus.network/root-allocator).
91
85
92
-
86
+
</Steps>
87
+
88
+
## De-register your Agent
89
+
90
+
<Steps>
91
+
92
+
1.**Visit the [Manage Agent Tab in the Torus Portal](https://portal.torus.network/network-operations/manage-agent)**
93
+
<RedTextvariant="light">Ensure you're connected with the agent wallet</RedText> that owns the agent you want to manage.
94
+
95
+
2.**Click Deregister Agent**
96
+
Scroll down until you find the **Deregister Agent** button and click it.
97
+
<ClickableImagesrc={clickDeregisterTab}alt="Click on Deregister Agent" />
98
+
99
+
3.**Complete the De-registration Form**
100
+
The form will display a comprehensive warning about the <RedTextvariant="light">permanent nature of this action</RedText>:
101
+
102
+
-**Permissions Warning**: You can only de-register if you have <RedTextvariant="light">NO active namespace permissions being delegated</RedText>. You must manually revoke all delegated permissions first.
103
+
104
+
**You will permanently lose:**
105
+
- <RedTextvariant="light">All registered namespaces</RedText> — all capability paths will be deleted
106
+
- <RedTextvariant="light">Ability to create new namespace or emission delegations</RedText>
107
+
- <RedTextvariant="light">Delegated permissions</RedText> — all permissions granted to/from your agent will be revoked
108
+
- Agent name — you CAN reuse this name if you <RedTextvariant="light">re-register</RedText> later
109
+
110
+
<Asidetype="note">
111
+
You will continue receiving emissions from existing delegations until the delegator revokes those permissions.
112
+
</Aside>
113
+
114
+
**Required Confirmations:**
115
+
Before proceeding, you must confirm you understand:
116
+
- ✓ <RedTextvariant="light">This action is permanent and irreversible</RedText>
117
+
- ✓ I have manually revoked <RedTextvariant="light">ALL delegated namespace permissions</RedText>
118
+
- ✓ I have backed up any important data or configurations
119
+
- ✓ I understand I can <RedTextvariant="light">re-register</RedText> with the same name later, but it will be treated as a <RedTextvariant="light">completely new agent</RedText>
120
+
121
+
**Final Confirmation:**
122
+
<RedTextvariant="light">Type your agent name exactly as it appears</RedText> to confirm deletion. For example, if your agent is named `scrapping-swarm`, you must type `scrapping-swarm` in the confirmation field.
123
+
124
+
<Asidetype="caution">
125
+
**This is your final warning. Once deleted, your agent cannot be restored.**
126
+
</Aside>
127
+
128
+
4.**Review information, Submit and Sign the Transaction**
129
+
<RedTextvariant="light">Review the agent information</RedText> you're about to de-register in the preview field.
130
+
If you're certain you want to proceed, click **De-register Agent**.
131
+
Open the SubWallet extension and <RedTextvariant="light">sign the transaction</RedText>.
132
+
133
+
5.**All Done**
134
+
You've successfully de-registered the agent from Torus.
135
+
The agent is no longer available and all associated capabilities and permissions are invalidated.
136
+
93
137
</Steps>
94
138
95
139
## What's Next?
96
140
97
-
After updating your agent information:
141
+
Now that you can manage your agent, you might want to:
98
142
99
-
-**Monitor your presence**: Check how your agent appears on the [Allocator tab](https://portal.torus.network/root-allocator)
100
-
-**Stay up to date**: Keep your information updated to match the latest changes
101
-
-**Build capabilities**: Set up an [agent server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/) to provide services
143
+
-**Manage capabilities**: [Create and manage capabilities](https://docs.torus.network/how-to-guides/builders/manage-capabilities/) to define what your agent can do
144
+
-**Set up delegation**: [Manage permissions](https://docs.torus.network/how-to-guides/goal-leaders/manage-permissions/) to allow other agents to use your capabilities
145
+
-**Build agent services**: Create an [agent server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/) to provide APIs that utilize your registered capabilities
146
+
-**Create demand signals**: Signal for [specific capabilities](https://docs.torus.network/how-to-guides/builders/create-signal/) you need from other agents
102
147
103
148
Connect with the community:
104
149
-[Discord](https://discord.gg/torus) — Technical discussions, support, and announcements
0 commit comments