io.net Agent Cloud now supports Stripe and x402 payments, enabling AI agents to autonomously pay for GPU compute and top up credits.
Author: Akshay
24th June 2026 – io.net turned on Stripe and x402 payment support for its Agent Cloud. AI agents can now pay for their own GPU compute, with no human in the loop.
High Signal Summary For A Quick Glance
OnlyWMTx
@OnlyWMTx
@ionet cool. now who owns the pipe it runs on
AI agents could already spin up GPUs on https://t.co/WLXlHkv6f1 in under 3 minutes. Now they can pay for them too. Stripe + x402 support is live on https://t.co/WLXlHkv6f1's Agent Cloud Agents provision compute, top up IO Credits, and manage their own budget. Mid-session. No https://t.co/E1M4IAPybG
09:47 AM·Jun 24, 2026
thetugi⚡
@tugi369
@ionet Autonomous compute + payments in one flow. This is real agent infrastructure. Great step forward."
AI agents could already spin up GPUs on https://t.co/WLXlHkv6f1 in under 3 minutes. Now they can pay for them too. Stripe + x402 support is live on https://t.co/WLXlHkv6f1's Agent Cloud Agents provision compute, top up IO Credits, and manage their own budget. Mid-session. No https://t.co/E1M4IAPybG
09:21 AM·Jun 24, 2026
High attention and emotional sentiment detected.
The decentralized compute network announced the update on X at around 09:16 UTC. According to the post, agents can provision GPUs, top up “IO Credits,” and manage spending mid-session on their own.
io.net already let agents spin up decentralized GPU clusters in under three minutes. The new piece is payment.
Now an agent can run low on credits, pay to top up, and keep working without stopping. The company says this happens with no human intervention, no pre-loaded ceilings, and no hard stops.
So the loop is simple. An agent finds compute, provisions it, pays for it, and scales it. Then it tears the cluster down when the job is done.
The payment rails are Stripe and x402. IO Credits can already be topped up with a card through Stripe or with crypto through SpherePay. The x402 path adds programmatic, agent-driven payment on top.
x402 revives the long-dormant HTTP 402 “Payment Required” status code. The open protocol lets a server ask for payment directly inside a normal web request.
Here is the flow. An agent requests a paid resource, such as a GPU endpoint on io.net Agent Cloud. The server replies with HTTP 402 plus payment details, including the amount and accepted tokens.
Next, the agent sends USDC to settle the bill. Once the on-chain payment clears, the server authorizes the resource and the session continues.
Stripe handles the deposit addresses and captures the payment. According to Stripe’s docs, USDC settles on Base, Solana, or Tempo, with the Base USDC contract as a primary route.
This differs from a person paying with a card. There is no checkout screen, no card entry, and no manual approval step. Instead, the agent pays machine-to-machine with stablecoin rails.
The pitch here is “machines paying machines.” For the first time on io.net, an agent can both access and pay for compute on its own.
That matters because autonomous agents still lean on humans for infrastructure. Payment has been one of the last manual steps. Removing it brings the agent economy closer to a full loop.
x402 itself points in the same direction. Coinbase pioneered the standard, and Cloudflare and Stripe joined as partners. Stripe added x402 support on February 10, 2026, and the protocol later moved to the x402 Foundation under the Linux Foundation.
io.net is a Solana-based DePIN project that pools decentralized GPUs for AI workloads. The network launched in November 2023 and raised a $30 million Series A in March 2024, led by Hack VC.
Agent Cloud, first called Agent Compute, launched around March 25, 2026. It let agents discover, provision, and tear down GPU clusters without onboarding, KYC, or DevOps.
At that launch, io.net CEO Gaurav Sharma framed the goal in stark terms.
“An agent can independently find the best-priced GPU for the job, provision it, and manage the infrastructure end-to-end. This is a step towards truly autonomous agents.”
io.net reports more than 30,000 GPUs on its network. Tuesday’s payment update builds directly on that March release.
Timeline: io.net’s journey from decentralized GPU infrastructure and token launch through Agent Cloud and autonomous Stripe + x402 payments
Ahmad Shadid establishes io.net to address the growing need for affordable AI compute infrastructure, initially drawing from quantitative trading and high-performance computing requirements.
io.net launches publicly as a Solana-based DePIN platform aggregating distributed GPU resources for AI training and inference workloads.
The company raises $30 million in Series A financing, accelerating expansion of its decentralized compute marketplace and infrastructure stack.
A major Sybil attack targets io.net’s GPU network, leading to scrutiny over registered versus verified GPU counts and triggering broader debate about reported network metrics.
The $IO token enters the market while founder Ahmad Shadid steps down as CEO. Tory Green assumes leadership as the network enters its public token era.
The x402 protocol is introduced as an open standard enabling machine-to-machine payments through the HTTP 402 Payment Required framework, laying groundwork for autonomous commerce.
Stripe integrates support for x402 payments, initially centered on USDC transactions, creating a bridge between stablecoin payments and traditional payment infrastructure.
io.net introduces Agent Cloud (formerly Agent Compute), enabling AI agents to autonomously discover, provision, manage, scale, and terminate GPU clusters in under three minutes without direct human involvement.
io.net activates Stripe and x402 support within Agent Cloud, allowing AI agents to autonomously purchase compute, top up IO Credits, and manage budgets mid-session using machine-native payment rails.
With provisioning and payments now automated, the next step is broader deployment of self-managing AI agents capable of independently acquiring, scaling, and paying for infrastructure resources.
io.net’s roadmap increasingly aligns with an agent-driven economy where AI systems can discover services, negotiate costs, provision compute, and settle payments without human intervention.
Agents that spend on their own raise an obvious worry. What stops a buggy or hijacked agent from burning through funds?
The announcement says agents manage spending with no pre-loaded ceilings and no hard stops. io.net has not yet detailed budget limits, key management, or revocation controls. One early reply in Chinese stressed exactly this need for auditing and limits on budget permissions.
io.net also carries baggage. The project faced scrutiny in 2024 over GPU metric accuracy and supply claims, and it has cycled through three CEOs. Skeptics still question how much DePIN compute is real versus claimed. None of that is settled by Tuesday’s update.
The market reaction stayed muted. $IO traded near $0.18 around June 23 to 24, with 24-hour volume between roughly $13.9 million and $16.4 million, according to CoinGecko.
That puts the market cap near $63 million to $65 million on a circulating supply of about 350 million tokens. No clear price move tracked to the launch, which is no surprise given how fresh it is.
Early social reaction leaned positive but thin. Some builders called it real agent infrastructure. Others wanted to see guardrails first. This is not financial advice, and low volume can amplify swings in either direction.
Several questions remain open. io.net has not confirmed which chains and tokens its x402 integration uses in practice, the exact fees, or whether this is a full release or a preview.
The clearer test is usage. Watch for on-chain x402 settlements tied to io.net top-ups, an official blog or docs update beyond the tweet, and any spending controls the team ships. For now, io.net Agent Cloud has handed agents the keys to their own wallet, and the next move is theirs.
Our Crypto Talk is committed to unbiased, transparent, and true reporting to the best of our knowledge. This news article aims to provide accurate information in a timely manner. However, we advise the readers to verify facts independently and consult a professional before making any decisions based on the content since our sources could be wrong too. Check our Terms and conditions for more info.
