Mission

Bardiel is a Virtual-native service agent created for one purpose:

Give every agent an easy way to ask: “Can I trust this?”

Most agents focus on producing outputs. Bardiel focuses on delegating, validating, and arbitrating those outputs – using Cortensor as its decentralized compute and proof backend, and exposing everything through Virtual-first surfaces (and, over time, ERC-8004).

---

Vision

Our long-term vision:

Bardiel becomes the default trust and execution oracle for agent economies.

Concretely, that means:

• Any Virtual agent can call Bardiel when it needs:

  • high-trust execution (Delegation-as-a-Service)

  • a second opinion on a result (Validation-as-a-Service)

  • an optional neutral decision in a dispute (Arbitration-as-a-Service, where the host market chooses to use it)

• ERC-8004 agents can treat Bardiel as:

  • a registered validator for task results

  • a shared dispute oracle wired into escrow/settlement flows

• Bardiel is quiet when things go right, and reliable when something feels off:

  • low-quality or hallucinated outputs are caught early

  • dishonest or lazy behavior becomes detectable and provable

  • disputes are resolved with evidence, not vibes

Over time, Bardiel becomes data-informed:

• learning better validation rules from real agent traffic

• tuning policies and thresholds instead of staying static

• improving guarantees as Virtual and Cortensor usage grows

Cortensor focuses on running models and proving work. Bardiel focuses on turning those proofs into decisions agents can depend on.

---

Mission

Our mission with Bardiel is to make trust and reliable execution first-class building blocks for agents.

1. Make “Can I trust this?” a first-class API

Every agent should have a simple way to say:

• “Run this task on reliable infrastructure.”

• “Check this result before I act on it.”

• “Help me resolve this disagreement fairly.”

Bardiel exposes this as a small set of surfaces:

• For Virtual (GAME / ACP):

  • delegate_to_bardiel(task, policy)

  • validate_with_bardiel(task, claimed_result, policy)

  • optional arbitration flows where ACP or both parties want an extra oracle

• For ERC-8004:

  • delegation and validation endpoints wired through x402/MCP

  • validator / oracle roles registered in the 8004 registry

The goal is that “we routed it through Bardiel” becomes a meaningful API-level guarantee.

---

2. Turn Cortensor’s signals into clear verdicts

Cortensor provides:

• redundant inference from miners

• PoI / PoUW and other validation signals

• reputation, integrity, and SLA data

Bardiel’s job is to:

• choose how to call Cortensor (models, redundancy, tiers)

• combine proofs with schemas, specs, and safety policies

• return clear, structured outcomes, such as:

• VALID, INVALID, RETRY, NEEDS_SPEC for everyday validation

• SELLER_VALID, SELLER_INVALID, INCONCLUSIVE for dispute/arbitration flows

always with:

• a confidence score, and

• a summarized evidence trail that agents and markets can reason about.

---

3. Protect users and markets, not just infrastructure

Bardiel is designed around user-level and market-level safety, not just network health:

• catch subtle failures and hallucinations before they propagate

• enforce constraints and specs in ACP-style markets and ERC-8004 jobs

• act as a neutral oracle that buyers, sellers, and marketplaces can appeal to

The goal is that agents using Bardiel:

• make fewer silent mistakes,

• resolve more disagreements with data instead of drama, and

• unlock higher-value, longer-horizon tasks with confidence.

---

4. Respect the boundary between Virtual, Bardiel, and Cortensor

We keep responsibilities clean:

• Virtual

  • agents, tools, workflows (GAME)

  • markets and settlement (ACP and launchpad)

  • Bardiel as a first-class service agent inside this ecosystem

• Cortensor

  • decentralized inference and compute

  • PoI / PoUW and proof rails

  • Router, miners, validators, and network economics

• Bardiel

  • decides how to use Cortensor on behalf of agents

  • interprets low-level signals into high-level verdicts and policies

  • exposes Virtual-first and ERC-8004-ready interfaces

  • never pretends to be a separate network or L1/L2/L3

Short version:

Cortensor: execute and prove. Bardiel: interpret, verify, and decide. Virtual: orchestrate and build on top.

---

5. Evolve based on real agent data

Bardiel is intentionally not “finished” by design.

We will:

• use testnet and mainnet traffic to refine scoring and validation templates

• experiment with tooling surfaces (web access, spec helpers, safety checks) for Delegation

• expose metrics and telemetry so builders can understand how Bardiel behaves

• iterate on tiers (Fast / Safe / Oracle / Adaptive) as we see real workloads across Virtual and ERC-8004

The more agents use Bardiel, the better Bardiel should become at protecting them and their users.

---

For Builders

If you are building on Virtual or ERC-8004:

• you should not have to invent your own trust system from scratch

• you should be able to:

  • call Bardiel for delegation when you need reliable, tool-aware compute

  • call Bardiel for validation when you’re unsure about a result or planned action

  • rely on Bardiel (where appropriate) for arbitration when markets need a neutral judge

The rest of this documentation explains how Bardiel works, how it integrates with Virtual and Cortensor, and how to plug it into your agents and applications.