For the complete documentation index, see llms.txt. This page is also available as Markdown.

Payments

x402 Facilitator

The AWE x402 Facilitator helps applications verify and settle programmatic payments between buyers and sellers.

x402 is an open payment standard built around the HTTP 402 Payment Required status code. It allows APIs, applications and agent services to charge for individual requests without requiring subscriptions or manual payment flows.

How an x402 payment works

  1. A buyer requests a protected resource.

  2. The server responds with 402 Payment Required and provides payment instructions.

  3. The buyer prepares a payment authorization and submits it with the request.

  4. The facilitator verifies the authorization and settles the payment onchain.

  5. Once the payment is confirmed, the server provides the requested resource.

Why use a facilitator?

Applications can verify and settle x402 payments independently. A facilitator provides this functionality as a service, reducing the blockchain infrastructure that each developer needs to operate.

The AWE Facilitator provides standard endpoints for:

  • Verification — Confirm that a payment authorization is valid.

  • Settlement — Submit the authorized payment onchain.

  • Status handling — Return the result to the application so it can provide the requested resource.

Current support

The AWE Facilitator currently supports fee-free USDC payments on Base, allowing sellers to receive the full payment amount without an additional facilitator fee. Standard network costs may still apply.

What builders can monetize

The facilitator can support payments for:

  • API requests

  • AI inference

  • MCP tools

  • Agent services

  • Digital content

  • Usage-based applications

AWEtoAgent Kit provides a higher-level framework for adding x402 payments to agent applications.

Last updated