翻訳待ち：We're in Web 3.0

AI サービスが一時的に利用できないため、復旧後に翻訳を補完します。

← writing We're Already in Web 3.0 Agata Ciesielski · August 5, 2026 The Agentic Web · 2026 Web 3.0 agents reach it for us Web 2.0 our code talks to it Web 1.0 we read it YOU ARE HERE I've spent the last three weeks trying to talk myself out of one sentence. The sentence is: we are in Web 3.0, right now. I couldn't do it. So instead I'm going to try to talk you into it. The name is radioactive I know using the phrase Web 3.0 is radioactive. The last people who used it were selling tokens, and we all got so sick of hearing about it that our brains now turn off the moment someone says it. But I think the crypto crowd had the right instinct and the wrong candidate. Funny enough, crypto wasn't even the first claimant. In 2006 the name went to the Semantic Web, a dream of a web that machines could read and act on for us. Which sounds familiar. The web really does move in eras, and a new one was due. It's just that it was ready for an evolution, not a demolition. Three doors This all started at my keyboard. Every website I build has a frontend and a backend API. That's been standard for as long as I can remember: the pages people read, and the interface our code talks to. But sometime in the past year, a third piece became standard for me without my noticing the moment it happened: the MCP server, the interface agents talk to. I was writing myself rules for when to build one, and stopped mid-list. Every site I ship now has three doors. One for people. One for code. One for agents. That's not a new feature. That felt like a new web. At first I thought this new web was just MCP. Then I looked around and realized it's much bigger. MCP wraps the APIs we already have, but it has siblings. There's a protocol that wraps a webpage's own buttons. One that wraps checkout, one that wraps the payment signature, one that wraps the favor of my assistant calling yours. Every one wraps something that already exists, and every one is an old human behavior, translated. Nothing gets rebuilt. There's the evolution. The doors are getting used And the new doors are getting used. This year, automated traffic passed human traffic on Cloudflare's network for the first time ever measured. Most of that is still crawlers feeding models, and the errand-running slice is small. But it's bending faster than anything else on the chart. Every behavior gets its own fight They're getting fought over, too. Commerce has two competing protocols, and merchants are being told to support both. Payments has five contenders. (Two of them settle over stablecoins. Yes, crypto found its way into my Web 3.0 after all. As plumbing. 😅) Two different protocols are currently named ACP. And beside the contenders, the corpses and zombies: one protocol has already merged into its rival, and one standard is published by thousands of sites and read by no one. The agentic web · August 2026 Six behaviors. Fifteen protocols. One era. Every human behavior on the web is getting its own standards fight. That is what the inside of an era looks like. The human behavior The contenders State of the fight Using tools and services MCP vs. everyone's custom plugins and function schemas ● SettledThis era's REST moment. Adopted by every major lab. Browsing and clicking a site WebMCP vs. agents scraping screens with vision ◙ EarlyIn browser origin trials. Barely deployed yet. Asking a site a question NLWeb llms.txt one protocol, and one file published by thousands, read by no one ◙ UnsettledNLWeb growing. llms.txt widely adopted, ignored by every major platform. Shopping and checkout UCP ACP Google + Shopify vs. OpenAI + Stripe ▲ Live fightMerchants already told to support both. Authorizing a payment AP2 x402 MPP Visa TAP Mastercard Agent Pay ▲ Hottest spaceFive contenders. The money is literally here. My assistant calls yours A2A IBM ACP ANP AGNTCY yes, at least two protocols answer to ACP ● ConsolidatedA2A won. IBM's ACP merged into it, August 2025. Wins, wars, corpses, and one zombie, all at once. Agata Ciesielski That mess is what finally did it, because it's a mess we've seen before. Nobody defined Web 2.0 as REST. REST and SOAP fought it out years after everyone already had an API, because you only fight over standardizing a behavior people are already doing messily. The sign-in wars ran until 2012. You can tell how far into an era you are by which fights are still open. The eras were never about technologies So here's the frame that convinced me, three weeks in. The eras of the web were never defined by technologies. They're defined by how we reach the web. Web 1.0 was pages: we read it. Web 2.0, to me, was APIs: our code talked to it. And the next era was never going to be about where the blockchains go. It's that we reach the web through agents now. I'd been building the answer into every website without noticing. From inside the standards fight, none of this looks like a future being predicted. It looks like scaffolding going up around a building people are already living in. Nobody sent an announcement. Nobody did for Web 2.0 either. We're in it. What this new web does to the people using it, and how it changed the way I build, are the next two pieces. Piece one of three. Originally published on LinkedIn.