AI Agents Will Pay Online Soon. Korea's Door Is Locked.

Opening

In May 2025, Coinbase quietly unveiled a protocol. Its name: x402. It revived HTTP status code 402 — the “Payment Required” code that had existed since the internet’s earliest days but sat unused for nearly 30 years.

The concept is simple. An AI agent sends a request to an API; the server responds, “This information costs $0.001”; the agent pays instantly, with no human involved, and receives the data. No credit card, no subscription, no account needed. Payment functionality gets attached with a single line of code.

7 months after launch, x402 had processed over 100 million transactions worldwide. Cloudflare co-founded the protocol’s foundation, and Google Cloud’s agent payment system adopted x402 as a payment rail.

And here, one question occurred to me.

Can Korean AI agents actually access this payment infrastructure?

Network Usage Fees: Where the Structure Began

To answer this question, we first need to understand a peculiar feature of Korea’s internet ecosystem.

Korea is the only country in the world where network usage fees have gone up. In 2015, the Ministry of Science, ICT and Future Planning (MSIP, now the Ministry of Science and ICT) revised the Interconnection Notification — the regulation governing interconnection fees between telecom carriers — introducing a traffic-based fee system. Under this structure, overseas services sending traffic into domestic networks effectively had to pay Korean telecom carriers.

In 2016, one company became the first to publicly criticize this change: Cloudflare, an internet infrastructure company operating servers in more than 120 countries.

Cloudflare revealed on its official blog that Korea’s network usage fees were more than 15 times higher than Europe’s. Then it quietly changed strategy — rerouting free-plan users’ traffic away from Korean servers to servers in Japan, Hong Kong, and the US instead.

Domestic developers still feel the result today. Unless you’re on the $200/month Business plan, running a Korean service through Cloudflare actually increases latency. You spin up a service in Seoul, and requests end up crossing the Pacific twice. That’s why “using Cloudflare routes you through Japan” is common knowledge in Korean developer communities.

There was an even more direct incident. In 2023, Korea’s 3 major telecom carriers blocked the domain of Cloudflare’s storage service, R2¹​, at the DNS level. When one user asked a carrier why, the reply was:

“Cloudflare was blocked because it doesn’t pay network usage fees for its non-enterprise customers, and the block won’t be lifted unless Cloudflare takes action.”

This is no longer a “performance issue.” It’s a structure that controls access itself.