Skip to content

Clair

Gives retailers an endpoint that consumer shopping agents query for eligibility, offers and carts from the store's own systems.

CommerceAPIAgentsEnterprise
meetclair.co ↗
At a glanceswept 2026-10-12

not read yet

Use

For
Retailers wanting consumer buy-side agents to find, query and build carts from their catalog
Price
Price not read
Activity
Actively maintainedsite updated 7 days ago
Company
founding year not on record
Runs as
API
AlternativesSet it up for my teamIs Clair yours? Claim the card →
What people do with it
  • check whether a store is visible to consumer agents
  • answer product eligibility and offer questions for agents
  • hand off agent-brought shopper demand into a retailer-controlled cart
The companyeach fact with its source · read 2026-10-12
How a program reaches itfound, not claimed · read 2026-10-13
  • MCP serverco.meetclair/clairverified in the MCP registry
  • Stateanswers, 3 toolschecked 2026-10-13
  • Address to connectwww.meetclair.co/api/mcp

MCP server details →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Commerceby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

All Commerce tools →

Questions this page answers
  • What is Clair?

    Gives retailers an endpoint that consumer shopping agents query for eligibility, offers and carts from the store's own systems. It is listed in the Atlas under Commerce.

  • Who is Clair for?

    Retailers wanting consumer buy-side agents to find, query and build carts from their catalog

  • Do people use Clair?

    Little sign of use.

  • Is Clair still maintained?

    Actively maintained: site updated 7 days ago.

  • What are alternatives to Clair?

    In Commerce, by use: Mention Network, CartHappy, ShopHelp, Atomz AI, AI Shopping Optimizer, Curie.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.