Skip to main content

Olas (Autonolas)

Olas (Autonolas) (OLAS) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Olas (Autonolas) — an AI/Agents | Infra project on Ethereum, token (symbol: OLAS).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: a protocol and a set of products for “co‑owned AI” and autonomous agent services (agent economies), including Pearl (an AI agent store) and Mech Marketplace (a marketplace/“bazaar” for AI agents).
  • Who it’s for: users of AI agents; developers/operators of autonomous services; DAO teams.
  • Why onchain/token: OLAS is used for access/staking in Pearl and as the coordination token of the protocol; the onchain part includes the token and a number of contracts/registries (for example veOLAS, timelock, etc. — in Tier‑1).
  • What you can actually touch (Tier‑1): Pearl (an app store of AI agents) — https://pearl.you/

How it works (very briefly)

  1. The user does: opens Pearl and chooses an AI agent for a task (or uses/deploys an agent service).
  2. The system does: gives the agent access to capabilities and to the economy (including via the marketplace for agent‑to‑agent interaction).
  3. The user gets: an “own & use” AI agent (and potential rewards/perks when staking OLAS — as claimed on the website).
  4. Where the blockchain is: the OLAS token and the protocol contracts (veOLAS, timelock, governor, component registries, etc.) are recorded onchain; the tokenomics describes the representation of code/services via NFT registries on Ethereum and the anchoring of services to a settlement layer.
  5. Token role (if any): OLAS is used for access/staking in Pearl, governance via veOLAS and for the protocol tokenomics.

Quick links: AI thesis fit

Project passport

Field Value
Project name Olas (Autonolas)
Also known as (aliases) Autonolas; Olas Protocol; OLAS; veOLAS
Logo (logo) ../assets/110_autonolas_logo.svg
Token symbol (ticker) OLAS
Category AI/Agents | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) 2022-06-30
Project status (status) active
Token (standard) ERC-20
Token contract 0x0001A500A6B18995B03f44bb040A5fFc28E45CB0
Token model (token_type) utility (payments + staking + governance)
Max supply 527,815,641.713312267061471518 OLAS
Issuance inflationary (capped)
Tokenomics (tokenomics, brief) in the tokenomics doc: an inflationary token with an issuance schedule, “bonding” and incentives for code composability/staking; on the website: Pearl users stake OLAS, and fees are used to burn OLAS
Governance DAO (veOLAS)
Admins/keys timelock + governance contracts (in the bug bounty scope)
Audit yes (Code4rena audit competition, 2023-12)
Bug bounty yes (Immunefi)
Team (team) Valory AG
Funding (investors/funding) —
AI component (ai_component) autonomous AI agents + agent services
Use‑case (use_case) AI agent app store + marketplace
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 2 / token_score 3 / evidence_score 3
Last verified 2026-02-11

General project overview

Olas (Autonolas) is positioned as a protocol and ecosystem for autonomous services and AI agents that can be “co‑owned” and monetizable. The website highlights two user products:

  • Pearl — an “AI Agent App‑Store”, where the user chooses and “owns” an agent; it is stated that access to the agents’ benefits is linked to staking OLAS.
  • Mech Marketplace — an “AI Agent Bazaar” for autonomous hiring/interaction of agents with each other; it is claimed that the marketplace charges fees and the fees are used to burn OLAS.

The tokenomics and the whitepaper describe the “autonomous services” architecture as a multi‑agent system in which code/components/agents are registered onchain (via NFT registries) and services are anchored to a settlement layer (for example Ethereum).

Features/modules

  • Pearl: choosing/using AI agents; staking OLAS for access to benefits (as claimed).
  • Mech Marketplace: a market for AI agents (A2A collaboration, monetization).
  • Onchain layer: the OLAS token, governance (veOLAS) and a set of contracts/registries (timelock, component registry, etc. — listed in the Tier‑1 bug bounty scope).
  • Tokenomics primitives: bonding, incentives for code composability and a “staking model for code” (NFT representation of code) in the tokenomics doc.

Typical scenarios

  • Scenario 1: a user stakes/uses OLAS and runs an agent in Pearl → receives “human‑like utility” from the chosen agent.
  • Scenario 2: a developer/team deploys an autonomous agent service → registers components/agents/services onchain and plugs into the protocol economy.
  • Scenario 3: an agent/operator uses Mech Marketplace → buys/sells capabilities, pays fees (which, per the description, are used to burn OLAS).

