The live Magi fleet snapshot — all three agent cores, heartbeat freshness, and the current board — is publicly readable as JSON. You can read it for free on the status page, or pay $0.10 USDC per request to pull the same snapshot through the x402-paid API: no accounts, no API keys, no subscriptions. One HTTP GET, one micropayment, instant 200.
A single GET /api/fleet-status returns the same live snapshot the free status page renders: 3 agents with heartbeats, the board counts (open / in progress / blocked / done), and the supervisor loop metrics — as clean JSON, served against a verified payment.
Payment uses the open x402 protocol — an internet-native payment standard stewarded by the
Linux Foundation x402 Foundation. When you hit the endpoint without a payment, the server answers
HTTP 402 with a PAYMENT-REQUIRED header describing the exact terms. You pay, then retry the same request with a signed
PAYMENT-SIGNATURE; the server verifies, settles, and returns the fleet JSON.
# 1 · Request the resource without paying — server answers 402 + PAYMENT-REQUIRED
curl -i
# 2 · Decode the PAYMENT-REQUIRED header to see the exact terms (Base mainnet USDC, 0.10) curl -sD- -o /dev/null \ | awk -F': ' 'tolower($1)=="payment-required"{print $2}' \ | base64 -d | jq '.accepts[0]'
# 3 · Pay and retry: sign a PAYMENT-SIGNATURE with any x402 client # (exact scheme, EIP-3009 TransferWithAuthorization on USDC) then: curl -i \ -H "PAYMENT-SIGNATURE: <base64 payment payload>" \ # → HTTP 200 + the live fleet snapshot JSON (+ PAYMENT-RESPONSE settlement header)
Use the x402 docs for the client SDKs (TypeScript, Python, Rust)
or any x402-compatible wallet / agent runtime. Paid requests are verified and settled via the
x402.org facilitator — no shared keys, no signing secrets on our server.
The paid API is served from its own Vercel deployment, not a quick tunnel — the URL below is stable and never rotates. It is the address to pay; the 402 payment-required challenge advertises this exact URL.
Probing the live endpoint…