X402 Payment-Protected AI Chat

Get started with X402 payments in 3 simple steps:

Step 1: Create Your Wallet

The X402 client includes an integrated wallet system powered by Coinbase's CDP SDK. Your wallet is created locally and securely stored in your browser.

Step 2: Fund with USDC

Add USDC to your wallet to pay for messages. The client supports both Base mainnet and Base Sepolia testnet.

Choose Your AI Agent

Select from published agents or connect to any X402-compatible agent endpoint.

Our X402 Payment Facilitator provides the infrastructure for secure payment verification and settlement. It handles the complex cryptographic operations required for X402 protocol compliance.

paymentMiddleware(config, {
  "url": "https://x402-facilitator.aurracloud.com/api/v1/<YOUR_API_KEY>"
})

For developers who want to integrate X402 payments programmatically, here are the API details:

Request Format

{
  "messages": [
    {
      "role": "user", 
      "content": "What is the current price of ETH?"
    }
  ],
  "id": "unique-session-id",
  "userId": "user-identifier",
  "selectedToolkits": ["defillama", "chainlink"]
}

Example Request

curl -X POST https://x402.aurracloud.com/agent/00000000-0000-0000-0000-000000000001/v1/chat \
  -H "Content-Type: application/json" \
  -d '{
    "messages": [
      {
        "role": "user",
        "content": "What is the current price of ETH?"
      }
    ],
    "id": "test-session",
    "userId": "test-user",
    "selectedToolkits": ["defillama"]
  }'

Step 1: Initial Request

When you make a request without payment, you'll receive a 402 Payment Required response:

{
  "error": "Payment Required",
  "payment": {
    "amount": "0.01",
    "currency": "USDC",
    "network": "base-sepolia",
    "receiver": "0x...",
    "instructions": "..."
  }
}

Step 2: Complete Payment

Use an X402-compatible client or wallet to complete the USDC payment. The payment creates a cryptographic proof that can be used to access the protected resource.

Step 3: Access with Payment Proof

Retry your request with the payment proof in the X-PAYMENT header to access the protected content:

{
  "messages": [...],
  "reasoning": "The agent's thought process",
  "toolCalls": [...],
  "usage": {
    "inputTokens": 50,
    "outputTokens": 150,
    "totalTokens": 200
  }
}