Wishlist x402

Written by: David Christopher

Translated by: Block Unicorn

As I was reading the recent report published by Galaxy Research, I gained one of the clearest visions of the future value of x402.

One example caught my attention: an intelligent agent helps users book trips by querying high-quality weather data through x402, finding the best dates and destinations, providing flight and hotel options, and then passing all information into the booking process. Each query is akin to a micro-payment. Each data source gets paid. The intelligent agent consolidates all information and ultimately makes the booking decision.

What impressed me was the perfect combination of x402 with data aggregation and management. Someone consolidates dispersed data sources into proprietary data, making it more useful than any single provider, and sells access via x402. Data managers only bear the cost of integration once. Callers pay per query. Everyone benefits (assuming the data volume is large enough, which we’ll discuss later).

From Galaxy Research

Before such services become widespread, I still believe x402 is in its early stages. If you’re a developer wanting to build with x402 but lacking inspiration, here are some conceptual products I would eagerly try if I could start using them immediately!

Skills Endpoint

Skills are carefully crafted instruction sets created by humans for AI agents to perform specific tasks.

Currently, most skill marketplaces use fixed fee models: permanent access costs $5, $15, or $20. This creates misaligned incentives. Users who only occasionally use skills pay too much, while power users pay too little, and skill creators can’t earn proportional value based on usage. A truly useful skill—like a genuinely helpful consultant (if such exists)—should be worth far more than a one-time $15.

x402 offers an alternative. Skill creators can publish their work via the x402 interface and set prices based on actual usage: pay-per-use (single session), monthly subscription (a new feature in x402 V2), or both. The payment system supports these modes. Skills with thousands of calls per month can generate ongoing revenue for creators, while less frequently used skills don’t require users to prepay.

Niche Cryptocurrency News Aggregation

Crypto news is scattered across Twitter, Telegram groups, podcasts, RSS feeds, and Substacks. Tracking a specific ecosystem becomes even more complex. Following all updates on Sui or Starknet means monitoring a dozen sources daily.

An x402 data stream tailored to the ecosystem can solve this. Someone can aggregate Twitter profiles, articles from website RSS feeds, and Telegram messages into a curated info feed for a specific ecosystem via API. The agent can query: “What happened in Starknet in the last 24 hours?” and receive structured responses. No more switching tabs or apps.

Ecosystem Data Aggregation

Developer activity has always been hard to measure accurately.

Electric Capital’s annual reports and their continuously updated dashboards are excellent open-source resources, but they have limitations. For example, I just checked the ecosystems with the highest developer growth over the past year: PancakeSwap, Monad, and Aleo. Of course, this is based on a single metric—but it also highlights a broader issue: developer activity data in crypto is highly fragmented, with no single source providing a complete picture.

Having an x402 data source that consolidates Electric Capital data, GitHub activity, Artemis metrics, and protocol-specific data into a weighted developer activity stream would fill a real gap. The agent could query: “How is Solana’s developer momentum over the past quarter?” and get more useful insights than raw commit counts.

News Briefs and Podcast Performance Trackers

One idea I personally find useful is a service that tracks the development of ideas presented in podcasts or news briefs and measures their progress over time.

Citron does something similar for the stock market, publishing annual forecast scorecards and performance evaluations at year-end. But for most news briefs and podcasts, if you want to know whether a media outlet’s predictions truly paid off over time, you have to do manual research.

A service via x402 could benchmark media predictions, filling this gap. Just provide the news brief or podcast, and it will track each prediction, timestamp it, follow subsequent price movements, and score the media’s past performance. The agent could query: “How did X’s asset predictions perform over the past year?” and receive verified answers.

Security and Audit Trail Trackers

Protocols rarely issue announcements proactively when attacked. News cycles are rapid, and if you’re offline when a vulnerability occurs, you might completely miss it. By the time you act, the event that should have garnered attention may already be buried under weeks of news coverage.

Security audits are similarly scattered across auditor websites, protocol documentation, and GitHub repositories. Reviewing a protocol’s audit history is more difficult than expected.

An x402 info stream aggregating this information into a queryable endpoint would be ideal. Users could pay a few cents extra to access this info before deciding on profit-sharing, especially when operating through an agent interface.

Is This Really Feasible?

All the above rely on two key questions: can the economic incentives support teams building these info streams? And are they legally permissible to develop?

Economically, the outlook isn’t optimistic. Since the early days of the internet, pay-per-project models have struggled. The perceived value of a paid content often exceeds the actual cost of payment, leading to high cognitive costs for deciding whether something is worth paying for. That’s why the internet shifted toward subscriptions: predictable billing, decision fatigue reduction, and lower churn.

But the advent of agents changes this. You top up your wallet, the agent spends on your behalf, and when funds run low, you top up again. API credits work similarly. The question shifts from “Is a few cents worth it?” to “Can endpoint providers recover costs at scale?”—which depends on usage volume.

Legally, x402 handles payments and metering but doesn’t alter upstream data copyright issues. If you use authorized APIs, public data, or first-party x402 endpoints, it’s straightforward product development. But relying on web crawlers or operating in gray areas of terms of service could limit persistence and scale. If upstream providers object, you’re in risky territory.

x402 V2 introduces dynamic payment routing and revenue sharing. Data managers can share some earnings with original data providers, aligning incentives and turning potential TOS conflicts into collaborations—though this reduces profit margins.

Whether the economics and legality can scale remains to be seen. But if they do, these are the data streams I’d be willing to pay for.

Can these economic and legal mechanisms work at scale simultaneously? We’ll see. But if they do, these are the data streams I’d pay for.