aid: cooler-screens
name: CoolerX
description: '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. The platform pairs an AI "Intent Engine" for contextual
  targeting and conversion-funnel optimization with a Dynamic Content Engine for creative
  optimization, alongside campaign management, real-time measurement, and a data integration
  hub for product, price, promotion and context data. 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.
  CoolerX sells to retailers and brands through a demo and sales motion; as of this profile it
  publishes no public developer program, API reference, SDK, or machine-readable specification.'
image: https://www.coolerx.com/wp-content/uploads/2025/01/white-on-black-coolerX-logo.png
url: https://raw.githubusercontent.com/api-evangelist/cooler-screens/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-source-url: https://forgeglobal.com/cooler-screens_stock/
x-tier: stub
x-tier-reason: harvest
specificationVersion: '0.23'
created: '2026-08-09'
modified: '2026-08-12'
tags:
- Company
- Retail
- Retail Media
- Advertising
- Digital Signage
- In-Store Media
- Merchandising
- Artificial Intelligence
- Internet of Things
apis:
- name: CoolerX Website MCP Server
  description: >-
    A live, OAuth-protected Model Context Protocol endpoint served by CoolerX from its own
    apex host and discovered through the RFC 9728 protected-resource metadata document at
    https://coolerx.com/.well-known/oauth-protected-resource. It is published by the
    WordPress MCP Adapter running on the coolerx.com marketing site, which exposes that
    site''s WordPress Abilities API as MCP tools. It is a CONTENT surface for the website —
    NOT the CoolerX retail-media platform, Intent Engine or Dynamic Content Engine, which
    remain behind a sales gate at the unreachable api.coolerx.com and portal.coolerx.com.
    Anonymous tools/list returns 401 with a conforming Bearer challenge, so the tool list is
    not enumerated in this profile. The endpoint is undocumented on the CoolerX site and
    coolerx.com serves a TLS certificate that expired 2025-06-10, so a certificate-validating
    client cannot reach it.
  humanURL: https://coolerx.com/
  baseURL: https://coolerx.com/wp-json/mcp/mcp-oauth-server
  tags:
  - MCP
  - Agents
  - OAuth
  - Content Management
  - WordPress
  properties:
  - type: MCPServer
    url: mcp/cooler-screens-mcp.yml
  - type: Authentication
    url: authentication/cooler-screens-authentication.yml
  - type: OAuthScopes
    url: scopes/cooler-screens-scopes.yml
  - type: ErrorCatalog
    url: errors/cooler-screens-problem-types.yml
  - type: RateLimits
    url: rate-limits/cooler-screens-rate-limits.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/cooler-screens-domain-security.yml
- type: LLMsTxt
  url: llms/cooler-screens-llms.txt
- type: Website
  url: https://www.coolerx.com/
- type: PrivacyPolicy
  url: https://www.coolerx.com/privacy-policy/
- type: WellKnown
  url: well-known/cooler-screens-well-known.yml
- type: Conformance
  url: conformance/cooler-screens-conformance.yml
- type: Plans
  url: plans/cooler-screens-plans-pricing.yml
- type: RateLimits
  url: rate-limits/cooler-screens-rate-limits.yml
- type: ErrorCatalog
  url: errors/cooler-screens-problem-types.yml
- type: Authentication
  url: authentication/cooler-screens-authentication.yml
- type: OAuthScopes
  url: scopes/cooler-screens-scopes.yml
- type: MCPServer
  url: mcp/cooler-screens-mcp.yml
- type: Support
  url: https://coolerx.com/contact/
x-enrichment:
  date: '2026-08-12'
  status: enriched
  artifacts_added: 10
  pass: local-v1
  note: >-
    Round 2 overturned round 1. Round 1 recorded that every /.well-known/ path 404s and
    that CoolerX has no machine-readable surface. Two paths on the apex host in fact
    return 200 JSON — RFC 8414 OAuth authorization server metadata and RFC 9728 protected
    resource metadata — and the latter names a live, OAuth-gated MCP endpoint at
    https://coolerx.com/wp-json/mcp/mcp-oauth-server. Both documents are saved verbatim.
    The MCP surface belongs to the WordPress marketing site (MCP Adapter plugin over the
    WordPress Abilities API), not to the CoolerX retail-media platform, and every artifact
    in this repo says so. The retail-media platform itself remains sales-gated: no
    developer portal, no OpenAPI, no pricing, and api.coolerx.com / portal.coolerx.com
    still refuse TCP connections.