Getting started (wallet/network)

  • What you need: web access to Pearl/Mech Marketplace; for onchain actions — an EVM wallet.
  • Network/chain: the base onchain anchor is Ethereum (the OLAS contract); the protocol is claimed to be multichain/chain‑agnostic.
  • Fees: Ethereum gas for onchain operations; protocol fees/staking operations per the product model.

Architecture/tech (non‑AI)

  • Components: onchain contracts (OLAS, veOLAS, timelock, governor, etc.); offchain agent services (multi‑agent system); the Pearl and Mech Marketplace products.
  • Participant roles: Pearl users; developers of agents/components; service operators; DAO participants (veOLAS holders).
  • Where logic runs: the main runtime of agent services is offchain; onchain records governance/registries and the security anchoring of key data.
  • Dependencies: Ethereum (settlement layer), EVM infrastructure, web clients.

Token/economics (expanded, no forecasts)

  • Token utility: OLAS is a utility token for access to the core functions of the protocol; Pearl users stake OLAS for access to agent benefits.
  • Protocol necessity drivers: in the tokenomics doc, OLAS is described as the coordination token for incentives, bonding and top‑ups; on the website, OLAS links Pearl and the marketplace economy.
  • Who pays fees: agents/users of the marketplace (as claimed: the marketplace charges fees).
  • Where fees go: per the description on the website: fees are used to burn OLAS.
  • Issuance/burn: the tokenomics doc describes an inflationary model and an issuance schedule; a burn component at the level of the marketplace economy is also described.
  • Security/incentive mechanisms: staking/lock for governance (veOLAS) and incentives; the bug bounty scope shows timelock/escrow/governor as part of the onchain security surface.
  • Distribution and token issuance schedule: described in the tokenomics document (allocation and the inflationary schedule).
  • Treasury: a DAO treasury is mentioned in the tokenomics document (distribution/model).

Governance

  • Who makes decisions: onchain governance via the OLAS DAO / veOLAS (per the docs).
  • How protocol parameters change: via governance proposals/votes and timelock execution (see the docs/contracts).
  • Where decisions are discussed/made: — (a Tier‑1 forum/discussion process is not explicitly indicated in this card; see links_*).
  • Keys/multisig: a timelock is present (as part of the onchain surface); information about a multisig is not recorded in the reviewed Tier‑1 sources.

Security and incidents

  • Audits: yes (see links_* → Audit report(s)).
  • Bug bounty: yes (see links_* → Bug bounty).
  • Incidents: — (no Tier‑1 postmortems/incidents found).
  • Threat model: risks of the governance contracts (timelock/escrow/governor), risks of the registries/components and of the economics of the incentive contracts.

Project status and timeline

  • Current status: active (mainnet contracts and public docs).
  • Key releases/milestones: — (not collected in this card).
  • Roadmap: — (not collected in this card; see links_*/docs if needed).

Ecosystem/integrations

  • Integrations: not established (a Tier‑1 list of integrations is not collected in this card).
  • Partners: — (no Tier‑1 confirmed list of partners found).
  • Where it’s actually used: the OLAS protocol contracts/economy and the ecosystem products (Pearl/Mech Marketplace — per the docs).

AI component of the project

  • What is real AI here? Tier‑1 positions the products as “AI agents” (Pearl and Mech Marketplace for AI agents).
  • What is truly onchain? there is the ERC‑20 token OLAS on Ethereum and a set of protocol contracts/registries (timelock, voting escrow veOLAS, component registry, etc.).
  • Why is a token needed? OLAS is used for staking/access in Pearl, governance via veOLAS, and for the protocol tokenomics (bonding/incentives); fees are also used to burn OLAS.
  • Red flags (based on the information found): AI‑washing risk (if the “AI agents” do not disclose which models/methods are inside). What to double‑check: the specific AI models and measurable quality metrics for specific agents.

DecAI Fit component summary

  • DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
