How x402 Lets AI Agents Pay for APIs Automatically

How AI Pays for Paid APIs — and Gets Billed for It

On 6 May 2025, Coinbase unveiled a payment protocol called x402. It repurposes the web server’s “402 Payment Required” response so that a program can read a paid service’s price and settle it directly.

Say an AI agent tries to access paid data. The server sends back the price and payment terms. The agent, drawing on whatever wallet and funds it has available, sends back data authorizing payment, and once the payment is confirmed, it receives the information it needed. The whole point is to cut out the usual step of setting up a subscription account and API key for every single service.

“Automatic payment” doesn’t mean AI can spend money with zero setup. The wallet needs funds, and developers still have to decide what kinds of payments to allow. They can require a human to sign off every time, or let the system process payments automatically within pre-set limits.

When x402 announced its V2 in December 2025, the team said it had processed more than 100 million cumulative payments across APIs, apps, and AI agents. That figure can’t all be read as autonomous AI purchases, but it’s still notable how much experimentation is underway to wire payments directly into software.

In September 2025, Cloudflare announced it was working with Coinbase to establish an x402 foundation. Google also unveiled its own agent payment protocol, AP2, introducing crypto-payment extensions built on x402. That doesn’t mean all of Google’s payments are shifting to x402 — it’s one payment rail plugged in among several.

Reading all this, I found myself thinking about how easily a developer building a service in Korea could actually bring these tools into a real business. There’s a wide gap between code being open-source and actually serving real customers and collecting payment from them — a lot has to be worked out in between.

Network Costs Shape How Services Get Delivered

In an August 2016 post on its official blog, Cloudflare explained that internet transit costs in Seoul and Taipei ran about 15 times higher than the European and North American baseline. Transit refers to the service of relaying data through other networks. This figure was Cloudflare’s own cost comparison at the time.

In the same post, Cloudflare pointed to Korea’s interconnection rules as the backdrop for these costs. The terms governing how network operators exchange traffic and settle payments with one another also affect the operating costs of any service that relies on those networks.

What interests me is how operating costs translate into actual user experience. Service providers choose which networks to connect to and which server routes to use, weighing cost against quality. When a request from a user in Korea has to travel through an overseas server, latency can grow noticeably for certain tasks. Developers end up checking the routing and response times specific to accessing a product from Korea, even when it’s the same product used elsewhere.

That said, it’s too simple to say that Cloudflare’s free plan always routes overseas while a specific paid plan always gets processed in Seoul. Results can vary depending on the user’s network and how the service itself is configured. And a cost comparison from 2016 can’t fully explain every routing path in use today.

What the R2 outage records actually show

In September 2023, reports surfaced on Korean developer forums that certain domains related to Cloudflare’s file storage service, R2, had become unreachable. The issue, as described, was that DNS lookups were failing, making it impossible to connect to the service.

The records from that time contain conflicting explanations. Some comments relayed a telecom carrier’s response attributing the block to unpaid network usage fees. Others cited a different response, claiming it was a blocking request related to malware distribution. There were also reports that the symptoms varied depending on the domain and the network carrier, and comments noting that the block was lifted on September 26th.

Given this, it’s hard to treat these records as definitive proof that Korea’s three major telecom carriers blocked all of R2 over unpaid network fees. Nor can we conclude from this that R2 remains inaccessible today.

That said, this doesn’t erase the real development headaches at the time. If you were running a service connected to an external storage provider, a sudden loss of access meant you had to start hunting for the cause. The cost I see here isn’t just the number on the price sheet — it’s also the time spent checking and dealing with problems like this one.

Twitch Cited Network Costs as the Reason for Its Exit

Twitch announced in December 2023 that it would shut down its Korea operations on February 27, 2024. CEO Dan Clancy explained that network costs in Korea were 10 times higher than in most other countries. The company said it had tried P2P delivery and lowered the maximum resolution to 720p, but still couldn’t find a sustainable way to operate.

This was a judgment Twitch made based on its own operating costs and losses. It doesn’t mean every streaming company faces the same cost structure. But it does show that network costs can be a major variable in deciding whether to degrade service quality or exit a market altogether.

For users, the result was fewer services to choose from. It’s an important case for developers too — because the conditions for running a business aren’t just about which technologies are available, but whether you can keep delivering them at the price and quality you want.

Writing integration code and registering as a business are different problems

