Spec-tracking UCP Core
We own the implementation work. Your store tracks the spec as it evolves, so you never chase a moving target.
UCP is the new open protocol for agentic commerce — co-developed by Google, Shopify, Etsy, Wayfair, Target and Walmart. UCPhub brings it to everything else: one spec-tracking core, a connector for your stack, and a fully working reference agent under one roof.
UCP is co-developed by
§ 01
UCP lets AI agents discover, compare and buy from your store. Without it, your catalog only exists as HTML humans can read — not as endpoints agents can safely check out against.
§ Both sides
UCP has a business side (the store being shopped) and a platform side (the AI agent doing the shopping). Most tools only do one. We ship both — so merchants have a place to sell, and agent builders have a real counterparty to build against.
The connector, the UCP endpoints, the dashboard. Everything your store needs to be discoverable and buyable by any UCP-compatible agent.
A fully working UCP platform (the agent side) you can browse, compare and transact against. Use it to develop, test and demo your own agent — no scraping, no reverse-engineering.
§ Architecture
One UCP Core, maintained by us and kept to spec as UCP evolves. One connector per commerce platform that plugs into it. Adding a new stack doesn’t mean a rewrite — it means a connector.
The protocol-side implementation. Checkout, identity, orders — kept up to the latest UCP spec so your integrations don’t drift.
The platform-side implementation. One connector maps your commerce platform into UCP Core — cleanly, reversibly, per-platform.
§ 02
Three steps, from your storefront to any UCP-compatible agent.
Plug UCPhub into your commerce platform. WooCommerce is a WordPress plugin that’s live today; more connectors are in active development. No re-platforming, no checkout changes.
Products, variants, offers, availability, checkout and order contracts get mapped into the Universal Commerce Protocol — automatically and on every change.
Your store now speaks UCP. Any UCP-compatible agent — including our own reference agent at app.ucphub.ai/demo — can discover, compare and check out against your catalog. No per-channel exports.
§ 03
UCPhub publishes the standard /.well-known/ucp endpoint for your store — plus an allowlist for the agents you actually want to transact with. You’re not exposed to every agent on the internet; only the ones you’ve said yes to.
GET /.well-known/ucp HTTP/1.1 Host: yourstore.com 200 OK content-type: application/json { "ucp": { "version": "2026-01-11", "capabilities": { "dev.ucp.shopping.checkout": [{ "version": "2026-04-08", "spec": "https://ucp.dev/2026-04-08/specification/checkout", "schema": "https://ucp.dev/2026-04-08/schemas/shopping/checkout.json" }], "dev.ucp.shopping.order": [{ "version": "2026-04-08", "spec": "https://ucp.dev/2026-04-08/specification/order" }] }, "payment_handlers": { "com.shopify.shop_pay": [{ "id": "shop_pay", "version": "2026-01-11" }], "com.google.pay": [{ "id": "gpay", "version": "2026-01-11" }] } } } // This is the real UCP discovery payload your store publishes // once UCPhub is installed. Agents read it, and use it to talk UCP.
Your store → allowlist ChatGPT ✓ allowed full checkout Gemini ✓ allowed full checkout Claude ✓ allowed full checkout Perplexity ✓ allowed discovery only UCPhub reference agent ✓ allowed full checkout Unknown agent · agent-xyz ✗ denied manual review required Unknown agent · scraper-bot-42 ✗ denied rate-limited // Toggle any agent on or off from your workspace. // Default policy: allowlist-only. UCPhub never auto-allows an agent // you haven't approved — the door stays closed until you open it.
§ 04
We own the implementation work. Your store tracks the spec as it evolves, so you never chase a moving target.
One core, a pluggable connector per platform. Adding a new commerce stack doesn’t mean a rewrite.
UCP has a business side (the store) and a platform side (the agent). We ship both — so you can build against a real, working counterparty today.
Remap fields, override taxonomies and enrich metadata per connector — without forking the protocol. Ships with the first non-Woo connector.
Offers, shipping matrices, tax rules and return windows encoded for agents — so AI checks out cleanly against your real policies.
UCP is developed openly at ucp.dev by Google, Shopify, Etsy, Wayfair, Target and Walmart. UCPhub is an implementation, not a proprietary fork.
§ 05
Your storefront stays. Your checkout stays. UCPhub quietly adds the UCP layer agents need — so customers coming in through AI assistants can actually buy from you, not a competitor.
Stop stitching a bespoke marketplace feed per client per channel. Configure the UCP layer once, roll it across your book, and own the agentic-commerce layer before your competitors notice it exists.
Stop reverse-engineering HTML. UCPhub runs a fully working platform-side reference at app.ucphub.ai/demo — a real UCP business you can discover, compare, and check out through, today.
GET /.well-known/ucp HTTP/1.1
Host: demo.ucphub.ai
200 OK
{ "ucp": {
"version": "2026-01-11",
"capabilities": {
"dev.ucp.shopping.checkout": [...],
"dev.ucp.shopping.order": [...]
}
} }
§ 06
UCP is going to be to agentic commerce what card-present payments were to the web. Getting it plumbed into your store early is the whole play — UCPhub made that a one-afternoon job.
My store’s job is to be buyable — by humans in my theme, and by agents over UCP. UCPhub let me do both without touching checkout. Nothing else came close.
One integration that covers every agent that will ever exist beats five custom marketplace feeds that constantly break. We rolled UCPhub across our entire client book in a quarter.
We stopped scraping product pages the week we pointed our agent at the UCPhub demo. Real price, real stock, real checkout. Night and day versus reverse-engineered HTML.
§ 07
ready when you are
install in < 5 min · no credit card · cancel anytime