Empire Access Layer (EAL)

​

What EAL is for

​

BYO-x402 (live today)

​

What you need

• An x402-capable agent or client. This includes Claude Code / Cursor with an x402 payment tool (for example via Base MCP), or any client built with an x402 library (x402-fetch, @x402/axios, @coinbase/x402).
• A funded wallet with USDC on Base (Polygon and Solana are also supported). Calls cost roughly $0.001–$0.05 each for intelligence reads; a few dollars covers a lot of usage. Use a dedicated, lightly funded wallet — never your main treasury.

​

1. Discover the catalog

# Human/JSON catalog of all live endpoints + indicative prices
curl https://x402.ottoai.services/otto-x402-catalog.json

# Machine-readable catalog for AI agents
curl https://x402.ottoai.services/llm.txt

# Standard x402 discovery document
curl https://x402.ottoai.services/.well-known/x402

​

2. See the paywall

curl -i https://x402.ottoai.services/crypto-news
# → HTTP/1.1 402 Payment Required
#   (body describes the USDC amount + chain to pay)

​

3. Pay per call

import { wrapFetchWithPayment } from "x402-fetch";
import { createWalletClient, http } from "viem";
import { privateKeyToAccount } from "viem/accounts";
import { base } from "viem/chains";

// Your own funded wallet — this key never leaves your machine and is never sent to Otto.
const account = privateKeyToAccount(process.env.X402_PRIVATE_KEY as `0x${string}`);
const wallet = createWalletClient({ account, chain: base, transport: http() });

const fetchWithPay = wrapFetchWithPayment(fetch, wallet);

const res = await fetchWithPay("https://x402.ottoai.services/crypto-news");
const data = await res.json(); // paid, settled, and returned in one call

​

Where to look next

• The full endpoint list, prices, and capability tags live on the x402 Storefront page.
• Prefer on-chain USDC escrow with receipts and reputation for higher-stakes jobs? Use acp-cli instead.

​

Coming soon: fund one Safe, Otto auto-pays

• Fund once. You’d fund a single non-custodial Otto Safe (the same user-owned Safe7579 account /app is converging onto) — and that one balance would power both the dApp and your agent.
• Authorize a capped, revocable pull. You’d sign once to grant Otto’s payer a bounded permission to pull USDC from your Safe to cover your calls — with an exact spending cap, an expiry, and the ability to revoke at any time. It is not a blank check: Otto’s authority is limited to the cap until expiry or revocation, and never the whole Safe.
• Your agent stays keyless. Your agent would authenticate to your Otto account with a scoped, revocable token — no on-chain key ever enters the agent’s sandbox. A stolen token alone can’t move funds beyond the cap, and you revoke it from the dApp.
• One balance, two front doors. The same funded Safe would back both the /app dashboard and your external agent — fund in one place, spend across the empire.

​

Summary

• Live today: point your own agent at Otto’s x402 catalog and pay per call from your own funded x402 wallet (BYO-x402). No keys go to Otto; you approve every payment.
• Coming: fund one non-custodial Safe once and let Otto auto-pay your agent’s calls under a capped, revocable permission — keyless agent, one balance across the dApp and your terminal.