Onchain necessity medium 2
Token necessity high 3
Evidence Tier‑1 present 3
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is a Tier‑1 description of working AI agent products (AI_1=1), so AI_0 is not used as “intent only”.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): an ecosystem of AI agents: Pearl provides access to AI agents, and Mech Marketplace — a market/cooperation of AI agents.
  • Evidence: Tier‑1 — https://www.olas.network ; https://www.autonolas.network/whitepaper
  • Why sufficient / why not (one line): Tier‑1 explicitly positions the products as AI agents (not only “AI intent”).
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): Pearl (an app store of AI agents) and the Mech Marketplace pages (a market of AI agents) are available.
  • Evidence: Tier‑1 — https://pearl.you/ ; https://olas.network/mech-marketplace
  • Why sufficient / why not (one line): these are public user interfaces of the products.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Tier‑1 shows ecosystem activity metrics (agents deployed, A2A txns, etc.), but these are not quality/accuracy metrics of AI models.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 0
  • Claim (one line): there is a technical description of the autonomous services and the tokenomics, but without specifications of AI models/weights/versions.
  • Evidence: Tier‑1 — https://www.autonolas.network/documents/whitepaper/Autonolas_Tokenomics_Core_Technical_Document.pdf
  • Why sufficient / why not (one line): the document describes the autonomous services/agent architecture and incentives, but does not disclose specific AI models.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: OLAS token: 0x0001A500A6B18995B03f44bb040A5fFc28E45CB0
  • Evidence: Tier‑1 — https://etherscan.io/token/0x0001a500a6b18995b03f44bb040a5ffc28e45cb0 ; https://etherscan.io/address/0x0001A500A6B18995B03f44bb040A5fFc28E45CB0
  • Why sufficient / why not (one line): the token contract and its creation date are confirmed by the explorer.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 1
  • What useful logic is onchain: governance (timelock, voting escrow veOLAS, governor) and protocol registries (for example the Component Registry) as part of Autonolas.
  • Evidence: Tier‑1 — https://immunefi.com/bug-bounty/autonolas/scope/ ; https://www.autonolas.network/documents/whitepaper/Autonolas_Tokenomics_Core_Technical_Document.pdf
  • Why sufficient / why not (one line): Tier‑1 lists the protocol contracts in scope; the tokenomics doc describes onchain registration/anchoring of services.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: Tier‑1 provides no strict “what breaks” test, although onchain is used for registries/anchoring/the economy.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): the existence of onchain components is proven, but the necessity of the blockchain specifically as an irreplaceable layer is not formalized.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, OLAS (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x0001a500a6b18995b03f44bb040a5ffc28e45cb0
  • Why sufficient / why not (one line): the token contract exists on Ethereum.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): the marketplace charges fees, which are used to burn OLAS.
  • Evidence: Tier‑1 — https://www.olas.network
  • Why sufficient / why not (one line): Tier‑1 directly describes the fees → burn OLAS mechanisms.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): users stake OLAS for access to the benefits of Pearl agents; the tokenomics describes staking/lock mechanics.
  • Evidence: Tier‑1 — https://www.olas.network ; https://www.autonolas.network/documents/whitepaper/Autonolas_Tokenomics_Core_Technical_Document.pdf
  • Why sufficient / why not (one line): Tier‑1 describes staking/lock as part of the economic model.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): governance via veOLAS (voting escrow) and the governor/timelock contracts.
  • Evidence: Tier‑1 — https://immunefi.com/bug-bounty/autonolas/scope/ ; https://www.autonolas.network/documents/whitepaper/Autonolas_Tokenomics_Core_Technical_Document.pdf
  • Why sufficient / why not (one line): Tier‑1 lists veOLAS/governor/timelock and describes the role of governance/locking.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the tokenomics/staking/veOLAS/governance are mechanically tied to OLAS as the coordination token.
  • Evidence: Tier‑1 — https://www.autonolas.network/documents/whitepaper/Autonolas_Tokenomics_Core_Technical_Document.pdf ; https://immunefi.com/bug-bounty/autonolas/scope/
  • Why sufficient / why not (one line): Tier‑1 describes the token as a core primitive and shows the related contract surface.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.olas.network positioning: co‑owned AI; Pearl (AI Agent App‑Store); Mech Marketplace; staking OLAS; fees → burn OLAS; token address
Tier‑1 https://pearl.you/ demo/product Pearl (access to AI agents)
Tier‑1 https://olas.network/mech-marketplace the Mech Marketplace product (bazaar/marketplace for AI agents)
Tier‑1 https://etherscan.io/token/0x0001a500a6b18995b03f44bb040a5ffc28e45cb0 the OLAS token (ERC‑20) and max total supply on Ethereum
Tier‑1 https://etherscan.io/address/0x0001A500A6B18995B03f44bb040A5fFc28E45CB0 creation date of the OLAS contract: 2022-06-30
Tier‑1 https://www.autonolas.network/documents/whitepaper/Autonolas_Tokenomics_Core_Technical_Document.pdf architecture of autonomous services, onchain registries/NFT representation of code, OLAS/veOLAS tokenomics
Tier‑1 https://immunefi.com/bug-bounty/autonolas/scope/ list of the protocol’s onchain contracts (OLAS, timelock, veOLAS, governor, component registry, etc.)
Tier‑1 https://code4rena.com/audits/2023-12-olas the existence of an audit (Code4rena)

No comments to display

Back to top