Ken Fromm retweetledi
x402 broke a million transactions in the last two weeks alone, as endpoints keep going live across the ecosystem.
Yet, a number of them appear to be unauthorized wrappers of services whose terms EXPLICITLY prohibit reselling. Right now there's no way to tell which is which.
Three cases to consider:
- Wolfram Alpha prohibits "resellers and aggregators," bans scraping, and bars sublicensing without permission. Yet, there's a third-party endpoint available for accessing it via x402
- Amadeus, a travel service, requires formal certification for any third-party connection, documented in a Service Order. You can access via Stabletravel. Whether the endpoint meets that standard isn't visible from the outside
- A third-party wrapper was sourcing Google Flights data via SerpApi — a company Google is actively suing for scraping Search results and reselling access. Endpoint was recently removed from the Agentic Market storefront
To be clear — the accountability here does NOT sit with x402. It's an open protocol, same as HTTP. It sits with those packaging unauthorized endpoints and collecting fees. With these current dynamics, providers bear the server load and see NONE of the revenue.
A cleaner model already exists. MPP marks first-party integrations directly on each service card. Exa announced native x402 support, going first-party and citing the Linux Foundation's governance as the reason for choosing it.
If there's no accountability here, it poisons the well. Potential native integrators become adversaries rather than participants. That revenue belongs to the providers. Native integration is how they claim it, and how x402 earns the legitimacy it needs to grow.
David Christopher@davewardonline
English
