Verify
Validate payment payloads, payer binding, network, asset, amount, expiry, authorization context, and replay protection.
Built into the API →
Enterprise x402 infrastructure
The trust layer for agentic payments.
Verify, settle, recover, and govern x402 payments for AI agents, APIs, devices, and fleets—with enterprise policy binding and direct merchant settlement.
NoncustodialUSDC on Basex402 V2ModelGlue-ready
live transactionchecking
01
Authorization receivedMission and policy context bound
12 ms02
Payment verifiedUSDC · Base · replay-safe
44 ms03
Settlement submittedDirect to merchant destination
pendingpayment_idx402_8f31…c942authorizationmg_auth_7219recoveryenabledx402 V2Protocol ready
BaseInitial network
USDCSettlement asset
24/7Recovery lookup
Core infrastructure
Infrastructure for payments that cannot afford ambiguity.
A narrow facilitator layer with explicit states, deterministic recovery, replay protection, and clean separation from enterprise governance.
Settle
Submit approved payments through a dedicated signer boundary while merchants receive funds directly.
Built into the API →Recover
Look up payment state by payment ID or authorization nonce before retrying an interrupted request.
Built into the API →Clean separation of concerns
ModelGlue governs. x402Facilitator executes.
Keep enterprise identity, policy, approvals, budgets, and commerce intelligence in ModelGlue while the facilitator stays focused on verification, settlement, health, and recovery.
- ModelGlue evaluates identity, policy, budgets and approvals.
- x402Facilitator verifies and submits authorized payments.
- Funds move directly to the merchant destination.
- Every payment remains recoverable and auditable.
Agent / DeviceRequests service
↓ModelGlue.aiAuthorize + govern
↓x402Facilitator.aiVerify + settle
↓MerchantDeliver + receive
One recoverable flow
From service request to verified delivery.
Every stage has a clear status, durable identifier, and auditable transition.
01DiscoverFind an approved paid service.
02AuthorizeBind mission, policy, amount, and nonce.
03VerifyValidate the x402 payment payload.
04SettleSubmit through the signer boundary.
05RecoverResume safely after interruption.
Developer first
Simple endpoints. Serious controls.
Start in sandbox, integrate verification and status lookup, then connect your signer boundary only when production settlement is ready.
Explore all endpoints →POST /wp-json/x402facilitator/v1/verify
{
"payment_id": "x402_8f31c942",
"network": "base",
"asset": "USDC",
"authorization_nonce": "mg_7219"
}
200 OK · verified · replay_safeReady when you are
Read the API documentation→Start in sandbox. Go live deliberately.
Test verification, status, and recovery before enabling production settlement.