For as long as the web has existed, there has been exactly one way into your site: a page of HTML built for human eyes. Buttons to click, forms to fill, menus to hover. Every visitor — every customer, every sale — arrived through that one door, a person driving a browser.
That assumption is quietly breaking. A growing share of the people who want what you sell will never load your product page themselves. They'll ask an AI assistant, and the assistant will act on their behalf: search your catalog, compare options, check availability, put things in a cart. The human still decides. But the hands on the keyboard belong to an agent.
When that agent shows up, what does it find? Today, almost always, a wall of markup written for someone with eyes and a mouse. It scrapes, it guesses, it gets your prices wrong, it misses your outlet section, it can't tell an in-stock variant from a sold-out one. It does its best with the human door because you never built it another one.
HTML was never meant for machines
HTML describes how a page looks, not what your business can do. A human reading "1 299 kr" and a small grey "Only 2 left" understands price and scarcity instantly. A machine sees two strings in two divs and has to reverse-engineer their meaning from layout — layout you will redesign next quarter and break again.
This is why agents scraping storefronts are unreliable, and why nobody wants to bet a purchase on them. The information is technically on the page, but it isn't offered in any form a machine can trust. Search, browse, product detail, cart, checkout — these are real capabilities your site already has. The problem is they're only exposed as pixels.
The new door: an agent surface
What agents need is a second interface to your site — one built for them the way HTML was built for people. In practice today that means an MCP (Model Context Protocol) surface: a small, well-described set of actions an assistant can call directly. Search this catalog. Get this product's details. Add this to a cart. Structured input, structured output, no scraping and no guessing.
Think of it as the difference between an agent squinting at your storefront and an agent reading a menu of exactly what your site can do, calling those actions with confidence, and getting clean, current answers back. An MCP surface is discoverable (an agent can find it), typed (it knows what each action takes and returns), and stable (it doesn't shatter when you restyle a page).
This is the same shift the web made once before. When sites started offering APIs, a whole economy of integrations, partners, and apps became possible on top of them — things the HTML page alone could never support. The agent web is that moment again, except the consumer isn't a developer wiring up an integration. It's an assistant, acting live, for a customer who is ready to buy right now.
Why this decides your site's future
Here's the uncomfortable part. Discovery is moving upstream — into the assistant. When a shopper asks their AI to "find a waterproof jacket under 1 000 kr and add the best one to my cart," the assistant will transact with the sites it can actually operate. If yours only speaks HTML, you're not in that conversation. A competitor with a clean agent surface is.
The sites that win the agent web will be the ones an assistant can reason about and act in without friction — the ones that answer accurately, in structure, in real time. That is no longer a nice-to-have sitting next to your website. For a meaningful and growing slice of demand, it is the way customers reach you. A good agent surface is becoming as fundamental as a mobile- friendly site was fifteen years ago: invisible when you have it, fatal when you don't.
Three ways to get one
So every site needs an agent surface. The real question is how you get one. There are three honest paths, and the right one depends on your team, your budget, and how much of this you want to own. Here's the trade-off, side by side.
| Build it yourself | Let poneva build it | Use a platform (e.g. Shopify) | |
|---|---|---|---|
| What you build | The whole MCP surface — map every capability, wire it to your catalog and inventory, describe it for agents. | Nothing. You point us at your site and we generate the surface from it. | Nothing custom — you get whatever agent features the platform ships. |
| Control | Total. Every layer is yours to shape. | High over what it exposes, though the surface runs through us. | Low. You get the platform's surface, on its roadmap. |
| Ongoing effort | Continuous — a surface that isn't maintained quietly rots. | None. It heals itself as your site changes. | None. Maintained by the platform. |
| Hosting & uptime | Yours to run. | Handled for you. | Handled by the platform. |
| Keeping up with the ecosystem | Your team tracks a fast-moving protocol and assistant landscape. | Our job, not yours. | The platform's job. |
| Cost | Expensive developers plus hosting; no per-use fee. | A service fee — but no build and no hosting. | Cheap to switch on if you're already there; platform fees and lock-in. |
| Requirements | An engineering team you can keep on it. | The site you already have — no migration. | Being on that platform, and running your business its way. |
| Best for | Teams that must own every layer and can fund it. | Teams that want the agent web without the build or a re-platform. | Merchants already all-in on the platform. |
We built poneva for the large middle: teams that need an agent surface, don't want to fund a permanent in-house project to get one, and either aren't on a big platform or don't want to reshape their business around one. You get the upside of the agent web without the build, on the site you already have — a working, self-healing MCP endpoint grounded in your real catalog, prices, and stock, so whichever assistant your customers use can actually do things on your site instead of scraping and guessing.
The web is growing a second face
The web isn't going to stop being made of pages people read. It's growing a second face — one made of capabilities agents can act on — right alongside the first. For the last twenty years your only surface was the human one. The next twenty will be defined by whether you also have the agent one.
Every site is going to need that surface. We'd like to give yours one before your customers' assistants come knocking and find only a wall of HTML. Point us at your store — we'll do the hard part.