Glossier
glossier.com · E-commerce / D2C Retail modeTransactional
Overall = mean of Interrupt Score 100 and Machine-Readability 40.53 → 70 / 100. The badge is set by the Interrupt Score alone — how scoring works.
Confidence: Provisional (0.3) — Based on Tier 0/1 evidence only (passive checks, no live transaction attempt) — treat the number as a triage signal, not a verified outcome.
Custody posture hasn't been assessed yet.
Checkout flow not yet probed (Tier 2). For a transactional listing the purchase/checkout path is where interrupts actually bite — this score reflects only what passive and signup-level checks could observe, not a verified purchase.
Machine-Readability Score
Four check groups, equal weight: machine interfaces (OpenAPI, MCP server, llms.txt), browsing efficiency, element discoverability, and discovery/agent access (retrieval-bot robots.txt access, sitemap, schema.org). Each check is tagged with how strong the real-world evidence is that it changes agent behavior — proven, plausible, or emerging — grades are honesty labels, they never weight the score. A separate signal about ease of integration — it never enters the Interrupt Score or badge above.
- llms.txtemergingFound — www.glossier.com/llms.txt
- llms-full.txtemergingFound — www.glossier.com/llms-full.txt
- AGENTS.mdemergingFound — www.glossier.com/AGENTS.md
- A2A agent cardemergingNot provided
- MCP server (well-known or official registry)plausibleNot provided
- OpenAPI/Swagger specplausibleNot provided
- Rate-limit headersplausibleNot provided
- Structured JSON error responsesplausibleNot provided
- OAuth authorization-server metadata (RFC 8414)provenFound — www.glossier.com/.well-known/oauth-authorization-server
- API catalog (RFC 9727)emergingNot provided
- Agent-payment discovery (x402 / UCP)emergingUCP manifest: https://www.glossier.com/.well-known/ucp
- Lean HTML transfer sizeplausibleNot provided
- Manageable DOM sizeplausibleNot provided
- High content-to-markup densityplausibleNot provided
- Content readable without JS executionprovenraw HTML holds 406% of rendered text (13939 vs 3436 chars; threshold 40%)
- Clean-content alternate (RSS/Atom/feed/markdown)plausibleNot provided
- Serves markdown on Accept: text/markdownplausiblereturned text/markdown; charset=utf-8
- Interactive elements are semanticplausible415/428 semantic (97%); 13 div/span click targets
- Form fields have accessible namesplausible59/61 named (97%)
- Inputs carry autocomplete hintsplausibleNot provided
- WebMCP tools (modelContext API)emergingNot provided
- AI retrieval/search fetchers allowed (robots.txt)provenno retrieval-fetcher blocks in robots.txt
- Sitemap (indexability)plausibleFound — www.glossier.com/sitemap.xml
- schema.org JSON-LD in raw HTMLplausibleNot provided
- Content-Signal directives (robots.txt)emergingNot provided
- Web Bot Auth key directoryemergingNot provided
- Discovery Link headers on homepageemergingNot provided
- robots.txt AI-crawler accessplausibleno AI-crawler blocks in robots.txt
Findings
How scoring works →Interrupt tier: Low-Interrupt — no interrupts found; interrupt score 100 / 100. It alone drives the badge above; the headline Overall score blends it 50/50 with Machine-Readability.
Every tool starts at 100. Each interrupt found subtracts a penalty of base weight × timing × hardness × evidence — the multiplier values below come from the same rubric tables the score is computed with, so the arithmetic in this matrix reproduces the number exactly.
No interrupts found — no penalties, so the score stays at 100.
Score is in the 95–100 band, but the Zero-Interrupt badge additionally requires a completed live Tier-2 transaction and no hard-blocker finding — no live Tier-2 transaction has verified this flow end to end yet, so it is capped at Low-Interrupt.
Checked — nothing found
A check only turns green when a probe tier capable of detecting that interrupt actually ran and found nothing. Not tested ≠ clean.
- CAPTCHA / bot-challengeNone found — checked at Tier 0 (passive scan)
- “Contact sales” wall (no self-serve path)None found — checked at Tier 0 (passive scan)
- ToS clause banning automated/bot accessNone found — checked at Tier 0 (passive scan)
- Identity / KYC verificationNone found — checked at Tier 0 (passive scan)
Not yet tested
- Email OTP verificationNo probe tier that can detect this has run yet — unknown, not clean
- SMS / phone OTP verificationNo probe tier that can detect this has run yet — unknown, not clean
- Mandatory phone verification callNo probe tier that can detect this has run yet — unknown, not clean
- Mailed physical code (postal)No probe tier that can detect this has run yet — unknown, not clean
- Manual approval queueNo probe tier that can detect this has run yet — unknown, not clean
- Mandatory redirect to vendor’s own siteNo probe tier that can detect this has run yet — unknown, not clean
- SSO-only signup, no API-key issuanceNo probe tier that can detect this has run yet — unknown, not clean
- Rate-limit-triggered manual reviewNo probe tier that can detect this has run yet — unknown, not clean
- One-time account / payment-method provisioningNo probe tier that can detect this has run yet — unknown, not clean
- Crypto wallet / key-custody setupNo probe tier that can detect this has run yet — unknown, not clean
Agent-ready alternatives
Other E-commerce / D2C Retail tools in the same mode (transactional), ranked by Overall LLM-Friendliness — comparable to this listing because they share its usage mode.