Frequently Asked Questions

AI assistants used to learn about your products by scraping the open web. That era is ending: assistants and the platforms behind them now read structured, brand-published feeds and endpoints defined by agentic-commerce protocols like UCP. Publishing a compliant UCP surface is how you become the source of truth an AI quotes – rather than leaving it to guess from whatever pages it can scrape. Run our completely free check to see whether your site already exposes what UCP expects.

The fastest way is to run our completely free check – we inspect your site against the published UCP spec and tell you exactly what passes and what doesn't. UCP is a technical specification with strict requirements for data structures, endpoints, and behavior, so it's genuinely hard to self-assess manually. For ongoing assurance – knowing you're still compliant after the next spec release – CorgiMaps continuously generates and maintains a compliant UCP surface for you.

You have two paths. The DIY route is to build and host UCP-compliant endpoints yourself, mapping your product, pricing, and inventory data from all your source systems and files into the exact schema the spec requires and then keep that build current as the spec evolves. The more straightforward path is using CorgiMaps, which connects to your existing data sources and generates compliant UCP endpoints for you, with no custom build necessary.

Shopping behavior is moving into AI assistants. Already, 73% of consumers are using AI in their shopping journey, and Accenture estimates that by 2030 more than 30% of online commerce – close to $3.1 trillion – will run through AI agents. If an AI can't see your products, it will recommend a competitor who is visible. Showing up isn't optional marketing. This is where the next purchase decision happens.

No. Each agentic-commerce protocol defines its own data structures, endpoints, tools, and transport. So supporting one does not make you compliant with another. They overlap in spirit but differ in the details, so each requires its own compliant surface. CorgiMaps covers the major protocols at once from a single connection to your data, instead of building and maintaining a separate integration for each.

Yes, protocols like UCP are how you do it. By publishing a compliant UCP surface, you control the product data, pricing, availability, and purchase behavior an AI uses, instead of letting it infer those from scraped pages. Passive scraping gives you no control in the agentic era; a brand-published protocol surface puts you back in charge of how you're represented.

Different AI assistants and shopping platforms back different protocols, and no single one covers every surface. Supporting only one means you're invisible everywhere it isn't used. To reach as many shopping surfaces as possible, you generally need to support several protocols at once, which is why CorgiMaps maintains compliant surfaces across the major protocols from one place rather than one at a time.

Keeping up is continuous work, not a one-time task. Specs ship new releases, requirements change, and entirely new protocols keep emerging. Doing this by hand means tracking 6–12 evolving specifications and re-validating after every release. This is exactly what CorgiMaps maintains for you. It tracks the spec changes and keeps your endpoints compliant as they land, so your team doesn't have to monitor the protocols at all.

Frequently. Major releases tend to land on roughly a quarterly cadence, with smaller changes and activity happening as often as weekly across the protocols and their governing bodies. Because the space is young and moving fast, a surface that's compliant today can fall behind within a few weeks if no one is watching.

Yes. As new versions of UCP are published and AI platforms deprecate support for older ones, a surface that was compliant can quietly stop working, and you may not notice until you've dropped out of AI results. Staying compliant means tracking every release and updating accordingly. CorgiMaps handles this version drift for you, keeping your UCP surface current as the spec moves.

UCP opens a net-new revenue surface by enabling purchases inside AI assistants, comparable in significance to the original rise of e-commerce. Being present means your products are discoverable and buyable wherever shoppers ask an AI; being absent cedes that share to competitors who showed up first. For marketing, it's a new channel to win – and, increasingly, one you can't afford to skip.

At its core, UCP compliance is a supply-chain-data problem. It's about exposing accurate product, pricing, inventory, and fulfillment information from your separate systems and files in the structure the spec requires. It doesn't ask you to change how you actually fulfill orders. CorgiMaps connects to your existing data sources to publish that information correctly – with no changes to your fulfillment, IT, or operations stack.

Building UCP support yourself typically means months of custom engineering – mapping your data into the schema, standing up and hosting endpoints, and testing against the spec – followed by constant monitoring of 6–12 evolving protocols to stay compliant. CorgiMaps removes nearly all of that: it generates compliant endpoints in minutes from your existing data and keeps them current as the specs change, so there's no build and no ongoing maintenance burden on your team.

No. UCP is a commerce standard – it defines the catalog, cart, checkout, order, and payment capabilities a brand exposes to agents. MCP is one of the transports UCP can run over, alongside REST and A2A. In other words, UCP describes what commerce capabilities you offer; MCP is one of the ways an agent can call them.

A UCP profile advertises a well-known card, including the capabilities you support (such as catalog search, checkout, identity linking, order management, and payment token exchange), and the live service endpoints that back them. Capability names must follow UCP's reverse-domain convention and point their spec URLs back to the matching authority. Our completely free check inspects all of this and probes the declared endpoints to confirm they respond.