HTTP payments · x402
Charge USDC for an HTTP resource: the server communicates requirements, the client authorizes, and the facilitator verifies and settles.
A separate API
The facilitator runs as an OpenZeppelin Relayer plugin. Its supported, verify and settle routes and credentials are separate from TilcAI's. The SDK exposes Paywall, X402Facilitator and x402Fetch under tilcai-sdk/x402.
import { Paywall, X402Facilitator, x402Fetch } from "tilcai-sdk/x402";
// Server-side integration building blocks.
// Configure facilitator credentials and payment requirements
// before protecting or paying for a real resource.Status and checks
The SDK implementation, network configuration and isolated rail tests exist. The Monad log confirms plugin configuration, not an end-to-end x402 test on that network. Query facilitator supported and validate each asset, network and mode. Do not describe x402 mainnet as proven by CCTP.
Responses and uncertainty
HTTP 200 may contain isValid:false or success:false: read the body. A settle 504 may occur after submission; reconcile the hash before signing a new payload. CCTP moves USDC across networks; x402 pays for an HTTP resource. These are different flows.
Availability depends on your instance. Check /health and /v1/routes before integrating.