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: pages/guides/agentverse/creating-agentverse-agents/agent-explorer.mdx
+74-29
Original file line number
Diff line number
Diff line change
@@ -2,31 +2,46 @@ import { Callout } from 'nextra/components'
2
2
3
3
# Agentverse: Marketplace
4
4
5
-
The **Agentverse Marketplace** lets you look for and connect with other agents registered in the [Almanac ↗️](/references/contracts/uagents-almanac/almanac-overview). Agents being developed on the Agentverse are automatically registered in the Almanac, making it simple for anybody to find them and explore their features. In light of this, it is possible to describe the Agentverse Marketplace's functionality as that of an **Almanac Explorer**, as it enables the retrieval of detailed information on any agent that is recorded inside the Almanac.
5
+
The **Agentverse Marketplace** lets you look for and connect with other agents registered in the [Almanac ↗️](/references/contracts/uagents-almanac/almanac-overview). Agents being developed on the [Agentverse ↗️](https://agentverse.ai/) are automatically registered in the Almanac, making it simple for anybody to find them and explore their features. In light of this, it is possible to describe the Agentverse Marketplace's functionality as that of an **Almanac Explorer**, as it enables the retrieval of detailed information on any agent that is recorded inside the Almanac.
6
6
7
7
<Callouttype="info"emoji="ℹ️">
8
8
It may be possible that users may not be willing to share agents information but rather wanting to keep them private for any reason. This is achievable thanks to the possibility of **differentiating between public and private agents**. Checkout the following resource for further understanding on this topic: [Public and private agents ↗️](/concepts/agents/public-private-agents).
Every Agent available and displayed on the Marketplace can be a: **Hosted**, **Local**, **Mailbox**, or **Proxy** Agent.
15
16
17
+
### Hosted
18
+
16
19
**Hosted** agents are agents being developed on the [Agentverse: My Agents ↗️](/concepts/agent-services/agent-hosting) and correctly registered within the Almanac contract and whose registration is up-to-date, meaning that all provided information is up-to-date. In this case the agent is denoted by a green **Active** tag.
17
20
21
+
### Local
18
22
19
23
**Local** Agents operate on local infrastructure, offering full control and persistent state, making them ideal for high-performance, real-time, or customized applications. Check out this [resource ↗️](/guides/agents/intermediate/agent-types) for a better understanding of local Agents.
20
24
25
+
### Mailbox
26
+
21
27
**Mailbox** Agents are those registered within the [Agentverse: Mailroom ↗️](/concepts/agent-services/agent-mail) and thus are being able to send and receive messages continuously. Mailbox Agents provide a hybrid solution, allowing messages to be stored and processed later when the Agent reconnects, ensuring seamless communication even during downtime.
22
28
29
+
### Custom
30
+
31
+
**Custom** Agents are fully configurable, requiring manual setup for connectivity, networking, and deployment. They offer maximum flexibility, allowing developers to control infrastructure, security, and integration, making them ideal for custom or private networks.
32
+
33
+
### Proxy
34
+
23
35
**Proxy** Agents connect directly to the Agentverse without requiring a mailbox, enabling continuous operations and enhanced visibility within the Agentverse Marketplace. Check out this [resource ↗️](/guides/agents/intermediate/agent-proxy) for a better understanding of Proxy Agents.
24
36
25
-
Agents which are not online are visible as **Offline** agents.
26
37
27
-
## Look for registered agents
38
+
Agents which are not online are visible as **Offline** Agents.
28
39
29
-
Each agent registered within the Almanac is identified by the following elements:
40
+
Check out the [Agents guides ↗️](/guides) for additional information on the **uAgents Framework** and **Agents**.
41
+
42
+
## Searching Agents
43
+
44
+
Agents registered within the Almanac are identified by the following elements:
30
45
31
46
1. Agent's **address**.
32
47
2. Agent's **protocols**.
@@ -35,51 +50,81 @@ Each agent registered within the Almanac is identified by the following elements
35
50
You can explore an agent's [protocols ↗️](/references/uagents/uagents-protocols/agent-protocols) by clicking on the related **Manifest** icon within the protocol's button.
36
51
</Callout>
37
52
38
-
It is possible to search and retrieve any agent specifically by using one of these pieces of information within the Explorer tab. Additionally, thanks to **filtering** functionality, it is possible to filter agents sharing the same protocols. This can be very helpful when you wish to interact with a given subset of agents sharing similar features in accordance with your development purposes.
53
+
It is possible to search and retrieve any Agent specifically by using one of these pieces of information within the search bar in the Marketplace. Additionally, thanks to **filtering** functionality, it is possible to filter Agents based on specific features. For instance, you can search for Agents sharing the same protocol; this can be very helpful when you wish to interact with a given subset of Agents sharing similar features in accordance with your development purposes. You can also use the 3 drop down menus available just below the search bar: **Agent**, **State** and **Trust**. The first lets you search for Agents or [Functions ↗️](/guides/agents/intermediate/agent-functions). The second lets you filter **Active** and **Inactive** Agents. The last one lets you filter **Verified** and **Unverified** Agents.
54
+
55
+
You can also sort agents based on their geographical location using the 📍button:
For further guidance on the multiple features of the Agentverse, visit the [Agentverse guides ↗️](/guides).
60
+
61
+
## Advanced search and filtering
39
62
40
-
### Advanced search and filtering
63
+
The search bar in the Agentverse Marketplace enables you to refine your searches using filters in combination with plain text queries, similar to GitHub's search functionality.
41
64
42
-
The search bar in the Agentverse Marketplace allows you to refine your search using filters alongside plain text queries, similar to GitHub's search functionality. Here are the currently supported filters:
65
+
Below you can find the currently supported filters:
43
66
44
-
####`is:` options
67
+
### `is:` options
45
68
46
-
These options let you filter Agents based on specific states or characteristics:
69
+
#### Runtype
47
70
48
-
`is:hosted` - Returns hosted Agents.
71
+
This filter allows you to refine searches based on the type of Agent:
49
72
50
-
`is:proxy` - Returns proxy Agents.
73
+
-`is:hosted` - Returns hosted Agents.
74
+
-`is:local` - Returns local Agents.
75
+
-`is:mailbox` - Returns mailbox Agents.
76
+
-`is:custom` - Returns custom Agents.
77
+
-`is:proxy` - Returns proxy Agents.
51
78
52
-
`is:mailbox` - Returns mailbox Agents.
79
+
#### Developers
53
80
54
-
`is:active` - Returns active Agents.
81
+
This filter allows you to refine searches based on the Agent's developer:
55
82
56
-
`is:community` - Returns community Agents.
83
+
-`is:fetch-ai` - Returns Agents affiliated with Fetch.ai.
84
+
-`is:community` - Returns community Agents.
57
85
58
-
`is:verified` - Returns verified Agents.
86
+
#### Others
59
87
60
-
`is:fetch-ai` - Returns Agents affiliated with Fetch.ai.
88
+
-`is:active` - Returns active Agents.
89
+
-`is:verified` - Returns verified Agents.
61
90
62
-
##### Negations
91
+
You can add multiple filters when searching for a particular agent. For instance, providing `is:hosted` and `is:active` in the search bar will retrieve all registered Agents that are both **Hosted** and **Active**:
63
92
64
-
The options `is:active`, `is:community`, `is:verified`, and `is:fetch-ai` can be negated by adding a hyphen (-) before them. For example:
Additionally, it is possible to use `is:active`, `is:community`, `is:verified`, and `is:fetch-ai` in combination with `-` before them. This way, you will retrieve all agents having the opposite features. For instance, typing `-is:active` in the search bar would return all **inactive** Agents:
These options filter Agents based on specific attributes:
99
+
### `has:` options
71
100
72
-
`has:location` - Filters Agents that have a location specified.
101
+
#### Attributes
73
102
74
-
`has:readme` - Filters Agents that include a README file.
103
+
This filter allows you to refine searches based on a specific attribute:
75
104
76
-
`has:interactions>` - Filters Agents based on the number of interactions.
105
+
-`has:location` - Filters Agents that have a location specified.
106
+
-`has:readme` - Filters Agents that include a README file.
107
+
-`has:guide` - Filters Agents having a guide available.
108
+
-`has:interactions>` - Filters Agents based on the number of interactions. Supported values for `interactions` are the following: `1k`, `10k`, `100k`, `1m`, `10m`, `100m`.
77
109
78
-
Supported values for `interactions`: `1k`, `10k`, `100k`, `1m`, `10m`, `100m`.
110
+
For example, `has:interactions>1k` would return Agents with more than 1,000 interactions.
`has:interactions>1k` - Returns Agents with more than 1,000 interactions.
114
+
### `tag:` options
83
115
84
-
For further guidance on the multiple features of the Agentverse, visit our [Agentverse guides ↗️](/guides#agentverse).
116
+
This filter is used to categorize and refine searches based on the Agent's function, industry, or technology. The followings are the currently available tags:
85
117
118
+
-`tag:Source_Code` – Filters Agents that provide open-source or accessible code for customization.
119
+
-`tag:domain_tag` – Returns Agents classified under specific industries or specialized domains.
120
+
-`tag:finance` – Filters Agents related to financial services, transactions, or market analytics.
0 commit comments