Verun Protocol — Stellar

LIVE on Stellar Testnet   Deployed April 2026 · 4 API Endpoints · v0.1.0

Technical documentation for Verun Protocol — the AI Agent Trust ID for regulated European finance, designed to support MiFID II + EU AI Act audit obligations, built on Stellar by BCP Partners GmbH.

Overview

Verun is the trust infrastructure layer for AI agents operating in regulated European financial markets.

What is Verun?

As AI agents begin autonomously executing token transfers, minting securities, and placing investment orders, there is no existing standard for establishing who an agent is, whether it can be trusted, and whether it is permitted to act in a regulated context.

Verun solves this with the Verun Accredited Agent Score (0–1000): a consensus-based trust verdict issued by registered validators, anchored on Stellar for every evaluation, and enforced at the tokenforge Chain API gate.

Key Facts

3 Operating Modes

Architecture

Three complementary layers — Stellar for trust, tokenforge as the regulated gate, Stellar for settlement. No layer competes with another.

Layer Stack

Flow

Fee Distribution

Trust Score Gates

Every tokenforge Chain API capability is gated behind a minimum Trust Score. Scores are computed by validator consensus and anchored on Stellar.

Score Tiers

MiFID II + EU AI Act Alignment

Verun is designed to generate the machine-readable audit trail required by MiFID II Art. 17 (algorithmic trading governance) and the EU AI Act Art. 14 (high-risk-AI human oversight + logging) for agents acting in regulated European financial workflows.

Mapping per Article

Validator Model

Validators are the institutional backbone of Verun. They provide the consensus votes required for every agent evaluation.

Active Validators (Testnet)

Consensus Rules

A verdict requires ceil(N/2) matching votes from selected validators. With 3 validators: 2-of-3 required. UNAVAILABLE votes are excluded from the tally. If consensus cannot be reached, the evaluation returns BLOCK.

Validator Economics

Validators earn 10% of all evaluation fees automatically via the fee distribution contract. No manual claim required. Fee share scales with validation volume.

API Reference

Base URL: https://verun-stellar-mvp.vercel.app

GET /api/health

Service status and network confirmation.

{
  "ok": true,
  "service": "verun-stellar-mvp",
  "network": "stellar-testnet"
}

GET /api/validators

List all registered validators with metadata.

{
  "validators": [
    {
      "id": "val-bcp-01",
      "name": "BCP Partners",
      "type": "internal",
      "status": "active",
      "policy": "score_based"
    },
    {
      "id": "val-tokenforge-02",
      "name": "tokenforge",
      "type": "external",
      "status": "active",
      "policy": "chain_api_based",
      "api": {
        "type": "rest",
        "network": "testnet",
        "docs": "https://docs.tokenforge.io"
      }
    },
    {
      "id": "val-test-03",
      "name": "Test Validator",
      "type": "internal",
      "status": "test",
      "policy": "score_based"
    }
  ]
}

POST /api/evaluate

Evaluate an agent. Returns 2-of-N validator consensus verdict + Stellar on-chain anchor.

{
  "agentId": "agt_demo",
  "score": 820,
  "operation": "transfer",
  "validatorIds": ["val-bcp-01", "val-tokenforge-02", "val-test-03"]
}

{
  "success": true,
  "verdict": {
    "agentId": "agt_demo",
    "score": 820,
    "operation": "transfer",
    "validators_used": [
      { "id": "val-bcp-01", "name": "BCP Partners" },
      { "id": "val-tokenforge-02", "name": "tokenforge" },
      { "id": "val-test-03", "name": "Test Validator" }
    ],
    "votes": [
      { "validatorId": "val-bcp-01", "vote": "LOW", "reason": "score_800+", "source": "val-bcp-01" },
      { "validatorId": "val-tokenforge-02", "vote": "LOW", "reason": "chain_api_gate_passed_transfer:820>=500", "gate": { "permitted": true } },
      { "validatorId": "val-test-03", "vote": "LOW", "reason": "score_800+", "source": "val-test-03" }
    ],
    "tally": { "LOW": 3 },
    "consensus": "LOW",
    "permitted": true,
    "kickback_rate": 10,
    "ts": "2026-04-20T09:33:09.734Z"
  },
  "anchor": {
    "txid": "KBGSXMRXSM6P75RB6XHYT3RY6JNK7IGY6KIXWGXTVLRUEXPE6BZA",
    "ledger": "62604931",
    "explorer": "https://stellar.expert/explorer/testnet/tx/KBGSXMRXSM6P75RB6XHYT3RY6JNK7IGY6KIXWGXTVLRUEXPE6BZA"
  }
}

