Skip to main content

Merchant Introduction

Learn how to monetize your APIs and services with x402 on bex.co

Share
Last updated on August 19, 2026

Learn how to sell services with x402 on bex.co

Monetize Your API with x402

x402 enables you to monetize HTTP APIs and content with on-chain payments while maintaining your existing infrastructure. bex.co provides enterprise-grade x402 facilitator services with Sui-first, multi-network support.

Key Benefits

  • Zero network fees for merchants and customers
  • Sub-second payment settlement on Sui blockchain
  • Multi-network support: Sui, Ethereum, Base, Polygon, Avalanche, and more
  • Universal compatibility with any HTTP-capable service
  • Enterprise reliability: 99.9% uptime SLA

Architecture Overview

The x402 protocol enables seamless HTTP-native payments with four key components:

System Components

  • Client: Initiates requests to protected resources and submits on-chain payments
  • Server (Merchant): Your application that defines payment requirements, validates payments, and delivers services
  • bex.co Facilitator: Handles payment verification and settlement through standardized endpoints
  • Blockchain: Executes and confirms all payment transactions (Sui, Ethereum, etc.)

How It Works

  1. Request: Client requests a protected resource from your server
  2. 402 Response: Your server returns HTTP 402 with payment details
  3. Payment Authorization: Client signs a payment authorization
  4. Verification: bex.co facilitator verifies and settles the payment on-chain
  5. Delivery: Your server receives confirmation and delivers the requested resource

Getting Started

Prerequisites

Before implementing x402 on your server:

  1. Get a bex.co API Key: Sign up for a free account
  2. Choose your blockchain: We recommend starting with Sui for fastest settlement
  3. Select your framework: We provide SDKs for popular frameworks

Quick Start Guides

Available Frameworks

  • Express.js - Build an x402-enabled Express server with our step-by-step guide
  • Hono - Build an ultra-fast x402-enabled Hono server
  • Next.js - Build a full-stack x402-enabled Next.js application

See our Quick Start Guide for a framework-agnostic implementation.

bex.co Facilitator Configuration

Production Endpoint

text
https://x402.bex.co

Supported Networks

NetworkStatusSettlement Time
SuiComing Soon<200ms
EthereumComing Soon~12s
BaseComing Soon~2s
PolygonComing Soon~2s
AvalancheComing Soon~2s

SDK Installation

bash
# Node.js / TypeScript
npm install x402
 
# Python
pip install x402

Quick Example

Here's a simple example of protecting an endpoint with x402 using Express.js:

typescript
import { paymentMiddleware } from "x402-express";
 
app.use(
  paymentMiddleware(
    process.env.ADDRESS as `0x${string}`,
    {
      "GET /api/premium/data": {
        price: "$0.01",
        network: "sui",
      },
    },
    {
      url: "https://x402.bex.co",
      apiKey: process.env.BEX_API_KEY,
    },
  ),
);
 
app.get("/api/premium/data", (req, res) => {
  res.json({ data: "Premium content" });
});

Want the complete implementation? See our detailed Express.js Integration guide for step-by-step instructions, advanced features, and production deployment tips.

Next Steps

  1. Quick Start Guide - Get started with x402 in minutes
  2. Implement a Crypto Paywall - Build a complete paywall system
  3. Join the Waitlist - Get early access to bex.co x402 facilitator

Additional Resources

  • API Documentation: Detailed x402 protocol specification (coming soon)
  • SDKs: TypeScript, Python, Rust, and Go client libraries (coming soon)
  • Dashboard: Monitor transactions and manage your x402 endpoints at bex.co/dash
  • Support: Get help on our Discord or GitHub

Pricing

bex.co charges a small facilitator fee per transaction:

  • Free Tier: First 1,000 transactions/month free
  • Pro Tier: $0.001 per transaction after free tier
  • Enterprise: Custom pricing for high-volume merchants

View full pricing details →

One API key for 30+ chains

bex router is a single multi-chain gateway — one key, one bill, metered in compute units instead of an account per network.

Explore bex router