What is Bardiel?

Bardiel is a Virtual-native service agent that acts as a trust and execution oracle for other agents.

Most agents today can call tools, hit APIs, and complete tasks – but as soon as they touch real users, real budgets, or real permissions, a harder question appears:

“Which agent should we trust — and who’s actually checking their work?”

Bardiel exists to answer that question inside Virtual first, and then for ERC-8004 agent ecosystems that need the same reliability via a shared /delegate and /validate layer.

---

Why Bardiel Exists

Agent systems typically 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 fills this gap by combining:

• Virtual – agent “brains,” tools, and markets (GAME, ACP, buyers/sellers)

• Cortensor – decentralized compute + proofs (Router, miners, validators, PoI/PoUW)

• Bardiel – a decision + execution layer that turns those proofs into simple, actionable verdicts

Conceptually:

• /delegate → “AWS for agents” – offload work to a shared, verifiable execution fabric

• /validate → “safety checkpoint” – pre-/post-action verification before you trust or pay

Instead of every agent building its own trust stack, Bardiel provides a shared, verifiable execution layer they can all lean on.

---

Bardiel in the Virtual Ecosystem

Within Virtual, Bardiel behaves as a service agent that other agents call through:

• GAME Workers/Functions

• ACP flows and market logic

GAME provides the brain + orchestration:

• agents plan and decide when to use Bardiel

• Workers execute and call real functions

Bardiel provides the execution + trust layer:

• decides where and how to run a task on Cortensor via /delegate

• applies a policy tier (fast, safe, oracle, adaptive)

• uses tooling (web fetch, search, spec normalizer, schema helpers, etc.) to shape context

• interprets PoI/PoUW signals, reputation, integrity, and spec/schema checks

• returns a clear result + verdict + evidence

From a Virtual developer’s perspective, Bardiel is:

• a Worker/Function target you can call, for example:

  • delegate_to_bardiel(task, policy)

  • validate_with_bardiel(task, claimed_result, policy)

• a service provider in ACP for:

  • high-trust execution (delegated jobs that come back pre-validated)

  • pre-action checks and second opinions before settlement

  • optional extra oracle signals in complex disputes

In day-to-day Virtual flows, Bardiel mostly acts as a pre-action safety and quality layer: agents keep their “brain” in GAME, and rely on Bardiel to do the work and check the work before ACP or other evaluators step in.

---

Bardiel and ERC-8004

Beyond Virtual, Bardiel can also register as a validator / oracle service for ERC-8004 agent ecosystems:

• ERC-8004 agents can delegate tasks to Bardiel for reliable execution on Cortensor via an agent-native /delegate surface.

• Bardiel can serve as a task validator via the 8004 registry (pre- and/or post-action checks using /validate).

• For marketplaces that integrate it, Bardiel can act as a dispute oracle (Arbitration-as-a-Service) using oracle-grade policies.

The ordering is simple:

1. Virtual-first – Bardiel’s primary home and integration surface.

2. ERC-8004-next – external agent ecosystems that want the same execution and verification layer, wired in over ERC-8004/x402/MCP surfaces.

Under the hood, both Virtual and ERC-8004 paths end up using the same Bardiel → Cortensor pipeline.

---

How Bardiel Uses Cortensor

Bardiel does not run models itself. It acts as a smart Cortensor client and execution layer:

• creates or reuses sessions with pre-paid budgets (Stake-to-Use / x402)

• submits tasks through Cortensor Router nodes

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

• uses Bardiel-side tooling to prepare context (web access, spec normalization, schema checks, etc.)

• collects miner outputs and trust signals, including:

  • PoI consistency and N-of-M consensus

  • PoUW usefulness scores

  • reputation and stake weighting

  • schema/spec validation

  • integrity checks (for example, commit/reveal alignment)

Then Bardiel applies oracle logic to:

• choose a result (for delegation flows)

• decide a verdict (for validation and arbitration flows)

• return structured output back into Virtual or ERC-8004 hosts:

{
  "status": "VALID | INVALID | RETRY | NEEDS_SPEC | SELLER_VALID | SELLER_INVALID | INCONCLUSIVE",
  "result": { /* chosen output, when applicable */ },
  "confidence": 0.0,
  "evidence": { /* summarized trust signals */ },
  "retry_instructions": "optional guidance"
}