Stripe is a platform for online payments and subscription management. You’ll run into it constantly in overseas service documentation and code examples, but opening a standard Stripe Payments account under a Korean corporate entity isn’t supported. That’s a different issue from a Korean consumer paying by card at an overseas Stripe merchant.

Even if an AI coding tool generates working Stripe integration code, it doesn’t resolve the eligibility requirements for the business itself. If you’ve finished the code but can’t actually open the account you need, you have to pick a different payment service and redo the integration. This extra work is what I see as the real problem in go-to-market.

Businesses operating a payment gateway (PG) service in Korea face requirements around registration, settlement, and security. But not every business that uses an existing PG to sell its own products has to register as a PG operator itself — roles differ depending on the structure through which payment funds are received and settled.

Network segregation is another regulation that can weigh on businesses. The Financial Services Commission has been pursuing an improvement roadmap and some cloud-use exceptions since 2024. So it’s inaccurate to say Korean financial services can’t use global cloud infrastructure at all. In my view, the cost of adjusting infrastructure and operations to meet local requirements is a real factor in market-entry decisions.

There is a path to using Stripe: incorporate in a supported country. But a Korean corporation doesn’t necessarily need to set up an overseas entity just to receive payments from overseas customers. Domestic PGs that support cross-border payments, or merchant-of-record (MoR) services that take on the seller role and handle payment and tax processing, are also worth considering. Which products and countries each service supports varies.

PayPal isn’t limited to receiving payments in Korea, either. Per its official guidance, you can pay overseas sellers for goods and services or receive payment from overseas customers. What’s restricted is domestic transactions between two Korean accounts. Account eligibility, outbound payments, and domestic payments each need to be checked separately.

Even with alternatives available, extra costs remain. You have to re-compare fees and subscription-management features, decide on refund and settlement methods, and rewrite existing code. It amounts to a different starting point than teams that can simply apply the examples straight out of overseas developer documentation.

Oswarld’s Lens

When I’m mapping out a market-entry strategy, I weigh expected revenue against the cost of launching and maintaining the service. Network fees, payment-service contracts, and development and operations tailored to local regulations all factor into that calculation.

x402 isn’t a payment rail that only one company can operate — it’s an open protocol. The fact that opening a Stripe account is difficult in Korea doesn’t mean x402 becomes technically unusable. Nor is it a scheme that can only be implemented if you sign up with Cloudflare.

What concerns me is the gap that opens up when you try to turn an open technology into an actual business. Even if an agent successfully writes the code to send a payment request, the business still has to verify the customer’s payment authorization and operate collection, settlement, and refunds. A new protocol doesn’t make all of that disappear.

Nor does the program that executes the payment function on your behalf automatically register as a financial operator. Businesses have to review their liability and applicable requirements based on who is running the service and whose money is moving through which transactions. The clearer this process is, and the better it’s supported by tooling, the more time developers can spend actually testing their product.

I think that when evaluating Korea’s domestic network and payment environment, you have to go one level deeper than just listing which services are available. You need to look at how long integration takes, the cost of running domestic and international payments separately, and how long it takes to resolve outages. And it’s worth examining not just the costs already incurred, but also the market experiments that got delayed or abandoned along the way.

These days, more people in Korea are starting to build with vibe coding — building software by describing what you want in natural language and letting AI write the code — and interest in payment tools like Stripe is growing too. As the speed of building products increases, I’d like to see unnecessary delays shrink in the process of hooking up payments and infrastructure as well.

We need to be able to quickly test whether a service built in Korea can actually sell to customers abroad. Alongside introducing agentic payment technology, I think we need a conversation about reducing the friction domestic developers face in actually applying that technology to their businesses.

How AI Pays for Paid APIs — and Gets Billed for It

Network Costs Shape How Services Get Delivered

What the R2 outage records actually show

Twitch Cited Network Costs as the Reason for Its Exit

Writing integration code and registering as a business are different problems

Oswarld’s Lens

Your take shapes the next issue

References

How AI Pays for Paid APIs — and Gets Billed for It

Network Costs Shape How Services Get Delivered

What the R2 outage records actually show

Twitch Cited Network Costs as the Reason for Its Exit

Writing integration code and registering as a business are different problems

Oswarld’s Lens

Your take shapes the next issue

References

Related issues

EU Preliminarily Rules TikTok's Endless Scroll Violates DSA

Buying Chips Isn't the Same as Running a Data Center

Why Rare Earths, Nuclear Treaties, and Power Grids Connect