noon.com

No evidence of noon.com (the Middle East e-commerce platform) appearing as a launch partner, adopter, or implementer of the Agent2Agent (A2A) protocol. The named founding and early partners in both the April 2025 Google launch and the subsequent Linux Foundation transfer are enterprise software and cloud vendors — Atlassian, Box, Cohere, Intuit, LangChain, MongoDB, PayPal, Salesforce, SAP, ServiceNow, AWS, Cisco, Microsoft — with no consumer or regional e-commerce presence matching noon.com. Choosing not_found (not confirmed_absent) because no noon.com-specific statement or deprecation notice was found; absence is from search coverage, not a vendor declaration.

No evidence of noon.com participating in the Agentic Commerce Protocol (ACP) as a launch partner or subsequent adopter. The confirmed ACP launch partners identified in the OpenAI and Stripe announcements are Etsy and Shopify (and select Shopify merchants such as Glossier, Vuori, Spanx, and SKIMS) — noon.com does not appear among them. This is a not_found rather than confirmed_absent because no noon.com-specific statement or deprecation notice was located; the protocol is simply not mentioned in connection with this vendor anywhere in the available evidence.

No evidence that noon.com (the Middle East e-commerce platform) appears among AP2's known launch or contributor partners. The 60-organization list published at AP2's FIDO Alliance donation includes Mastercard, PayPal, Adyen, Etsy, Revolut, and others — noon.com is not among them. No noon.com-specific AP2 documentation, announcement, or integration was found. Status is not_found rather than confirmed_absent because absence is based on non-appearance in available partner lists, not a noon.com-specific rejection or deprecation statement.

No evidence of an MCP server or MCP-based integration published by noon.com (the Middle East e-commerce marketplace) was found across searches targeting their developer/API surface and any AI-agent integration announcements. Third-party connectors (Datavio, Apify scrapers, Omniful) exist for noon marketplace data, but none are official MCP implementations. The search space is somewhat constrained because noon's seller/partner API documentation sits behind a partner portal requiring registration, so an embedded MCP link inside gated docs cannot be ruled out, but no public-facing evidence was located.

No evidence that noon.com (the Middle East e-commerce platform) is a launch partner or documented adopter of MPP. Named launch partners include Anthropic, DoorDash, and Mastercard. MPP is a newly launched (March 2026) open standard co-authored by Stripe and Tempo; noon.com has no visible developer surface or public documentation indicating adoption.

No evidence found that noon.com has implemented NLWeb or appears in any known launch partner list for the protocol. Named NLWeb launch partners and ecosystem references found include Shopify, Google (UCP/NLWeb adjacent), and Microsoft's own Azure/GitHub implementations — noon.com is absent from all such lists. Search results for noon.com returned only affiliate and seller-onboarding content unrelated to NLWeb.

No evidence found that noon.com (a major Middle East/Gulf e-commerce marketplace) has integrated with or announced support for UCP. Search results for 'noon.com UCP' and 'noon UCP checkout Google merchant agentic commerce Middle East' returned only Google/Shopify UCP documentation and general merchant guidance, with no mention of noon.com as a participating merchant. Google's own documentation notes UCP checkout is currently limited to select US merchants, which further reduces the likelihood noon.com would yet appear. No vendor-specific announcement, Merchant Center integration evidence, or UCP profile was found — not_found chosen over confirmed_absent because noon.com's silence on UCP may simply reflect non-US geographic scope rather than a deliberate decision against it.

No evidence found of noon.com implementing or announcing WebMCP support. The protocol, co-developed by Google and Microsoft, is still in early preview/experimental stage with no publicly documented e-commerce launch partners at all — named adopters in available sources are generic demo apps (e.g., a restaurant reservation example from GoogleChromeLabs) and individual developer blogs, not major retail platforms. noon.com was not mentioned in any WebMCP coverage found. Status is not_found rather than confirmed_absent because noon.com has made no vendor-specific statement either way.

No evidence that noon.com (the UAE/Middle East e-commerce platform) has adopted or announced support for the x402 protocol. The known x402 ecosystem members and launch partners include Coinbase, Cloudflare, Google, Microsoft, AWS, Shopify, Stripe, Visa, Mastercard, Circle, Solana Foundation, Fiserv, and Polygon Labs — noon.com does not appear among them. Noon.com is a consumer retail marketplace with no publicly documented API surface oriented toward stablecoin micropayment settlement.

No evidence found of noon.com (the Middle East/North Africa e-commerce platform) building or publishing an app on OpenAI's ChatGPT Apps platform via the Apps SDK. Searches surfaced only noon.com's own mobile apps (iOS/Android) and unrelated OpenAI ecosystem content. No noon.com developer announcements, ChatGPT app store listings, or SDK integration documentation referencing noon were found.

Marketplace seller/partner API covering order management, product catalog, and fulfillment operations (inventory, shipment creation, returns) via a REST interface; sellers must hold a noon Seller Lab account and generate a service-account JWT credential to access.

Documented at https://noon-docs.noonpartners.dev/ — domains covered include Orders, Products, and Fulfillment. Access requires an active seller relationship; credentials (including test/sandbox credentials) are provisioned by noon account managers or self-service within Seller Lab. Third-party integrators (e.g., ChannelEngine, Omniful) have independently confirmed the JWT-based auth flow.

Payment gateway API for merchants to initiate, authenticate, authorize, and capture online payments; a separate surface from the marketplace seller API, operated under the noon Payments brand.

Documented at https://docs.noonpayments.com/ — covers direct-integration (merchant controls UI/UX, collects card details) and redirect flows. Operates under the noon Payments entity, which is the payments arm of noon.com, not a third party. Merchant onboarding required before live credentials are issued.

Direct HTTP probing of noon.com for /llms.txt, /agents.md, /.well-known/agent, /.well-known/ai-plugin.json, and /.well-known/ucp all timed out with DNS resolution failures — the domain blocked the sandbox environment's outbound requests entirely. No web search results reference noon.com publishing any self-declared agent discovery files. The check was structurally blocked, not completed, so not_found cannot be claimed; unable_to_verify is the accurate status.