otto.de

No usable finding available for this protocol (no legitimate scan available within the candidate window).

No evidence that otto.de appears among AP2's 60+ named launch partners or any subsequent partner announcements. Named launch partners include Mastercard, PayPal, American Express, Adyen, Coinbase, Etsy, Lowe's, Salesforce, ServiceNow, Worldpay, Shopee, and others — otto.de is not among them. No otto.de-specific AP2 documentation, pilot announcement, or implementation was found.

No evidence found of otto.de or the Otto Group offering an MCP (Model Context Protocol) server or client endpoint. Otto does operate a documented REST-based Marketplace API (api.otto.market) for sellers and service partners, but no MCP surface was found in searches across otto.de, the Otto Group, and the otto.market developer portal. A separate unrelated 'OTTO MCP' product from Briq (a construction-finance company) appeared in results but is entirely unrelated to otto.de.

No evidence found that otto.de has adopted, announced, or been listed as a partner for MPP. Named launch and design partners on the protocol include Anthropic, DoorDash, Mastercard, Shopify, OpenAI, Visa, and Cloudflare — otto.de appears in none of these lists. MPP is a newly launched protocol (2026) and adoption among European retail e-commerce operators is not yet documented.

No evidence found of otto.de adopting or piloting NLWeb. Microsoft's confirmed NLWeb launch partners (announced at Build 2025) include Shopify, Tripadvisor, Eventbrite, O'Reilly Media, Common Sense Media, Allrecipes, Chicago Public Media, and Hearst/Delish — otto.de does not appear among them. No vendor-specific documentation, endpoint, or public announcement from otto.de regarding NLWeb was found.

No evidence found that otto.de (OTTO GmbH & Co KG) has adopted or announced support for the Universal Commerce Protocol. Searches across otto.de's developer portal (api.otto.de), corporate technology pages, and general UCP adoption coverage returned no mention of OTTO as a UCP participant or integrator. UCP coverage consistently references Shopify, Google, WooCommerce, Magento, and BigCommerce as adopters — not OTTO. OTTO does have its own Consumer API and AI initiatives, but none linked to UCP. Status is not_found rather than confirmed_absent because no vendor-specific denial or deprecation notice was found.

No evidence found that otto.de has implemented or announced WebMCP support. Searches surfaced WebMCP launch-context results naming early adopters such as Thumbtack (mentioned in lead-gen coverage) and Autheo, plus generic e-commerce guidance, but otto.de does not appear in any WebMCP adoption lists or partner mentions. Not_found chosen over confirmed_absent because no otto.de-specific statement on the protocol was located.

No evidence found that otto.de (the German e-commerce retailer) has any involvement with the x402 protocol. Known launch partners and early adopters include Coinbase, Cloudflare, Stripe, and QuickNode — none of which connect to otto.de. Otto.de operates as a traditional retail/marketplace platform with no public signal of stablecoin micropayment infrastructure adoption.

No evidence found that otto.de has built or published an app on OpenAI's ChatGPT Apps platform (Apps SDK). Searches surfaced Otto Group's internal ogGPT tool (an Azure OpenAI-based internal chatbot for employees) and OTTO's own on-site AI assistants launched March 2026, but neither of these is a ChatGPT Apps SDK integration. No mention of otto.de in the ChatGPT App Directory (launched December 2025), whose featured launch partners included Booking.com and Spotify but not OTTO.

Seller and service-partner marketplace management API: product listing submission, order retrieval, shipment management, returns, and receipt downloads for sellers operating on the otto.de marketplace; service partners may additionally manage product data on behalf of sellers

OTTO Market API is publicly documented at api.otto.market and covers products, orders, receipts, shipments, and returns across distinct seller and service-partner access paths. Access requires registering as a seller or certified service partner in the OTTO Market Developer Program; a sandbox environment is available for pre-production testing. OpenAPI specifications are published for all interfaces at the API index.

Consumer-facing product catalog read API: retrieves OTTO.de product listings in HAL+JSON format with pagination and filtering by EAN, article number, or last-modified timestamp; read-only catalog browsing

Documented at api.otto.de/portal with a dedicated getting-access page, API guidelines, and REST reference including HAL+JSON response profiles. Documentation is publicly visible but access appears to require registration (a dedicated 'getting-access' guide exists). Distinct from the OTTO Market API in both domain (api.otto.de vs api.otto.market) and purpose (read-only catalog vs full marketplace operations).

B2B internal stock-level notification interface for OTTO Group companies: webhook-push and GCP Pub/Sub notifications triggered when inventory levels change for product variations

HAP Connect API is documented at api.hapconnect.platform.otto.de and explicitly limited to OTTO Group companies rather than general external partners. As of the documentation reviewed, the notification implementation is in draft status and not yet active; the spec defines payload structures for GCP Pub/Sub offer notifications but the live system was not operational. Not a general-public or third-party developer interface.

Direct HTTP checks for https://www.otto.de/llms.txt, https://www.otto.de/AGENTS.md, https://www.otto.de/.well-known/agent, and https://www.otto.de/.well-known/ai-catalog.json all timed out with DNS resolution failures — the sandbox environment has no outbound internet access to otto.de. Web searches returned no results referencing otto.de publishing any self-declaration files. Unable to confirm presence or absence; this is a connectivity block, not an examined-and-found-nothing result.