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.
AUTONOMOUS ACTOR
→ INTENT → ACTION PLAN
→ IDENTITY / DELEGATION → AUTHORITY GRAPH → POLICY
→ EVIDENCE / CONTRADICTIONS → DECISION
→ SHORT-LIVED EXECUTION AUTHORISATION
→ YOUR EXECUTION SYSTEMS (PSP / ERP / WORKFLOW)
→ EXECUTION CONFIRMATION → DECISION LEDGERValarIQ 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, rather than competes with, your payment stack.
+ Stripe
ValarIQ + Stripe: you keep Stripe execution; ValarIQ decides whether the Agent may call it. Worked integration examples available to design partners.
+ 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.
Illustrative stack positioning only, not an implied partnership unless separately agreed.
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
Enterprise resilience
Enterprise resilience capabilities are being developed with design partners, including high availability, regional failover, policy continuity and configurable degraded-mode behaviour. Exact current-state capabilities are disclosed during technical diligence.
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: POST /api/v1/decisions and approval polling. Drop into any agent runtime or middleware.
SDK
Node gateway client (@valariq/gateway) with wrapTool gates Financial Actions before execution.
MCP
Control adapter for tool-list filtering and tool-call authorisation. Not a full MCP host. Staging foundation; production COMING until a controlled release.
Technical reference: /docs