Skip to content
Cerebrus Pulse

x402 Payments

x402 Payments

Section titled “x402 Payments”

Cerebrus Pulse uses the x402 protocol for payments — an open standard for HTTP-native micropayments built on the 402 Payment Required status code.

How It Works

Section titled “How It Works”
Client                          Pulse Gateway               Base / Solana
  |                                  |                                |
  |  GET /pulse/BTC                  |                                |
  |--------------------------------->|                                |
  |                                  |                                |
  |  402 Payment Required            |                                |
  |  + payment options (Base+Solana) |                                |
  |<---------------------------------|                                |
  |                                  |                                |
  |  Sign USDC payment              |                                |
  |  (x402 SDK picks your chain)    |                                |
  |--------------------------------------------> USDC transfer        |
  |                                  |                                |
  |  Retry request + payment proof   |                                |
  |--------------------------------->|                                |
  |                                  |  Verify payment via facilitator|
  |                                  |------------------------------->|
  |                                  |<-------------------------------|
  |  200 OK + analysis data          |                                |
  |<---------------------------------|                                |

The x402 SDK in your HTTP client handles steps 2–4 automatically. From your perspective, it’s just a normal HTTP request that costs $0.01–$0.04. The 402 response includes payment options for both Base and Solana — your SDK picks whichever chain your wallet is configured for.

Supported Networks

Section titled “Supported Networks”

Cerebrus Pulse accepts USDC payments on two chains. The 402 response includes payment options for both — your x402 SDK picks the right one based on your wallet.

PropertyBase (EVM)Solana
Network IDeip155:8453solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
CurrencyUSDCUSDC
USDC Address0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v
SchemeExact EVMExact SVM
FacilitatorCoinbase CDPCoinbase CDP
Gas/Fees~$0.001 ETH per txGasless (CDP fee payer)

Payment Details by Endpoint

Section titled “Payment Details by Endpoint”
EndpointPriceDescription
/screener$0.04 USDCMarket-wide scan of 50+ coins
/pulse/{coin}$0.02 USDCMulti-timeframe technical analysis
/sentiment$0.01 USDCMarket sentiment labels
/funding/{coin}$0.01 USDCFunding rate analysis
/oi/{coin}$0.01 USDCOpen interest analysis
/spread/{coin}$0.008 USDCSpread & liquidity analysis
/correlation$0.03 USDCBTC-alt correlation matrix
/arb$0.02 USDCMarket Stress Index
/cex-dex/{token}$0.01 USDCCEX-DEX price divergence
/bundle/{coin}$0.04 USDCCombined bundle (17% discount)
/healthFreeGateway status
/coinsFreeList available coins

Why x402?

Section titled “Why x402?”
  • No API keys — Your wallet address is your identity. No registration, no accounts.
  • No subscriptions — Pay only for what you use. One query = one micropayment.
  • Instant settlement — Payments settle on Base (fast, cheap L2) or Solana (sub-second finality).
  • Open standard — x402 is an open protocol. Any x402-compatible client works.
  • Transparent pricing — The 402 response includes exact payment details before you pay.

Wallet Requirements

Section titled “Wallet Requirements”

You need a wallet with USDC on either chain:

Option A: Base (EVM)

Section titled “Option A: Base (EVM)”
  1. USDC on Base — For payments (as little as $1 gets you 50+ pulse queries)
  2. A small amount of ETH on Base — For gas fees (typically < $0.001 per transaction)

Getting USDC on Base:

  • Bridge from Ethereum mainnet via the Base Bridge
  • Purchase directly on exchanges that support Base withdrawals (Coinbase, Binance)
  • Use a cross-chain bridge (Across, Stargate)

Option B: Solana

Section titled “Option B: Solana”
  1. USDC on Solana — Same pricing, same endpoints
  2. No SOL needed for gas — The CDP facilitator sponsors transaction fees

Getting USDC on Solana:

  • Purchase directly on exchanges that support Solana withdrawals (Coinbase, Phantom, Jupiter)
  • Swap on Jupiter or Raydium

SDK Options

Section titled “SDK Options”

Python

Section titled “Python”
Terminal window
pip install "x402[evm]" httpx    # For Base
pip install "x402[svm]" httpx    # For Solana

See the Python SDK Guide for full integration details.

TypeScript / Node.js

Section titled “TypeScript / Node.js”
Terminal window
npm install x402 viem                # For Base
npm install x402 @solana/web3.js     # For Solana

See the TypeScript SDK Guide for full integration details.

Budget Controls

Section titled “Budget Controls”

The x402 SDKs support budget limits to prevent accidental overspending:

# Python — the SDK supports per-request and global limits
# Configure in your client setup

At Pulse prices ($0.01–$0.04 per query), $10 of USDC gives you 250–1000 API calls.

Security

Section titled “Security”
  • Payments use EVM or SVM signatures — your private key never leaves your machine
  • The x402 facilitator (Coinbase CDP) verifies payments on-chain for both Base and Solana
  • Pulse never sees your private key — only the signed payment proof
  • All paid endpoints are rate-limited to prevent abuse
  • Solana transactions use CDP’s fee payer — no SOL needed for gas
Section titled “Related”