Hosted Agent Layer

The machine-facing storefront, generated and hosted for you.

We generate and host the structured catalogue, the protocol endpoints and the agent-identity rules that turn your fix list into a running service, so agents can discover, read and buy from you without your platform having to support any of it.

Waitlist. We are building this with a small number of pilot merchants on WooCommerce and BigCommerce.

Join the waitlist Get your free score first

Pricing

Setup
£1,500
From. Depends on platform and catalogue size.
Hosting
£249/month
From. A revenue-share option on agent-attributed orders is available because the layer sits in the transaction path and can prove them.

Prices exclude VAT and sales tax where applicable. Monthly plans are billed monthly and can be cancelled any time. Refunds and cancellation.

Is this for you?

You are not on Shopify or Adobe Commerce, so UCP, ACP and MCP are not switched on for you.
You sell in booking, lodging, food or local services, where the protocol councils exist but platform support lags.
You want one gateway that stays current as the protocols change, rather than an integration per protocol.

Probably not for you if…

You are on Shopify with Agentic Storefronts enabled and your score is already above 85. You have most of this.

What it is made of

Offer graph: One normalised record per product, with price, currency, availability, variants, delivery promise, returns terms and promotion conditions. Every layer below reads from it.
Schema service: Product, Offer, Organization and AggregateRating JSON-LD generated from the offer graph and served by tag or at the edge.
Discovery front door: A UCP business profile, an ACP document and an MCP server exposing catalogue, offer and policy tools, so agents call you instead of scraping you.
Checkout proxy: UCP checkout-session endpoints that call your existing cart and checkout. You remain merchant of record; payment stays tokenised through handlers so nobody new enters PCI scope.
Agent access rules: Verification of signed agent requests and the WAF rules that stop legitimate agents getting a 403.
Agent analytics: Which agents fetched what, and which orders they produced. Most merchants cannot see this today.

How it works

Read-only first
Offer graph, schema, discovery documents, MCP tools and analytics go live without touching checkout.
Adapters, not rebuilds
WooCommerce and BigCommerce first, then a generic adapter that takes a feed in and a webhook out.
Checkout proxy on pilot
Once the read-only layer is live and measured, the checkout proxy is switched on with a merchant willing to pilot it.
Protocols as adapters
One internal commerce model with UCP, ACP and MCP as adapters over it, so protocol churn stays in the adapter.

What you get

A live /.well-known/ucp profile and ACP document for your domain
Generated JSON-LD on every product page
An MCP server for your catalogue, offers and policies
WAF rules and a verified-agent allow-list
Agent traffic and order attribution reporting
On pilot, UCP checkout sessions proxied to your existing checkout

What it does not do

Questions

Which protocol do you support?

UCP first, because Google, Shopify, Amazon, Meta and Microsoft sit on its council and the specification is stable. MCP always, because every assistant reads it. ACP second, for presence inside ChatGPT. Payment authorisation is handled through the payment handlers rather than implemented directly.

Does this replace our platform?

No. It sits in front of it. Your catalogue, cart, checkout and order management stay where they are.

Why a revenue-share option?

Because this layer is in the transaction path and the analytics component can prove which orders came through agents. It is the one product where a share of attributed orders is honest.

Join the waitlist.

Tell us your site and platform. We reply within two working days with next steps and a start date.

Join the waitlist