Try the 402 challenge from your browser
No install, no SDK. Click the button — your browser sends a JSON-RPC request to this Shield, the Shield is forced under load (demo mode), it responds with HTTP 402 and a signed challenge. Inspect the headers below to see exactly what an agent would receive.
Equivalent in curl
curl -i -X POST https://x402.rpcpriority.com/rpc \ -H 'Content-Type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"getHealth","params":[]}'
browser → fetch('/rpc', POST)
402 Payment Required
— this is the expected response under load
The Shield issued a signed economic challenge. An x402-aware agent would now sign the payload with its Ed25519 keypair and retry — see /live to watch this happen with real agents.
x402 challenge headers (decoded)
| Header | Value | What it means |
|---|