[ x402 facilitator — payer risk scanning built in ]

VAPOR verifies and settles x402 stablecoin payments over EIP-3009 — same protocol, zero facilitator fees — but every payer is scored before settlement, not after. Everything below is live, straight from the running facilitator.

See it live Read the API docs

> Live activity

Verify and settlement requests, last 24 hours — real timestamps, no simulated data.

uptime —
verify— settle— success— volume— avg-risk— networks—

> Payer risk distribution

Every payer scanned before settlement — on-chain heuristics plus an optional reputation signal.

> How the score is built

on-chain Wallet age, transaction history, contract-vs-EOA — pulled straight from the chain, no third-party dependency required.
reputation Optional and additive. Plug in any provider speaking VAPOR's small generic contract — degrades gracefully to on-chain-only if unset.
policy Your policy decides, not VAPOR. Every payee sets its own max risk score, amount bounds, and deny list.
Full scoring methodology →

> Built for machine-speed commerce

Everything a standard facilitator does, plus what agent-to-agent payments actually need.

Payer risk scanner

Every payment scored before it settles, not after — the core of what makes VAPOR different.

Configurable policies

Per-payee max risk score, amount bounds, and deny lists — your rules, evaluated on VAPOR's scan.

Audit-grade logging

Every decision recorded and exportable as JSON or CSV — a real compliance trail, not an afterthought.

Webhook events

HMAC-signed payment.verified / settled / denied events to your own endpoint.

Zero facilitator fees

VAPOR doesn't take a cut of settled payments. Full stop.

Multi-chain ready

Network and token config is data-driven — adding a chain means adding a verified entry, not rewriting the pipeline.

x402 Bazaar-compatible discovery

Register/list your own resources through VAPOR's own discovery endpoint — no dependence on another facilitator's catalog.

> How a payment moves through VAPOR

01
Verify

Scheme, amount, time window, and EIP-712 signature checked against VAPOR's own verified network config.

02
Scan

The payer is scored — on-chain heuristics, plus a reputation signal if one's configured.

03
Decide

The payee's own policy evaluates the score against its configured thresholds and deny list.

04
Settle

Re-verified against live chain state, then broadcast via transferWithAuthorization.

> Quickstart

Any x402 resource server can point at VAPOR with no protocol changes.

curl https://your-vapor-instance/supported

curl -X POST https://your-vapor-instance/verify \
  -H "Content-Type: application/json" \
  -d '{
    "x402Version": 1,
    "paymentPayload": { "...": "the client-signed EIP-3009 authorization" },
    "paymentRequirements": { "...": "your resource'"'"'s price and payTo address" }
  }'

Full request/response shapes, policy overrides, and webhook contract: docs/API.md.