UCP by Vertical
UCP is live for retail, has a draft spec for lodging and a council for food. Travel, B2B and services have no UCP spec yet.
Each page shows what the spec defines for that industry, what is still open, and who is building it, checked against the spec itself.
Where each vertical stands
One line per industry. The status is what the UCP spec says today, not what has been announced.
| Vertical | Status | In one line |
|---|---|---|
| UCP for Retail | Live | UCP is live for retail. |
| UCP for Lodging | Draft spec | UCP has a draft spec for booking hotel stays. |
| UCP for Travel | Announced | UCP has no travel spec yet. |
| UCP for Food Ordering | Council formed | UCP has a Food Technical Council but no food ordering spec yet. |
| UCP for B2B | Community | UCP has no B2B spec, and B2B is not an officially named vertical. |
| UCP for Services | Community | UCP has no services spec. |
Explore a vertical
UCP for Retail
LiveThe first and largest UCP vertical — agents search catalogs, build carts, and check out across thousands of verified stores.
19,056 verified stores Shopify · Wix · WooCommerce · BigCommerce · +3 more Explore Retail & Shopping →UCP for Lodging
Draft specUCP's first lodging capability, dev.ucp.lodging.booking, is merged into the spec as a draft. It isn't in a release yet. Here's what it covers and what it still has to handle.
Amadeus · Booking.com · Expedia · Google · +3 more Explore Lodging & Hotels →UCP for Travel
AnnouncedFlights, rail and travel distribution are agentic commerce's hardest vertical — perishable inventory and dynamically generated offers, not fixed SKUs.
Amadeus · Booking.com · Expedia Group · Trip.com Explore Travel →UCP for Food Ordering
Council formedUCP has a seated Food Technical Council and a phased roadmap that starts at checkout, not the menu — but no food namespace and no published schema. Here's what it still has to handle.
Block (Square) · DoorDash · Google · Toast · +1 more Explore Food & Local Delivery →UCP for B2B
CommunityB2B isn't an officially-named UCP vertical, but it's the most-debated one. Where UCP actually fits B2B today — and the primitives the spec would have to add for the rest.
Aton (yes) · Cloudfy (yes) · Gotoclient (yes) · Presta (yes) · +4 more Explore B2B & Procurement →UCP for Services
CommunityAppointments, classes, reservations and rentals sell time, not stock. UCP has no services namespace yet — but a Governing Council working group is being explored, and scheduling capabilities are already turning up in real UCP profiles.
Wix — Universal Scheduling Protocol (draft) · Appointedd — com.appointedd.* · ligament-oss — #317 prototype · Community — issues #303 and #479 Explore Services & Bookings →How the spec is organised
The v2026-08-25 release moved payments and other generic pieces out of shopping/ into a shared common/ group. Payments, location, loyalty and identity are now used by every vertical rather than belonging to shopping.
Food and Lodging are the verticals the release named as next. Lodging's first capability, dev.ucp.lodging.booking, was merged into the spec as a draft on 24 September 2026 and isn't in a release yet. Food has a council but no namespace yet.
Services has no council, but scheduling capabilities under non-UCP namespaces already appear in real UCP profiles. As lodging, travel and food endpoints go live, these pages will track their adoption and readiness, measured the same way as platforms and capabilities today.
Explore protocol data
Is your store agent-ready?
Whichever vertical you're in, the prerequisite is the same: a valid, machine-readable UCP endpoint an agent can actually transact against.