| Authors | Fetch.ai and uAgents contributors |
|---|---|
| Document | Developer documentation reference; snapshot 2026-10-08 |
| Project | Fetch.ai / uAgents |
| License | uAgents software: Apache-2.0; paper/documentation license not verified |
| Official Source | Fetch.ai Developer Platform |
Fetch.ai’s developer architecture connects programmed agents, message discovery, hosting and optional language-model services. This reference follows official documentation reviewed on 8 October 2026. The older linked whitepaper route could not be verified; a current framework description should not be attributed to an unread 2019 paper. Token prices and alliance membership are outside this reference’s scope.
Agent Software Is Not Automatically Onchain AI
uAgents is a Python framework whose handlers respond to messages, events or scheduled tasks. An agent can execute ordinary programmed logic; integrating an LLM is an additional choice. Its ability to call tools comes from the code and permissions provided by its developer, rather than the framework automatically deciding every task.
The repository licenses uAgents software under Apache-2.0. That license does not establish the reuse terms or authorship of a historical whitepaper. Its README also describes optional Agentverse event reporting, so a deployment’s telemetry configuration matters.
Communication Identity and Wallet Identity
The address guide distinguishes the agent’s communication address from its Fetch network wallet address. The former identifies a recipient for messaging; the latter holds assets and interacts with ledger contracts. Identifying an agent does not by itself establish a human’s identity, service quality or authorization to spend another person’s funds.
A seed can reproduce the agent identity. The seed guide warns that disclosure can enable impersonation and access to its wallet. A developer must protect the deployment’s keys and API credentials; published demonstration phrases are not production secrets.
Messages, Protocols and Discovery
The communication guide demonstrates local messages and remote resolution of a recipient’s HTTP endpoint through Almanac. Those messages are not each necessarily a blockchain transaction. Compatible message models and handlers are required for the applications to understand one another.
A uAgents Protocol groups message types and handlers; it has no separate identity and cannot run independently. Including one adds behavior to an agent. A declared booking-response schema does not prove that a real reservation system was contacted.
Almanac publishes registration information such as endpoints and supported protocols. Registrations require renewal and expire. Signature validation checks address ownership, while a registered endpoint must still be available and its service behavior assessed. Discovery is not an endorsement of the result.
Agentverse, Mailboxes and ASI:One
Agentverse supports hosted and external agents. Its discovery, metadata, ranking and analytics belong to a platform layer, distinct from running local open-source agent code. A listing does not establish that every agent’s computation is performed onchain or that paid usage guarantees developer revenue.
A mailbox temporarily stores incoming messages so an offline or firewalled agent can collect them later. It does not execute the agent’s task while its runtime is stopped. Hosting and mailbox availability remain operational dependencies.
The ASI:One example uses a chat protocol, acknowledges receipt and calls a model API before sending a reply. Its fallback response handles a failed model call. An acknowledgement is not successful task completion, and a model-generated response is not proof that an external purchase or reservation occurred. Old planned payment-release dates are not confirmation of a currently available feature.
Authentication Has Limits
The verification guide demonstrates signing and checking a message digest. Applications must bind the checked digest to the actual payload they act on. Authentication can establish a signing identity and detect changes to the signed data; it does not prove the truth of a response, grant unlimited tool permissions or remove model, API and counterparty risk.
Social Media Sentiment
Not assessed for this technical reference. No dated discussion sample was collected; promotional ecosystem totals and token narratives are not current sentiment evidence.
Last updated: 2026-10
Related Terms
- Public Key — signature verification.
- Cosmos — background on the wider blockchain ecosystem.
See Also
- Bittensor Intelligence Market Reference — a different distributed-AI design.
Sources
- Fetch.ai and uAgents documentation contributors. Fetch.ai Developer Platform. Reviewed 8 October 2026. Current product and documentation entry points.
- Fetch.ai and uAgents documentation contributors. uAgents Repository and README. Reviewed 8 October 2026. Software license, runtime and optional telemetry.
- Fetch.ai and uAgents documentation contributors. uAgents Framework Introduction. Reviewed 8 October 2026. Programmed agents and optional language-model integrations.
- Fetch.ai and uAgents documentation contributors. Agent Addresses. Reviewed 8 October 2026. Agent communication identity versus ledger wallet address.
- Fetch.ai and uAgents documentation contributors. Seed Phrases. Reviewed 8 October 2026. Seed-based identity and wallet compromise risk.
- Fetch.ai and uAgents documentation contributors. Communicating with Other Agents. Reviewed 8 October 2026. Local messages and remote endpoint resolution.
- Fetch.ai and uAgents documentation contributors. Agent Protocols. Reviewed 8 October 2026. Message models and handlers rather than an independent runtime.
- Fetch.ai and uAgents documentation contributors. The Almanac. Reviewed 8 October 2026. Registration renewal, signatures and protocol discovery.
- Fetch.ai and uAgents documentation contributors. Agentverse v2 Overview. Reviewed 8 October 2026. Hosted versus external agents and platform discovery.
- Fetch.ai and uAgents documentation contributors. Agent Mailboxes. Reviewed 8 October 2026. Temporary message storage rather than execution while offline.
- Fetch.ai and uAgents documentation contributors. ASI:One Compatible Agent Example. Reviewed 8 October 2026. Chat acknowledgements, model/API dependency and fallback handling.
- Fetch.ai and uAgents documentation contributors. Message Verification Guide. Reviewed 8 October 2026. Digest signatures and the limits of authentication.