Available on npm, PyPI & Cargo

Private InfrastructureFor Autonomous Agents

Unified x402 + MPP payments — your agent spends privately.
Per-request or session-based. Policy-controlled. Strategy hidden.

Get Started

How Veil402 Works

Three layers of private financial infrastructure

Deposit & Configure

Deposit stablecoin into a pooled vault. Create agent identities, assign spending policies with daily limits, per-request caps, and merchant allowlists.

Agent Pays Privately

x402 for one-off API calls, MPP sessions for streaming data. Either way — Veil402 evaluates the policy and the pooled identity pays, not your wallet.

Encrypted Audit Trail

Every transaction is encrypted with AES-256-GCM. Only you can decrypt. Revoke agent credentials instantly. Full control, full privacy.

Agent

→

402

→

Veil402

→

Policy

→

Settlement

→

Merchant

→

Data

Built for Serious Agents

Policy Engine

14-step deterministic evaluation. Daily limits, per-request caps, merchant allowlists, endpoint restrictions, rate limiting.

Pooled Settlement

Merchants see Veil402's identity, not yours. Reduced on-chain linkability between owner and agent purchases.

Instant Revocation

Credential propagation in under 100ms. One click to cut off any agent immediately.

Double-Entry Ledger

Every transaction balances to zero. Six account types. Atomic reservations with capture/release.

Human-in-the-Loop

Set approval thresholds. Purchases above your limit require manual approval from the dashboard.

x402 + MPP

Both protocols, one proxy. Per-request x402 for one-off calls. Session-based MPP for streaming micropayments. Unified policy control.

Two Protocols. One Privacy Layer.

Veil402 is the only private payment proxy supporting both x402 and MPP under unified policy control.

x402

Per-Request Payments

Agent hits a 402 paywall → Veil402 authorizes → pooled identity pays → merchant delivers data. One request, one payment.

HTTP-native — works with any x402 merchant
~50ms overhead per request
On-chain settlement per transaction
Best for: API calls, data purchases, one-off queries

MPP NEW

Session-Based Streaming

Agent opens a session with a spend limit → streams hundreds of micropayments → settles once at close. Like OAuth for money.

Pre-authorized spend limit per session
Near-zero latency after session start
Batched on-chain settlement at close
Best for: streaming data, high-frequency APIs, real-time feeds

1Create SessionSet spend limit & TTL

→

2Stream PaymentsMicropay per request

→

3Settle & CloseBatch settle on-chain

Drop-In SDKs

x402 works like fetch. MPP sessions for streaming. Both private.

import { Veil402 } from '@veil402/sdk';const agent = new Veil402({credential: process.env.VEIL402_CREDENTIAL,});// x402 — per-request paymentsconst res = await agent.fetch('https://api.example.com/market-data');// MPP — session-based streamingconst session = await agent.createSession('https://api.example.com',{ spendLimit: '5000000' } // 5 USDC);for (let i = 0; i < 100; i++) {await agent.sessionFetch(session,'https://api.example.com/tick');}await agent.closeSession(session.id);

npm install @veil402/sdk

Honest Privacy

We tell you exactly what Veil402 protects and what it doesn't.

What Veil402 Protects

Privacy from public blockchain observers
Reduced linkability between owner and purchases
Private internal agent balances and policies
Encrypted receipts and audit trail
Instant credential revocation

What Veil402 Does NOT Protect

Absolute anonymity (we reduce linkability, not guarantee it)
Privacy from Veil402 infrastructure (MVP is partially custodial)
Privacy from the merchant receiving the request
Timing correlation attacks (mitigated by pooling, not eliminated)
Network-level observation (use a proxy for IP privacy)