HORIZON PULSE

Pay-per-call crypto data for AI agents

Honest x402 micropayments on Base mainnet (USDC). 6 live paid routes only — CoinGecko prices, technical signals, OKX perpetual funding (not Binance/Bybit), DefiLlama yields, on-chain portfolio risk, and Base/Ethereum gas. No invented metrics. No advertised 404s.

Live paid catalog (6)

Catalog frozen after first settlement — six live routes only; no new endpoints and no price changes. First settle: /api/pulse $0.005 — tx 0xedbd1a51….

GET /api/pulse — $0.005 USDC (5000 atomic) — BTC/ETH/SOL spot + momentum (CoinGecko)
GET /api/signals — $0.015 USDC (15000 atomic) — RSI/MACD/Bollinger + OKX funding
GET /api/yield — $0.02 USDC (20000 atomic) — DefiLlama yields (TVL ≥ $10M, prefer stablecoin/single-asset)
GET /api/portfolio?address=0x… — $0.04 USDC (40000 atomic) — Base + Ethereum balances, risk score, rebalance suggestions
GET /api/gas — $0.01 USDC (10000 atomic) — Base + Ethereum baseFee / priority / suggested maxFee + timingHint
GET /api/funding — $0.01 USDC (10000 atomic) — OKX BTC/ETH/SOL perpetual funding + crowding hint

Agent how-to (x402 v2)

Use base https://horizonpulse.dev (canonical). Backup: https://horizon-pulse-seven.vercel.app.
GET a paid route without payment → HTTP 402. Requirements are in the PAYMENT-REQUIRED header (x402 v2); body mirrors the same challenge.
Network is eip155:8453 (Base mainnet). Asset is USDC on Base. Pay the exact amount (atomic, 6 decimals) to payTo.
Retry the same GET with an x402 v2 PAYMENT-SIGNATURE header (not legacy X-PAYMENT as the primary path). Facilitator verifies + settles, then the JSON payload returns.

payTo: 0x5b32c973596078a967562ca652761404f19be0e9

USDC (Base): 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Network: base (eip155:8453) · Facilitator: Coinbase CDP x402

Free pages: GET / (this landing) · GET /status (live on-chain USDC on payTo — not an old Safe balance).

Host: https://horizonpulse.dev (canonical) · backup https://horizon-pulse-seven.vercel.app

Open /status GitHub

Unpaid paid-routes return HTTP 402 with PAYMENT-REQUIRED until a valid x402 v2 PAYMENT-SIGNATURE is provided. Settlement uses CDP when CDP_API_KEY_ID / CDP_API_KEY_SECRET are set. Coming-soon routes are not listed.