Why Veridex
Overview

Why Veridex

Veridex is the platform for bounded financial authority. It provides the infrastructure for applications and AI agents to execute on-chain actions within explicit limits, with full governance and audit trails.

The Problem

Modern applications β€” especially those powered by AI agents β€” need to execute financial transactions autonomously. But unrestricted autonomy is unacceptable for real-world deployments:

  • Developers need fast integration, clear session management, and predictable execution.
  • Operators need policy controls, approval workflows, incident response, and evidence for audit.
  • Neither is well-served by existing wallet infrastructure that assumes a single human signer.

The Veridex Model

Veridex introduces a layered authority model that separates identification, delegation, governance, and evidence:

LayerWhat It DoesWho Uses It
API KeysIdentify applications to the platformDevelopers
Session KeysDelegate bounded authority to softwareDevelopers & Agents
Governed ExecutionEnforce policies on every actionOperators
Audit EvidenceProduce verifiable traces per executionOperators & Compliance

Key Capabilities

For Developers (Build)

  • Multi-session keys: Create, list, select, rotate, and revoke multiple concurrent sessions per identity
  • Cross-chain execution: Base, Optimism, Arbitrum, Solana, Aptos, Sui, Starknet, Stacks
  • Agent SDKs: First-class support for AI agents with session inventory and MCP tools
  • Session Studio: Visual management of app sessions and agent sessions

For Operators (Operate)

  • Approval Inbox: Review and decide on pending actions before execution
  • Policy Packs: Configure spending limits, chain restrictions, approval thresholds, counterparty rules
  • Incident Log: Track and investigate security or policy violations
  • Trace Explorer: Step-by-step execution history with reasoning, verdicts, and signatures
  • Evidence Export: JSON and CSV bundles for audit and compliance review

Architecture

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚            Developer Platform               β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”  β”‚
β”‚  β”‚    Build     β”‚  β”‚      Operate         β”‚  β”‚
β”‚  β”‚  β€’ API Keys  β”‚  β”‚  β€’ Approvals         β”‚  β”‚
β”‚  β”‚  β€’ Sessions  β”‚  β”‚  β€’ Policies          β”‚  β”‚
β”‚  β”‚  β€’ Agents    β”‚  β”‚  β€’ Incidents          β”‚  β”‚
β”‚  β”‚  β€’ Activity  β”‚  β”‚  β€’ Traces            β”‚  β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜  β”‚  β€’ Evidence           β”‚  β”‚
β”‚                    β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜  β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚             Relayer + Governance             β”‚
β”‚  API key auth β€’ Session lifecycle            β”‚
β”‚  Approval queue β€’ Trace storage              β”‚
β”‚  Incident recording β€’ Evidence export        β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚           On-Chain Contracts                 β”‚
β”‚  VeridexHub β€’ Session[] per identity         β”‚
β”‚  Multi-chain deployment                      β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Next Steps