Architecture

One hop between agents and financial infrastructure.

ValarIQ doesn't move the money. It controls whether the agent is authorised to ask someone else to.

System diagram

Agent → ValarIQ → Financial infrastructure.

AI AGENT
    │
    ▼
VALARIQ
  Identity → Authority → Policy → Risk → ALLOW / ESCALATE / DENY → Evidence
    │
    ▼
FINANCIAL INFRASTRUCTURE
  Stripe / PSP / Bank / Ledger

ValarIQ evaluates every financial action at the execution boundary. Approved actions proceed to your existing payment processor, banking API, or ledger. Denied actions never reach infrastructure. Escalated actions wait for human authorisation.

Integration positioning

ValarIQ complements — not competes with — your payment stack.

+ Stripe

ValarIQ + Stripe — govern agent-initiated refunds and payments before they reach Stripe APIs.

+ Visa

ValarIQ + Visa — policy enforcement at the agent boundary, not a replacement for scheme connectivity.

+ Mastercard

ValarIQ + Mastercard — complementary control layer for agent-driven payment operations.

Fail-closed architecture

If ValarIQ is unavailable, high-risk money movement stops.

The control plane is designed to fail closed. When identity cannot be verified, authority cannot be confirmed, or policy cannot be evaluated, the default outcome is deny — not proceed. Configurable resilience options exist for institutions that cannot accept a single point of failure, but the product default protects against silent bypass.

Unverified agent identity → DENY
Authority profile expired or revoked → DENY
Policy engine unreachable → DENY (configurable)
Approval timeout without decision → DENY (configurable)
Observe mode → log and evaluate without blocking production

Resilience roadmap (enterprise)

Fail-closed raises a fair question: is ValarIQ a single point of failure? The answer must cover HA, regional failover, cached policy, emergency policy, circuit breakers, RTO/RPO, latency SLO, decision timeout, and degraded mode. These are design-partner and enterprise workstreams — not all shipped today — and are discussed openly in diligence rather than hidden.

Integration pattern

REST · SDK · MCP

One hop CTOs immediately understand. Wire ValarIQ into your agent runtime via the interface that fits your stack.

REST

HTTP API for verify, authorize, and approval polling. Drop into any agent runtime or middleware.

SDK

Typed client libraries for Node.js and other runtimes. Wraps certificate handling and decision polling.

MCP

Model Context Protocol server so LLM agents call ValarIQ as a tool — identity and policy enforced at invocation.

Technical reference: /docs

Control whether agents may act — not how money moves.

Read the API docs Architecture review