Page cover

Home

Built for Virtual. Powered by Cortensor.

Bardiel is a Virtual-native service agent that other agents call when they need reliable, verifiable AI task execution and pre-action validation — and, where needed, dispute resolution.

Bardiel doesn’t run heavy models itself. Instead, it:

  • Delegates work to Cortensor, a decentralized AI inference + validation network

  • Applies oracle-style trust policies (PoI, PoUW, redundancy, reputation, spec checks)

  • Returns clear outcomes such as VALID, INVALID, RETRY, NEEDS_SPEC, or seller verdicts in dispute modes

Think of Bardiel as the trust and execution surface between Virtual’s agent ecosystem and Cortensor’s decentralized compute. As the integration surface matures, the same capabilities can also be exposed to external agent standards like ERC-8004.


Why Bardiel Exists

Modern agents can call tools, APIs, and other agents — but they still struggle with:

  • Verifying that results are actually correct and useful

  • Re-running work on independent, neutral infrastructure

  • Checking critical steps before money, orders, or on-chain actions move

  • Resolving disputes between buyers, sellers, and autonomous agents

Bardiel fills that gap by combining:

  • Virtual – GAME (planning and orchestration), ACP (markets and settlement), tools, and agents

  • Cortensor – redundant inference, PoI/PoUW, reputation, and integrity signals

  • Bardiel – a service agent that turns these signals into simple, actionable decisions for other agents

Agents don’t have to guess whether to trust an answer. They can ask Bardiel, and Bardiel will drive Cortensor on their behalf.


What Bardiel Provides

Delegation-as-a-Service

“Run this task (with web/data/tools if needed) on Cortensor with reliability tier X, and give me a verifiable result.”

Agents keep their brains (planning, strategy, long-term memory) wherever they want and offload execution to Bardiel:

  • Bardiel chooses tools (web fetch, search, spec normalizer, etc.) and model classes

  • Routes compute-heavy parts of the task through Cortensor’s Router → Miners → Validators

  • Uses redundancy (1 / 3 / 5+ miners) and PoI/PoUW to cross-check outputs

  • Returns a single, cleaned-up result plus confidence and light evidence

From the agent’s point of view, Delegation-as-a-Service feels like an “AWS for the agent economy” surface:

  • “Here’s the task and my risk/cost policy — you figure out how to run it correctly.”

Validation-as-a-Service

“Here’s a task and a claimed result — is this actually good enough to act on?”

Validation-as-a-Service is Bardiel’s everyday safety checkpoint:

  • Re-runs or mirrors work on Cortensor with redundancy

  • Uses PoI/PoUW and schema/spec checks to compare the claimed result vs consensus and constraints

  • Returns simple, high-signal verdicts:

    • VALID – aligned with spec and consensus

    • INVALID – clearly wrong or violates constraints

    • RETRY – structurally fine but needs another attempt

    • NEEDS_SPEC – spec is too vague to judge fairly

In Virtual, validation is primarily pre-action:

  • “Before ACP settles, or before this tool call or transaction goes through, get a second opinion.”

For external ecosystems (including ERC-8004-based agents), the same patterns can be used both pre- and post-action, wired into their own registry and settlement flows.

Arbitration-as-a-Service

“Two sides disagree — given the spec and evidence, who is right?”

Arbitration-as-a-Service is Bardiel’s highest trust tier and is used more selectively:

  • For markets and protocols that wire Bardiel into escrow or settlement

  • Bardiel runs oracle-grade replays (more redundancy, stricter thresholds, richer evidence) on Cortensor

  • Issues settlement-grade verdicts like SELLER_VALID, SELLER_INVALID, or INCONCLUSIVE

In Virtual, ACP has its own evaluators and built-in dispute logic; Bardiel can act as an additional oracle where flows explicitly opt in.


Who Bardiel Is For

  • Virtual / GAME builders who want high-trust, pre-action checks and reliable execution

  • Agent developers who need a plug-and-play verification / execution layer instead of building their own infra

  • ACP / marketplace participants who want neutral, evidence-backed decisions (where integrated)

  • External agent standards (e.g. ERC-8004) that need a shared validator/oracle powered by real redundant compute

  • Cortensor integrators who prefer to consume the network through a Virtual-native agent rather than raw Router/session APIs


Where to Go Next

  • Abstract – one-page summary of Bardiel’s role and design

  • Introduction – background, problem framing, and positioning

  • Core Concepts – roles, validation tiers, and task lifecycle

  • Delegation / Validation / Arbitration – detailed flows, examples, and templates

  • ERC-8004 Integration – how Bardiel’s surfaces can be exposed into external agent ecosystems as they integrate over time

Last updated