x402-axum-example

x402-axum-example

An example Axum server demonstrating how to protect routes using the x402-axum crate and enforce payments using the x402 protocol.

This example shows how to:

• Configure a remote facilitator for payment verification and settlement.
• Gate access to an API endpoint using the x402-axum middleware that requires on-chain payment before responding.
• Use dynamic pricing to adjust prices based on request parameters.
• Implement conditional free access by returning an empty price tags vector.
• Enable structured logging and distributed tracing using tracing and OpenTelemetry to observe what's happening inside the middleware.
• Support multiple chains (EVM and Solana) and multiple schemes (v1 and v2 protocols).

What’s Included

• Axum setup
  • Defines multiple protected routes with different pricing strategies.
• x402 middleware usage
  • Demonstrates both static pricing and dynamic pricing approaches.
  • Shows multi-chain support with EVM (Base Sepolia) and Solana payment options.
  • Includes conditional free access by returning empty price tags.
  • Adds human-readable metadata via .with_description(...) and .with_mime_type(...).
• Tracing setup
  • HTTP-level tracing via tower_http::trace::TraceLayer
  • OpenTelemetry integration via x402_rs::telemetry::Telemetry
  • Rich per-request spans that capture method, URI, latency, status, and middleware internals.

Prerequisites

• Rust 1.76+ (Rust 2024 Edition)
• A running x402 facilitator
• Optional .env file to configure OpenTelemetry endpoint

Try It

git clone https://github.com/x402-rs/x402-rs x402-rs
cd x402-rs/examples/x402-axum-example
cargo run

The server will start on http://localhost:3000 and exposes multiple protected routes:

• GET /static-price-v1 - Static pricing with v1 protocol (EVM + Solana)
• GET /static-price-v2 - Static pricing with v2 protocol (EVM + Solana)
• GET /dynamic-price-v2 - Dynamic pricing "exact" scheme with v2 protocol (adjusts based on discount query param)
• GET /conditional-free-v2 - Conditional free access (bypasses payment with free query param)

All routes are protected by x402 middleware and require valid x402 payments unless conditional free access is triggered. If no valid payment is provided, the server responds with a 402 Payment Required status and detailed requirements.

Dynamic Pricing Endpoints

The example includes endpoints demonstrating dynamic pricing:

Dynamic price with discount:

# Full price (100 units of USDC on both EVM and Solana)
curl http://localhost:3000/dynamic-price-v2

# Discounted price (50 units of USDC on both EVM and Solana)
curl http://localhost:3000/dynamic-price-v2?discount

Conditional free access:

# Requires payment (returns 402)
curl http://localhost:3000/conditional-free-v2

# Bypasses payment entirely (returns content directly)
curl http://localhost:3000/conditional-free-v2?free

The conditional free access works by returning an empty price tags vector from the dynamic pricing callback. When the middleware receives an empty vector, it bypasses payment enforcement and forwards the request directly to the handler.

This demonstrates the flexibility, allowing for complex pricing strategies including free tiers, promotional access, and conditional pricing based on any request criteria.

Example (Request with payment):

If you use an x402-compatible client like x402-fetch, it will automatically perform payment (e.g., 0.01 USDC on Base Sepolia or 100 USDC on Solana) before fetching any of the protected routes, and receive the protected response.

Example JS code to access a paid endpoint

import { createWalletClient, http } from "viem";  // https://viem.sh/
import { privateKeyToAccount } from "viem/accounts";
import { baseSepolia } from "viem/chains";
import { wrapFetchWithPayment } from "x402-fetch"; // https://www.npmjs.com/package/x402-fetch

// Create a wallet client
const account = privateKeyToAccount("0xYourPrivateKey");
const client = createWalletClient({
  account,
  transport: http(),
  chain: baseSepolia,
});

// Wrap the fetch function with payment handling
const fetchWithPay = wrapFetchWithPayment(fetch, client);

// Make a request that may require payment
const response = await fetchWithPay("http://localhost:3000/static-price-v2", {
  method: "GET",
});

const data = await response.json(); //=> { "hello": "paid-content" }

Telemetry

To enable tracing, configure OpenTelemetry using environment variables. For use with local OpenTelemetry Desktop Viewer create a .env file:

OTEL_EXPORTER_OTLP_ENDPOINT="http://localhost:4318"
OTEL_TRACES_EXPORTER="otlp"
OTEL_EXPORTER_OTLP_PROTOCOL="http/protobuf"

With telemetry enabled, traces will include spans like:

• x402.handle_request,
• x402.verify_payment,
• x402.facilitator_client.verify.

These can be visualized in tools like Jaeger, Tempo, or Grafana.

See how x402 traces look in the OpenTelemetry Desktop Viewer

• Payment Required: Request received without payment, and the middleware returned a 402 Payment Required response:

  

  Note how the span includes a status=402 event emitted by the middleware:

  

• Payment Accepted: A valid x402 payment was provided; the middleware allowed the request and settled the payment:

  

  The span includes an event showing status=200:

  

Related Crates

• x402-axum – Axum middleware used in this example.
• x402-rs – Core x402 protocol types, client traits, and utilities.

License

Apache-2.0