x402 converts requests into revenue. SQD converts blockchains into structured facts. Rezolve brings both together under enterprise-grade commerce infrastructure.
The crypto community recently rediscovered an old HTTP status code with powerful new implications: HTTP 402 Payment Required, now gaining traction as x402. The concept: an API can respond with a 402 status code containing a price and payment instructions. The client pays in digital currency. The client retries the request. The server verifies payment and returns the result. No accounts, no OAuth, no API keys.
This matters for AI agents. Autonomous agents don’t do monthly subscriptions or credential management. They need to buy a single fact, pay instantly, and move on.
But payments are the easy half. The harder, more valuable part is making fresh, reliable, machine-readable facts available at inference time. On-chain activity is the richest signal — transparent and high-stakes — but it’s huge, fragmented, and hard to retrieve.
That’s Where SQD Comes In
SQD has spent years organizing multi-chain blockchain data into a combined lake-and-warehouse experience. With Rezolve Ai’s acquisition of Subsquid — days after Rezolve acquired Smartpay — the full stack falls into place:
- Data (SQD): Multi-chain on-chain facts
- Payments (x402 + Smartpay): Instant digital-asset settlement
- Intelligence (Rezolve Ai / Brain Suite): Enterprise orchestration and compliance
Smartpay processed over $1B in the twelve months ending September 30, 2025 — giving these 402-priced endpoints production-tested payment rails from day one.
How x402 Works
The protocol flow:
- API receives a request
- If unpaid, server returns 402 with pricing and payment instructions
- Client pays in digital currency
- Client retries the request
- Server verifies payment and returns the result
Illustrative price points: ~$0.01 per fact, ~$0.10 per curated bundle, ~$1.00 per deep trace.
What SQD Could Sell Per Request
Potential 402-priced revenue units:
- Open Token Facts — Canonical machine-readable information about tokens/projects
- Traces — Multi-hop transaction histories for contracts or addresses
- RAG Packs — Pre-structured bundles optimized for retrieval-augmented generation
- Risk Signals — Rolling anomaly flags monitoring suspicious patterns
- Social + On-Chain Joins — Identity graphs connecting platforms like Farcaster/ENS to blockchain activity
Each functions as a clean pay-per-request primitive: easy to meter, easy to compose. (These are exploratory concepts, subject to change.)
Why This Beats Subscriptions for Agents
- Low friction: No keys to issue, rotate, or leak
- Aligned incentives: Payment directly correlates with value delivered
- Composable: Agents can combine multiple 402-enabled providers
- Enterprise scalability: Rezolve offers reporting, reconciliation, and policy guardrails
What This Unlocks for Builders
Illustrative use cases:
- LLM Token Copilot: Query “What changed on-chain in 24 hours for $XYZ?” — purchase a RAG Pack, receive citations
- Risk Assessment Agent: Monitor address behavior approaching mixer adjacency — buy Risk Signals and transaction traces
- Growth Analytics: Track Farcaster adoption across projects exceeding $10M TVL — purchase Social + On-Chain Joins
- Trader Automation: Get alerts when governance voters overlap with deployer clusters — pay per fact bundle
The Takeaway
x402 lets agents pay per request. SQD makes the request worth paying for. Rezolve provides the path to enterprise-grade commerce and orchestration.
If you’re building agentic workflows and want to experiment with per-fact pricing — get in touch.
This post describes concepts currently under exploration and does not constitute a commitment to specific deliverables or timelines. Availability and scope will be determined following internal and partner reviews.