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 start touching real wallets, real orders, real permissions, a harder question shows up:

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 over time for ERC-8004 agent networks as well.

---

What Bardiel Is

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

• Delegation – offloading heavy or complex tasks (plus tooling like web/data access) to Cortensor with explicit reliability tiers, so agents can keep their “brain/logic” local and treat Bardiel as an execution layer.

• Validation – acting as a second opinion or pre-/post-action checkpoint, using redundancy, PoI/PoUW, and structured templates instead of vibes.

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

Bardiel is not:

• a new blockchain or compute network

• a planner or 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 whenever 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, web/data, and Cortensor) under a given trust tier

  • validate_with_bardiel(task, claimed_result, policy) – think twice before acting; get a verdict like VALID, INVALID, RETRY, or NEEDS_SPEC

  • optional arb_with_bardiel(dispute_payload) – an extra oracle layer in complex or high-stakes cases

Bardiel fits into Virtual as:

• a Worker/Function target (for example, 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 plan or reason

For most everyday Virtual use, Bardiel is a pre-action safety and quality layer: it helps agents avoid bad calls before ACP evaluators and dispute mechanisms need to step in.

---

Bardiel and Cortensor

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

• submits tasks to Cortensor Router nodes

• chooses a policy tier (fast, safe, oracle, adaptive) and requests redundancy (1, 3, 5+, or dynamic)

• uses Bardiel-side tooling (web fetch, search, spec normalizer, schema helper, etc.) to shape the context

• collects miner outputs and trust signals (PoI, PoUW, reputation, integrity checks, schema/spec validation)

• applies oracle logic to choose a result and a 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, integrity)

• verifiable, replayable task history

Bardiel turns those low-level signals into simple, actionable outcomes that agents and markets can actually use.

---

When to Use Bardiel

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

• high-stakes summaries, classifications, or analyses where being wrong is expensive

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

• second opinions on intermediate reasoning steps or proposed actions

• delegated research and long-running workflows that should come back already cross-checked

• dispute resolution in marketplaces that integrate Bardiel as an arbitration oracle

• any workflow where redundancy, proofs, and clear verdicts are required instead of blind trust

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.