# CoolerX > CoolerX — formerly Cooler Screens — is an in-store retail media and merchandising technology > company that turns cooler doors, endcaps, checkout coolers and pharmacy fixtures into > IoT-connected digital screens. It is deployed with retailers including Kroger, Walgreens, > Giant Eagle's GetGo, Chevron and Western Union, and is built on Microsoft Azure with NVIDIA, > BOE, LG, Samsung and Foxconn as hardware and infrastructure partners. Provenance: this file was GENERATED by API Evangelist from the public CoolerX website and this repository's artifacts, first on 2026-08-09 and revised on 2026-08-12. CoolerX does not publish an llms.txt of its own (https://coolerx.com/llms.txt returned 404 on 2026-08-12). It is a third-party profile, not a document served by CoolerX. ## API surface CoolerX publishes **no developer program**: no developer portal, no API reference, no SDK, no webhook catalog, and no machine-readable specification (OpenAPI, AsyncAPI, GraphQL SDL, JSON Schema or Postman collection). Probed on 2026-08-12 against `coolerx.com`, all 404: `/developers/`, `/developer/`, `/api/`, `/docs`, `/api-docs`, `/redoc`, `/graphql`, `/openapi.json`, `/openapi.yaml`, `/swagger.json`, `/v1/openapi.json`, `/llms.txt`, `/pricing/`, `/status/`, `/security/`, `/trust/`, `/partners/`, `/integrations/`. The Yoast page sitemap lists 15 pages and none of them is a developer, docs or pricing page. There is no GitHub organization (`coolerx`, `coolerscreens`, `cooler-screens` all 404 on the GitHub API) and no first-party package on npm, PyPI or any other registry. `api.coolerx.com` and `portal.coolerx.com` both resolve in DNS to 13.67.211.230 but refuse connections on ports 80 and 443 from the public internet — private or partner-only endpoints, not a documented API. The only public route to the retail-media platform is the "Request a Demo" / contact sales motion. **Correction to the 2026-08-09 revision of this file**, which stated that every `/.well-known/` path returned 404. That was wrong. Two of them serve real documents: - `https://coolerx.com/.well-known/oauth-authorization-server` — **200**, RFC 8414 OAuth 2.0 Authorization Server Metadata. Issuer `https://coolerx.com`, authorization code + refresh token grants, PKCE S256, public clients, one scope: `mcp`. - `https://coolerx.com/.well-known/oauth-protected-resource` — **200**, RFC 9728 Protected Resource Metadata, naming `https://coolerx.com/wp-json/mcp/mcp-oauth-server` as the resource. `/.well-known/security.txt`, `/openid-configuration`, `/api-catalog`, `/ai-plugin.json`, `/agent-card.json` and `/agent.json` do all return 404. ## MCP surface (live, authenticated, undocumented) Following that discovery chain, CoolerX serves **two live Model Context Protocol endpoints** from its own apex host: - `https://coolerx.com/wp-json/mcp/mcp-oauth-server` — OAuth-gated. An anonymous `tools/list` returns **401** with a correct RFC 9728 challenge: `WWW-Authenticate: Bearer realm="https://coolerx.com", resource_metadata="https://coolerx.com/.well-known/oauth-protected-resource"`. - `https://coolerx.com/wp-json/mcp/mcp-adapter-default-server` — gated by the WordPress REST permission check; anonymous `tools/list` returns **401 `rest_forbidden`**. These are published by the WordPress MCP Adapter plugin running on the CoolerX marketing site (WordPress on Azure App Service, PHP 8.3), which exposes the site's WordPress Abilities API (`/wp-json/wp-abilities/v1/`, also 401) as MCP tools. **This is a content surface for the coolerx.com website — it is not the CoolerX retail-media platform, the Intent Engine or the Dynamic Content Engine.** No tool names or input schemas are recorded in this profile because `tools/list` and the abilities index are both gated and could not be read without credentials. Two caveats matter to any agent reading this. First, the endpoints are undocumented anywhere on the CoolerX site and carry `x-robots-tag: noindex`, so they read as plugin-default infrastructure rather than a deliberately published product. Second, `coolerx.com` serves a TLS certificate that expired 2025-06-10 — any client that validates certificates cannot complete a handshake, so the MCP surface is live but effectively unreachable in practice. ## Platform capabilities (as described by CoolerX, not as a callable contract) - **Intent Engine** — intent-coefficient algorithm, predictive models, within- and cross-category conversion funnel optimization, closed-loop machine learning, contextual targeting. - **Dynamic Content Engine** — retail and advertising content management for media, product merchandising, dynamic pricing and promotions, brand and seasonal messaging. - **Advertising platform** — self-serve or programmatic buying, audience targeting, campaign management, performance and creative A/B testing, real-time measurement reporting. - **Data and analytics** — reporting and advanced analytics, insights and recommendations ("co-pilot"), and a data integration hub for product, price and promo data plus context data (time, weather, geo, events). - **IoT and edge** — SaaS delivery, cloud services, 24/7 network, software and data integration monitoring, hardware-agnostic deployment. ## Pages - [Home](https://coolerx.com/): company overview. - [Technology](https://coolerx.com/technology/): platform components and partner list. - [Company](https://coolerx.com/company/): about CoolerX. - [Discovery Screen](https://coolerx.com/discovery-screen/): retail media starter solution. - [Success Stories](https://coolerx.com/success-stories/): retailer and brand case studies. - [Demo](https://coolerx.com/demo/): request a demo — the sales entry point. - [Contact](https://coolerx.com/contact/): contact form. - [Careers](https://coolerx.com/careers/): open roles. - [Privacy Policy](https://coolerx.com/privacy-policy/): consumer and website privacy. ## Artifacts in this profile - [Well-known probe](../well-known/cooler-screens-well-known.yml): every `/.well-known/` path probed, with the two 200 documents saved verbatim alongside it. - [MCP](../mcp/cooler-screens-mcp.yml): the two live MCP endpoints, their transports, their 401 challenges, and why the tool list is not enumerated. - [Authentication](../authentication/cooler-screens-authentication.yml): the OAuth 2.0 profile read from the authorization server metadata. - [OAuth scopes](../scopes/cooler-screens-scopes.yml): the single published scope, `mcp`. - [Conformance](../conformance/cooler-screens-conformance.yml): RFC 8414 / 9728 / 7636 / 7009 and MCP authorization pass; OIDC, RFC 9457, OpenAPI, AsyncAPI and A2A do not. - [Error catalog](../errors/cooler-screens-problem-types.yml): the two observed error envelopes. - [Plans and pricing](../plans/cooler-screens-plans-pricing.yml): zero published plans; enterprise contact-sales only. - [Rate limits](../rate-limits/cooler-screens-rate-limits.yml): zero documented limits and no rate-limit response headers on any observed response. - [Domain security](../security/cooler-screens-domain-security.yml): probed TLS, HSTS, DNSSEC, CAA, SPF and DMARC posture, including the expired apex certificate. ## Optional - No status page, changelog, roadmap, terms of service, trust center, security.txt, bug bounty, GitHub organization, published package, Postman collection or A2A agent card was found for CoolerX on 2026-08-12.