# Competitive Intelligence Brief — Agent Work Platforms

**Evidence snapshot:** 17–18 September 2026  
**Scope:** Olas, Agentverse / Fetch.ai, Nevermined, Virtuals Protocol, and Skyfire as an additional relevant platform.

## Executive takeaway

**Product inference:** No single comparator visibly solves the whole Locus problem. The strongest reusable pattern is a layered system: open service registration and discovery (Agentverse or Olas), explicit job protocols and settlement (Virtuals), constrained budgets and revocation (Nevermined), and portable verified identity (Skyfire). Locus should connect those layers through one evidence-bearing work history rather than copying any platform’s token, marketplace, or branding model.

## Evidence-backed comparison

| Platform | Work or service discovery | Identity and reputation | Payments or budgets | Can outside agents join? |
|---|---|---|---|---|
| **Olas** | Olas describes Mech Marketplace as a decentralized marketplace where agents can hire other agents’ services or offer their own services. Pearl is presented as an agent app store. [[O1]](#sources) | The retrieved overview emphasizes co-ownership, governance, developer rewards, staking, and rewards for useful contributions; it does not document a portable identity or durable reputation mechanism. [[O1]](#sources) | Marketplace suppliers can earn crypto; the OLAS utility token coordinates agent interactions, while bonding and staking provide ecosystem incentives. The source does not specify customer-side budget controls. [[O1]](#sources) | **Likely yes (inference):** the source invites users to offer their own agents’ services and calls developer rewards permissionless, although marketplace admission details are not given. [[O1]](#sources) |
| **Agentverse / Fetch.ai** | Agentverse provides agent registration for search/discovery, hosting, and a marketplace for searching and discovering agents. Fetch.ai calls its marketplace an open directory and reports 2.7 million agents. [[F1]](#sources) | The source mentions verified brand agents plus tools to improve an agent’s visibility and ranking. It does not explain whether ranking reflects verified work outcomes or how reputation disputes are handled. [[F1]](#sources) | Fetch.ai lists smart contracts and agent payments, a public ledger of agents and transactions, token management, and wallets. The retrieved page does not describe mandate-based budgets or escrow. [[F1]](#sources) | **Yes at the registration layer:** the documentation explicitly offers “Register Your Agent,” agent hosting, development guides, adapters, and no-code tooling. [[F1]](#sources) |
| **Nevermined** | Its Agent Catalog lists curated AI services, and Commerce MCP is described as allowing an MCP client to find and pay for services. [[N1]](#sources) | Nevermined attributes transactions to an agent-specific mandate, but the retrieved page does not describe a general identity credential or historical reputation score. [[N1]](#sources) | Agents can receive virtual cards and revocable spending mandates with monthly and per-transaction limits. Nevermined also supports merchant payments, metering, x402, MPP, card rails, and settlement to a merchant’s payment provider. [[N1]](#sources) | **Supported as infrastructure, not proven as an open labor market:** the site offers SDKs, APIs, merchant integrations, cards, and budgets for agents, but the retrieved evidence does not establish unrestricted enrollment in a shared work marketplace. [[N1]](#sources) |
| **Virtuals Protocol** | Its Agent Commerce Protocol (ACP) is presented as a marketplace where agents discover services, negotiate jobs, coordinate execution, and settle payments. Listed primitives include an agent registry and job-specification standard. [[V1]](#sources) | EconomyOS supplies identity, email, domain, wallet, permissions, access control, and memory. ACP lists neutral evaluation, but the source does not explain whether evaluations accumulate into durable reputation. [[V1]](#sources) | EconomyOS includes wallets, payroll, permissions, and programmable capital; ACP lists trustless escrow and x402 settlement. [[V1]](#sources) | **Apparently yes, with conditions unclear:** the site provides “Create Agent” and “Explore Agent Offerings” paths, but the retrieved page does not state admission, chain, or capitalization requirements. [[V1]](#sources) |
| **Skyfire** | Skyfire is an identity, access, and checkout stack rather than a work marketplace; the retrieved page does not provide a job or service-discovery mechanism. [[S1]](#sources) | Its Know Your Agent (KYA) product is described as a portable verified identity token for access, login, services, and checkout across the open internet. [[S1]](#sources) | The agentic wallet can enroll user cards, manage stablecoins, collect user mandates, and execute tokenized-card transactions; the page names major card networks and USDC. [[S1]](#sources) | **Not established by the retrieved evidence:** Skyfire offers infrastructure for agents, but its homepage does not state whether any outside agent can self-register or obtain credentials without review. [[S1]](#sources) |

## Product lessons for Locus

### Olas
**Inference:** Separate contribution modes—building, operating, supplying services, governance, and liquidity—rather than treating every participant as the same kind of worker. Locus could reward useful contributions and operation without importing token staking or making financial stake a proxy for trust.

### Agentverse / Fetch.ai
**Inference:** Make agent capabilities searchable through a structured registry and provide a low-friction registration path. Locus should ensure ranking is grounded in attributable completed work, not merely visibility optimization, and should expose why an agent ranks where it does.

### Nevermined
**Inference:** Budgets should be explicit capabilities: scoped, capped, attributable, and instantly revocable. Locus could attach a mandate to each accepted job or delegation so that payment authority is never broader than the work requires.

### Virtuals Protocol
**Inference:** Standardize the full job lifecycle—discovery, specification, negotiation, execution, evaluation, and settlement. Locus should preserve human-readable evidence and appeal paths around any automated evaluation or escrow decision rather than relying only on “trustless” execution.

### Skyfire
**Inference:** Identity should be portable but purpose-limited. Locus could issue verifiable agent credentials for access and payment while keeping identity proof distinct from reputation: a verified agent is not necessarily a reliable worker.

## Recommended Locus pattern

1. **Open capability registry:** agents publish structured offerings, constraints, prices, and evidence links.
2. **Evidence-backed work history:** reputation derives from attributable accepted work, delivery, evaluation, disputes, and settlement—not purchased visibility or asset ownership.
3. **Job-scoped mandates:** every delegation carries budget, counterparty, time, transaction, and revocation limits.
4. **Explicit work protocol:** represent proposal, acceptance, execution, delivery, review, dispute, and payment as separate auditable states.
5. **Layered trust:** distinguish verified identity, capability evidence, customer evaluation, economic stake, and platform standing.
6. **Permissionless discovery, controlled execution:** allow broad listing and search while applying proportionate checks when credentials, funds, or sensitive resources are used.

## Evidence limits

The sources are official vendor pages, so they establish how each vendor publicly describes its offering, not independent proof that every feature performs as claimed. Where a retrieved page was silent—especially on reputation, admission rules, or budget controls—the table reports that limitation rather than treating silence as proof of absence.

## Sources

- <a id="O1"></a>**[O1] Olas Docs**, “Olas Docs,” retrieved 17 September 2026: https://docs.olas.network/
- <a id="F1"></a>**[F1] Fetch.ai**, “Fetch.ai Developer Platform | Documentation,” retrieved 17 September 2026: https://www.fetch.ai/docs
- <a id="N1"></a>**[N1] Nevermined**, “Payments Infrastructure for AI Agents,” retrieved 17 September 2026: https://nevermined.ai/
- <a id="V1"></a>**[V1] Virtuals Protocol**, “Society of AI Agents,” retrieved 18 September 2026: https://www.virtuals.io/
- <a id="S1"></a>**[S1] Skyfire**, “The Agent Trust Stack,” retrieved 17 September 2026: https://skyfire.xyz/