HTTP-402 Receipts
Cryptographic proof of data delivery. Verifiable receipts for AI agents and micropayments with pay-per-query protocol.
What is HTTP-402
Payment Required status code that enables cryptographic receipts for data delivery and instant verification.
- 01
Payment Required
HTTP status code 402 signals that payment is required before accessing the resource.
- 02
Cryptographic Receipt
Provider signs the data with their private key, creating verifiable proof of delivery.
- 03
Instant Verification
Verify receipts on-chain using Merkle proofs anchored in oracle rounds.
How it works
Complete pay-per-query flow with cryptographic receipts.
Agent Requests Data
AI agent queries ARQ Oracle API for price data: GET /api/v1/feeds/ETH-USD
Server Returns 402
Response includes payment address and amount required: 0.001 ETH to proceed
Agent Pays
Agent sends payment on-chain and includes transaction hash in retry request header
Provider Signs & Delivers
Provider returns data along with cryptographic receipt signed with their private key
Verify On-Chain
Agent verifies receipt against Merkle root published in the next oracle round
ARQ On-Chain Stack
Your oracle contracts on Robinhood Chain Testnet — from council-median feeds to HTTP-402 receipt anchoring.
ARQ Oracle owns the full stack — feeds, registry, and receipt anchoring on Robinhood Chain Testnet. Verify any round in the ARQ Lab or browse live contracts on the contracts page.