curl -X POST https://verun-stellar-mvp.vercel.app/api/evaluate \
  -H "Content-Type: application/json" \
  -d '{"agentId":"agt_demo","score":820,"operation":"transfer"}'

POST /api/score

Lightweight evaluation — verdict only, no Stellar anchor written. Use for quick checks where on-chain anchoring is not required.

{
  "agentId": "agt_demo",
  "score": 820,
  "operation": "transfer"
}

POST /api/mint-sbt

Issues a Soulbound Token credential to an agent, after running consensus. If consensus = BLOCK the request returns HTTP 403 and no SBT is minted. Full design + verification details on the Soulbound Token page.

POST /api/revoke-sbt

Kill-switch: clears the agent's vtrust_* manageData entry on the protocol account in a single Stellar transaction. Audit trail (the revoke TX) remains in horizon history. Used to satisfy MiFID II Art. 17 + EU AI Act Art. 14.

GET /api/sbt-status?agentId=…

Returns the current credential for an agent, or credentialed: false if not issued / revoked. Reads directly from the protocol account's on-chain data — no caching, no Verun-side state.

GET /api/sbt-list

Returns every active SBT issued by this protocol account. Useful for a public registry view — e.g. "all currently credentialed agents."

Stellar On-Chain Anchor

Every POST /api/evaluate writes the verdict payload as a Memo Transaction on Stellar Testnet — creating an immutable, timestamped audit trail.

How It Works

After validator consensus is reached, the Verun protocol wallet sends a self-payment of 1 stroop (0.0000001 XLM) with sha256(verdict) in the memo field (32-byte hash). The transaction is confirmed in ~5 seconds on Stellar.

Anchor Payload (note field)

{
  "agentId": "agt_demo",
  "score": 820,
  "operation": "transfer",
  "consensus": "LOW",
  "permitted": true,
  "validators": ["val-bcp-01", "val-tokenforge-02", "val-test-03"],
  "ts": "2026-04-20T09:33:09.734Z"
}

Verify On-Chain

Every anchor can be verified publicly on Stellar Expert:

https://stellar.expert/explorer/testnet/tx/{txid}

# Example live anchor:
https://stellar.expert/explorer/testnet/tx/KBGSXMRXSM6P75RB6XHYT3RY6JNK7IGY6KIXWGXTVLRUEXPE6BZA

Protocol Wallet

Soulbound Token (SBT)

LIVE on Stellar Testnet   mint · revoke · status · list — all four endpoints in production

Verun issues a non-transferable trust credential — the VTRUST SBT — to every agent that passes consensus. The credential is stored as a manageData entry on the protocol account, fully on-chain, publicly verifiable, and revocable in a single transaction.

Full architecture · Agent → Verun (3-step internal flow) → Consumer · Kill-switch · Money flow note

Wallet Architecture (Protocol-Custodial)

Verun's Stellar deployment uses a protocol-custodial model — a single responsible party is the issuer, agents do not hold private keys. This matches the Algorand MVP and aligns with EU AI Act Art. 14 (human oversight) + MiFID II Art. 17 (kill-switch).

How the credential lives on-chain

The SBT is not a Stellar asset in the traditional sense — it's a manageData entry on the protocol account. That means there is no asset balance, no trustline, no agent-side signature required. The "token" is a key-value pair stored permanently on the issuer's account.

Mint flow

// Request
{ "agentId": "agt_fahad_001", "score": 720, "operation": "transfer" }

