Goppa Agentic Commerce

AI assistants already research and compare products for their users. For your store to show up in those answers, it has to speak the protocols the agents use. Shopify stores got this built in. Everyone else did not.

Goppa serves four things on your own domain, with no configuration:

• /.well-known/ucp — a UCP discovery manifest conforming to the published specification, so an agent can find out what your store offers.
• /llms.txt — a plain-text description of your store, categories and products for AI models.
• /mcp — a live MCP server (JSON-RPC 2.0, protocol 2025-06-18) with three tools: search_products, get_product and get_store_info.
• /goppa/catalog — your catalogue as schema.org/Product JSON.

Products, prices, stock status, categories and attributes are read directly from WooCommerce and cached for ten minutes.

What this does, and what it does not

This plugin makes your catalogue findable, readable and searchable by AI agents. Search ignores accents, so “tenis” finds “Tênis” and “fussball” finds “Fußball”.

It does not process carts, checkout or payments, and the manifest does not claim otherwise — it declares catalogue search and lookup, nothing else. An agent that reads it will send the shopper to your store to buy. Announcing a checkout that does not exist would make agents try to transact and fail.

Optional: see what the agents actually do

Paste a token from a Goppa account and the plugin reports agent activity — which endpoint was called, what was searched, which product was returned. Never visitor data. This is off until you configure it; see “External services” below.

External services

With no token configured, this plugin makes no external connection. Everything above is served from your own site and nothing leaves it.

If you enter a Goppa store token in Settings → Goppa, the plugin sends agent activity to the Goppa service at https://trygoppa.com (endpoint /api/ingest). This is what is sent, and only when an AI agent requests one of the four endpoints above:

• which endpoint was requested (for example mcp);
• the User-Agent string sent by the agent, which the service classifies into a known agent name;
• which MCP tool was called (for example search_products);
• the search term or product identifier the agent asked for;
• the name of the product returned first.

Records are queued and sent after the response to the agent has already been delivered, so the service being slow or unreachable never delays your store. Nothing is sent about your human visitors: no IP addresses, no customer or order data, no personal information. Clearing the token stops it immediately.

Service provided by Goppa — Terms of Service, Privacy Policy.