Introduction

Agents are becoming the default abstraction for applications: they plan, call tools, coordinate with other agents, and transact on behalf of users. As soon as they are given real budgets and real users, a hard question appears:

Which agent should we trust?

Most agent systems today can execute tasks, but they still lack:

• a neutral, independent surface that can re-run or replicate work

• a standard validation layer to check correctness and usefulness

• a credible oracle to resolve disputes between buyers, sellers, and agents

Bardiel is designed to fill that gap — first for the Virtual ecosystem, and then for ERC-8004 agent networks.

---

What Bardiel Is

Bardiel is a Virtual-native service agent, built by Virtual and powered by Cortensor. It focuses on:

• Delegation – offloading heavy or complex tasks (plus tooling like web access) to Cortensor with reliability tiers.

• Validation – acting as a second opinion or pre-action check, using redundancy and scoring instead of vibes.

• Arbitration – providing dispute verdicts for markets that wire Bardiel into their settlement flows (primarily ERC-8004).

Bardiel is not:

• a new blockchain or compute network

• a planner/goal generator (that’s the GAME Agent’s job)

• a Cortensor miner or part of Cortensor’s base validator set

Instead, it is a productized trust + execution layer that other agents can call when they need reliable and verifiable results, not just “an answer.”

---

Bardiel in the Virtual Ecosystem

Within the Virtual ecosystem, Bardiel behaves as a service agent that other agents call through GAME and ACP:

• GAME (agent brain)

  • agents plan and decide when to ask Bardiel for help

  • Workers/Functions call Bardiel for delegation or validation

• Bardiel (service agent)

  • delegate_to_bardiel(task, policy) – run this task with tools + tiers

  • validate_with_bardiel(task, claimed_result, policy) – think twice before acting

  • optional arb_with_bardiel(dispute_payload) – extra oracle in complex cases

Bardiel fits into Virtual as:

• a Worker/Function target (e.g. delegate_to_bardiel, validate_with_bardiel)

• a service provider in ACP for high-trust execution and pre-settlement checks

• a trust oracle that plugs into existing GAME workflows without changing how agents think

For everyday Virtual use, Bardiel is mostly a pre-action safety and quality layer: it helps agents avoid bad calls before ACP evaluators and dispute mechanisms get involved.

---

Bardiel and Cortensor

Bardiel itself does not run heavy compute. It acts as a smart client of Cortensor:

• submits tasks to Cortensor Router nodes

• requests redundancy (1, 3, 5, or adaptive)

• uses tools (web fetch, search, spec normalizer, schema helper, etc.) to shape the context

• collects miner outputs and trust signals (PoI, PoUW, reputation, integrity)

• applies oracle logic to choose a result and verdict

From an agent’s perspective, this all collapses into a single call to Bardiel. Under the hood, Cortensor provides:

• decentralized inference (miners)

• validation and scoring (PoI / PoUW, reputation)

• verifiable, replayable task history

Bardiel turns those low-level signals into simple, actionable outcomes.

---

When to Use Bardiel

Use Bardiel whenever an agent needs more than a best-effort answer:

• high-stakes summaries, classifications, or analyses

• pre-action validation before calling tools, moving funds, or settling a job

• second opinions on intermediate reasoning steps or proposed actions

• dispute resolution in marketplaces that integrate Bardiel as an oracle

• any workflow where redundancy, proofs, and clear verdicts are required

In short:

If an agent needs to trust a result — not just get one — it should talk to Bardiel, and Bardiel will talk to Cortensor.