How x402 works
1
Client sends requestYour app (or Claude) calls the endpoint normally - no auth header needed.
2
Server responds 402 Payment RequiredThe response includes a payment descriptor: amount, asset (USDC), network (Base), and recipient address.
3
Client settles on-chainThe x402 client library signs and submits a USDC transfer on Base (eip155:8453) to 0x348Df429BD49A7506128c74CE1124A81B4B7dC9d.
4
Server verifies & respondsOnce payment is confirmed, the server executes the request and returns the result. The whole flow completes in one HTTP round-trip for the caller.
Quick start - REST

Use x402-fetch (or any x402-compatible client) to handle payment automatically:

import { fetch402 } from 'x402-fetch';

const response = await fetch402(
  'https://api.aurelianflo.com/api/ofac-wallet-screen/0xAbC123...',
  {
    method: 'GET',
    headers: { 'Accept': 'application/json' },
  },
  {
    walletClient,  // viem WalletClient on Base
  }
);

const result = await response.json();
console.log(result.sanctioned, result.matches);
Claude Setup

In Claude, go to Customize > Connectors and add this server URL to connect AurelianFlo tools:

https://aurelianflo.com/mcp

Claude Desktop does not use claude_desktop_config.json for remote MCP servers.

Generic MCP Client JSON
{
  "mcpServers": {
    "aurelianflo": {
      "type": "http",
      "url": "https://aurelianflo.com/mcp"
    }
  }
}

Use this JSON only for MCP clients that support direct remote HTTP MCP configuration.

Authentication

No API keys or end-user OAuth are required. Paid calls still settle in USDC on Base to the recipient address below:
0x348Df429BD49A7506128c74CE1124A81B4B7dC9d

Reference