VERIMANDTHE AUTHORITY LAYER FOR AUTONOMOUS AI
Explore VAGP View on GitHub

BUILD WITH AUTHORITY

Integrate Verimand
into your AI stack.

Use the public VAGP 0.3 specification, schemas, vectors and conformance assets today. The Verimand MCP Authority Server is publicly available for agent-native authority tooling.

View GitHubRead specification

VAGP 0.3 PUBLIC · MCP AUTHORITY SERVER AVAILABLE

AUTHORITY TOOLSAVAILABLE NOW
A current mandate for this exact action.

One protocol. Multiple ways to integrate.

Choose the interface that fits your use case. All interfaces are designed around VAGP
and the same deterministic authority boundaries.

PLANNED

REST API

For systems and applications. A system interface for authority decisions and explanations.

View API example
AVAILABLE NOW

MCP Server

For AI agents and MCP clients. Six public authority tools through the official MCP Registry and npm package.

Explore MCP

Available now: public VAGP 0.3 resources and the Verimand MCP Authority Server. Planned / in development: supported Verimand SDK, REST authority interfaces, MCP Authority Gateway and protected-tool execution enforcement. Public /v1 remains VAGP 0.2.

AVAILABLE NOW

Public VAGP 0.3 developer resources.

The open protocol package is public under Apache-2.0. Implementing VAGP does not require buying Verimand or using Verimand product infrastructure.

Specification ↗Schemas ↗Crypto profile ↗Vectors ↗Conformance assets ↗Independent Go reference ↗MCP Registry listing ↗npm package ↗MCP GitHub repository ↗

Connect via MCP.
VAGP governs authority.

MCP exposes capability. VAGP governs authority. The public MCP Authority Server lets MCP clients resolve and inspect authority; it does not intercept protected tool execution.

Install / startnpx -y @verimand/mcp-authority-server@0.1.0
MCP Registry ↗npm ↗GitHub ↗

AI Agent / MCP Client

Requests authority context through MCP

Verimand MCP Authority Server

Exposes six authority tools

VAGP Authority

Deterministic authority evaluation

PERMIT / DENY

Decision and explanation returned

AVAILABLE
  • verimand.resolve
  • verimand.explain
  • verimand.get_authority
  • verimand.get_mandate
  • verimand.get_agent_dna
  • verimand.verify_permit
FUTURE
  • MCP Authority Gateway
  • Protected-tool execution enforcement

Current MCP functionality provides authority resolution, explanation and inspection tools. The Authority Gateway and automatic enforcement before protected tool execution remain future work.

Verimand MCP Authority GatewayFUTURE

The future gateway enforces authority before protected tool execution. A missing mandate returns NO_AUTHORITY; only successful binding and resource-side verification can lead to a single-use execution permit.

  1. Agent
  2. MCP
  3. Authority Gateway
  4. VAGP Resolve
  5. Reject / verify & permit
  6. Protected tool
Inspect the enforcement architecture →

Agent interoperability with separate authority.

Verimand complements A2A rather than replacing it. A2A moves tasks between agents; VAGP decides whether the receiving agent has delegated authority to execute through a protected boundary.

Agent A↓ A2AAgent B↓ Verimand / VAGPPERMIT / DENY↓Protected MCP Tool
MCP: agent -> tools
A2A: agent -> agent
VAGP: authority

A2A-01 tested official A2A 1.0 task delegation, bounded delegated authority, multi-hop attenuation, Agent Card metadata, revocation and replay. A2A task receipt and Agent Card declarations do not themselves create authority.

Inspect A2A validation →

Current status: validated authority semantics with A2A 1.0. Not a public Verimand A2A package, production A2A Gateway or customer deployment claim.

IDENTITY / MULTICLOUD

Bring your identity. Keep one authority model.

Identity provider → trusted identity binding → VAGP authority. Provider identity must not itself grant authority. Identity establishes who the agent is; Verimand governs what it is authorized to do.

Inspect validation evidence →
REAL VALIDATEDGoogle Workload Identity Federation

Validated through the provider-neutral identity seam.

REAL SVID ISSUANCE VALIDATEDSPIFFE/SPIRE

Gateway verifier integration is not yet fully validated.

NOT YET VALIDATEDMicrosoft Entra Agent ID

Blocked on the blueprint credential/token path.

ILLUSTRATIVE
# Future API sketch — not a released endpoint
curl -X POST https://authority.example.invalid/resolve \
  -H 'Content-Type: application/json' \
  -d '{
    "agent": "agent_123",
    "action": "execute_payment",
    "resource": "account_456",
    "context": { "amount": 12500, "currency": "EUR" }
  }'

Design illustration, not a public wire contract. The .invalid host is intentionally non-routable. Public /v1 remains VAGP 0.2.

Simple to integrate.
Powerful by design.

The intended developer experience is a small, explicit integration: describe the request, resolve authority and enforce the result at the protected boundary.

Examples show future Verimand interface direction. They do not execute requests or publish a Verimand 0.3 API contract. The public VAGP 0.3 protocol assets are available now.

Explore working simulations

Start at the authority boundary.

Understand the reference implementation, then define identity, trusted Agent DNA, mandates and the protected action.

Agent DNA & attestation↗Protocol specification↗Conformance & test vectors↗Interactive authority playground↗
Current implementation and interface availability

VAGP 0.3 public assets are available now: specification, schemas, crypto profile, vectors, conformance assets and an independent Go reference implementation. The Verimand MCP Authority Server is also public with six authority tools. Planned / in development: supported Verimand SDK, REST authority interfaces, MCP Authority Gateway and protected-tool execution enforcement.

The Verimand implementation and independent clean-room Go reference both pass the same CF-01 Core black-box conformance suite: 81/81 required checks. This is conformance evidence, not external certification.

Read versioned evidence →

Build what’s next.
With authority.

Join the developer ecosystem building safer autonomous systems.

Explore VAGPJoin the conversation