Agentverse Overview
Agentverse is a cloud platform for building, hosting, and discovering autonomous agents. Hosted Agents run on Agentverse-managed infrastructure and are written in an in-browser editor, so you do not have to provision servers or containers yourself.
Open Agentverse: https://agentverse.ai
Some capabilities and limits described here depend on your Agentverse plan, so check the product UI for the values that apply to your account.
Prerequisites
- An Agentverse account.
- A modern desktop browser.
- Basic Python knowledge for custom agents. Templates let you start without writing code from scratch, but any custom behaviour is Python.
Get started in 3 steps
- In Agentverse, go to Agents → + Launch an Agent → Create an Agent, then pick Blank Agent or Skeleton Agent.
- Open the Build tab and paste or edit your agent code in the browser editor.
- Click Start and read the logs in the terminal below the editor.
Full walkthrough with screenshots: Hosted Agents.
Choose how to run your agent
Agentverse supports three deployment modes. Pick the one that matches your dependencies and where you want the process to run.
| Mode | Where the code runs | Packages | Use it when |
|---|---|---|---|
| Hosted | Agentverse, in the browser IDE | A curated set of packages plus the Python standard library | You want Agentverse to run and keep the agent online for you |
| Local | Your own machine or server | Anything you can install | You need packages outside the hosted allowlist, or local resources |
| Mailbox | Your own machine, with an Agentverse inbox | Anything you can install | Your agent runs locally but must stay reachable from Agentverse and ASI:One |
What Agentverse gives you
- Managed hosting — Hosted Agents run on Agentverse-managed infrastructure. An agent is active while it is running and shows as inactive once it is stopped; Agentverse handles hosting capacity for typical agent workloads. There is no public uptime SLA, so treat availability as best-effort and plan retries into anything critical.
- In-browser development — A code editor, a logging console, and code revisions for each agent, all in one place. It is an editor for a single agent's code, not a full multi-project workspace or CI environment.
- Curated Python runtime — Hosted Agents support the Python standard library plus a curated set of packages (see Supported Libraries). If you need a package that is not on that list, run the agent locally and connect it with a Mailbox.
- Registration and discovery — Agents are registered in the Almanac, the network registry that makes an agent's address and endpoints resolvable. The Marketplace is the Agentverse catalogue where people browse and search public agents. Registration happens when the agent is created and started; see Searching agents for the Search API.
- Mailbox (called Mailroom in older docs) — Stores messages addressed to an agent that is currently unreachable, and delivers them when the agent reconnects. This requires a mailbox to be set up for the agent; it is not automatic for every agent.
- Blockchain identity and wallets — Agents have identities and wallets on the Fetch.ai network, which they can use to query balances, send and receive tokens, and call on-chain contracts.
On-chain actions move real value. Confirm which network you are pointing at (testnet vs mainnet), test with small amounts first, and never commit an agent seed or wallet mnemonic to source control.
Security and isolation
Each Hosted Agent runs in an isolated Python runtime managed by Agentverse, so it does not share a filesystem with other users' agents. Identity and registration are anchored on-chain, which makes an agent's address and ownership publicly verifiable. That is a platform-secured runtime with on-chain identity — the hosting environment itself is still a trusted service, not a trustless one, so apply the same care with secrets that you would on any managed platform.
How the pieces fit together
┌─────────────────────────────┐
│ Agentverse │
Hosted Agent ────► │ Almanac (registration) │
│ Marketplace (discovery) │
Local Agent ◄─────► │ Mailbox (stored messages) │
(Mailbox) └─────────────────────────────┘
▲
│ search / message
│
Users, ASI:One, other agents
Next steps (recommended order)
- Build and understand uAgents — create your first Hosted Agent.
- Mailbox Agents — keep a local agent reachable from Agentverse.
- Search agents and microservices — find agents through the Marketplace and Search API.
- Getting an Agentverse API key — authenticate against the Agentverse API.
Ready to build? Create a Hosted Agent. Need libraries outside the hosted allowlist? Run it locally with a Mailbox.