// Response
{
  "success": true,
  "verdict_consensus": "MED",
  "agentId": "agt_fahad_001",
  "tier": "MED",
  "score": 720,
  "ts": "2026-04-30T14:40:53.913Z",
  "key": "vtrust_agt_fahad_001",
  "txid": "a6013d9d21ba6ab476b66410b87a8a5e3694866064d0af5e7131436df7871f5c",
  "ledger": "2310151",
  "credential_hash": "4f3aaa283c7cf13ff7427fd9560b49314baaf40bf790efb78cc4e3e00a45ea6d",
  "issuer": "GD2CGWE3LVWN6DQCNVMFWPGNP42FXQ66MLRXFUHSTCR3OUVHFJBYFTHW",
  "explorer": "https://stellar.expert/explorer/testnet/tx/a6013d9d...",
  "verify_url": "https://horizon-testnet.stellar.org/accounts/GD2CGW.../data/vtrust_agt_fahad_001"
}

The endpoint runs validator consensus first. If consensus = BLOCK, no SBT is issued — the operation gate is enforced before mint. One transaction includes both the manageData op and the anchor self-payment.

Revoke flow (kill-switch)

// Request
{ "agentId": "agt_fahad_001", "reason": "policy_violation" }

// Response
{
  "success": true,
  "revoked": true,
  "agentId": "agt_fahad_001",
  "key": "vtrust_agt_fahad_001",
  "reason": "policy_violation",
  "txid": "...",
  "ledger": "...",
  "revoke_hash": "...",
  "explorer": "https://stellar.expert/explorer/testnet/tx/..."
}

Revocation = manageData with value = null. The entry is removed from the issuer's account state in a single transaction (~5 seconds). The revoke transaction itself remains in horizon history forever — the audit trail is not erased.

Public verification (zero-auth)

Anyone — tokenforge, an auditor, a regulator — can verify the credential directly against Stellar Horizon. No Verun API call required.

curl https://horizon-testnet.stellar.org/accounts/GD2CGWE3.../data/vtrust_agt_fahad_001

# Active credential:
{ "value": "TUVEOjcyMDoyMDI2LTA0LTMwVDE0OjQwOjUzLjkxM1o=" }
# (base64 decode → "MED:720:2026-04-30T14:40:53.913Z")

# Revoked credential:
HTTP 404 Not Found

Endpoint summary

End-to-end demo (one command)

git clone https://github.com/Fahad00674/verun-stellar-mvp
cd verun-stellar-mvp && chmod +x scripts/sbt-demo.sh
./scripts/sbt-demo.sh agt_fahad_001 720

Runs the full lifecycle: status check → mint → public verification → revoke (kill-switch) → re-verification. Two real testnet transactions, ~25 seconds total.

Compliance mapping

Mainnet Roadmap

From Stellar Testnet MVP to production infrastructure with legal-audited MiFID II + EU AI Act alignment.

For Agents

Everything an AI agent needs to connect to Verun Network and get a trust verdict on Stellar — in under 60 seconds.

Step 1 — Add the System Prompt

Paste this into your agent's system instructions. It tells the agent when and how to call Verun before executing any financial operation.

You are an AI agent operating within the Verun Network trust framework on Stellar.

Before executing any financial operation, request a Verun trust evaluation.

== HOW TO EVALUATE ==
POST https://verun-stellar-mvp.vercel.app/api/evaluate
Body: { "agentId": "YOUR_AGENT_ID", "score": YOUR_SCORE, "operation": "transfer" }

== OPERATION GATES ==
read        → score 300+
transfer    → score 500+
order       → score 600+

== VERDICT RULES ==
permitted: true   → proceed with the operation
permitted: false  → stop, escalate to human supervisor
Always store the returned txid as your on-chain audit trail.

== HUMAN ESCALATION ==
If verdict is denied or pending, notify the human supervisor.
Never execute financial operations without a valid Verun verdict.

Network: Stellar Testnet
Validators: tokenforge · BCP Partners
Docs: https://verun-stellar-mvp.vercel.app/docs.html

Step 2 — Make the API Call

Your agent calls /api/evaluate before any operation. Replace YOUR_AGENT_ID with your agent's identifier.

Step 3 — Read the Verdict

Verun returns a verdict with an Stellar TXID as immutable proof.

Operation Reference

x402 Sequence Diagram — Stellar

Complete message flow between AI Agent, Verun Protocol, GoPlausible x402 Facilitator, and Stellar Network — including error paths.