RAEN — Live x402 Agent APIs on Base
November 2026. Royal Agentic Enterprises operates paid HTTP APIs that AI agents can call autonomously. No accounts, no API keys to manage, no billing dashboards — an agent pays per request in USDC on Base and gets its answer in the same HTTP exchange.
What's live
Every endpoint below is a real, deployed service returning a valid x402 402 challenge on Base mainnet (eip155:8453). Pricing is per call:
| Endpoint | Price | What it does |
|---|---|---|
| nanobanana-x402.fly.dev | $0.01 | Image generation & editing |
| nft-alpha-x402.fly.dev | $0.02 | NFT alpha signals across 8 tracked collections |
| royal-ruby-x402.fly.dev | $0.05 | US consumer-rights law citations (FCRA / FDCPA / TILA / state UDAP) |
| contract-eye-x402.fly.dev | $0.05 | Contract analysis |
| tradingagents-x402.fly.dev | $0.05 | Multi-agent ticker analysis |
| dispatch-x402.fly.dev | $0.50 | Intent routing across the RAEN fleet (23 services) |
| dispute-forge-x402.fly.dev | $0.75 | FCRA-compliant dispute letters |
| briefsnap-x402.fly.dev | $1.00 | Brief generation |
| staci-tradingagents.fly.dev | $5.00 | Deep multi-agent trading consensus |
Escrow and vault-pro endpoints are also live for payment escrow and scaffolding flows.
How to call one
Send an unauthenticated request and the service replies 402 Payment Required with a signed challenge naming the asset (USDC), amount, recipient, and facilitator. Pay that exact challenge with any x402-compatible client — @x402/fetch, the MCP x402 tools, or any HTTP-402 wallet flow — replay the request with the payment header, and the answer comes back with the service response.
Example: POST https://royal-ruby-x402.fly.dev/api/law-lookup with {"topic": "credit reporting"} returns a 402 challenge for $0.05 USDC on Base. Settle it, get the citations.
Why this shape
Agents don't have credit cards. They have wallets. HTTP 402 was designed for exactly this — pay-per-call micropayments with zero signup friction. The whole fleet settles through public facilitators on Base mainnet.
Discovery
All services emit x402 discovery extensions in their 402 responses, so x402-native indexes and agent bazaars can find them automatically. Every service also publishes /.well-known/x402.json describing its endpoints, prices, and schemas.