# Jolie Skin Co: 70 point Door Gap
- Site: jolieskinco.com
- Scanned: 2026-09-08
- Scan type: Basic scan
- Business type: unknown
- Report: https://www.seconddoor.io/r/jolieskinco-k2zv54
- Scanner version: 12
A skincare site blocks automated clients at the door while serving real browsers normally, making it inaccessible to AI agents despite publishing signals of intent.
## Scores
| Measure | Score |
| --- | --- |
| Humans | 94/100 |
| Agents | 24/100 |
| Composite | 59/100 |
| Door Gap | 70 points |
The human score is the mean of the four human dimensions, the agent score the mean of the six agent dimensions, and the Door Gap the difference between them.
## What the machine actually did
The site refused automated access at jolieskinco.com, so the agent could not reach the site at all.
- blocked reach the site at all
- ok      find out whether machines are welcome
- ok      ask whether the door opens for requests carrying the AI crawlers' names
- ok      read the site's own guide for language models
- blocked find out what pages exist
- missing find a contact route for machines
- missing find a published agent interface
- missing find an agent plugin manifest
- missing find out whether verified agents are recognised
- missing read the homepage as data rather than as a page
- missing find a machine readable API spec
- missing read the developer documentation
- blocked read the prices without running JavaScript
- ok      walk the way a visitor would, to a signup form or a product
## Top issues
1. **/, /pricing turn the honest automated client away while serving a real browser, so the search crawlers that would cite the page are turned away by a rule about the client.** (machine_discoverability)
2. **Pricing is not machine-readable and cannot be discovered by agents without a real browser.** (commercial_rails)
3. **No API surface or integration documentation is published, leaving agents with no way to understand what actions they can take.** (programmatic_onboarding)
The evidence and the recommended fix for each are on the report page: https://www.seconddoor.io/r/jolieskinco-k2zv54
## Files generated from this scan
- **Let verified assistants through** at `notes`, 1 hour, developer. Verify: The next scan opens the homepage and the key pages in a real browser and under the search crawler names, and every one is served.
- **robots.txt rules for AI crawlers** at `/robots.txt`, 10 minutes, no developer needed. Verify: The next scan reads robots.txt and finds every search and agent crawler allowed, none of them kept off product or pricing paths.
- **Organization structured data** at `homepage`, 15 minutes, developer. Verify: The next scan reads Organization and WebSite nodes in the homepage JSON-LD and the structured data check passes.
- **Machine interfaces: where you stand** at `notes`, 10 minutes, no developer needed. Verify: The next scan finds the interface you published answering at its well-known path, and that check passes.
- **security.txt** at `/.well-known/security.txt`, 10 minutes, no developer needed. Verify: The next scan fetches /.well-known/security.txt as text and the security.txt check passes.
Each file is written from what this scan found on the site. The content is in the JSON once the evidence is opened: https://www.seconddoor.io/api/reports/jolieskinco-k2zv54
## The agent door
- **machine_discoverability** 43/100. The site publishes llms.txt and declares 152 robots.txt directives that allow major AI crawlers (ChatGPT, Claude, Gemini, Perplexity and others), but the homepage itself returns HTTP 403 to automated clients while serving a real browser.
- **programmatic_onboarding** 32/100. OAuth authorization metadata is published at the standard path, signalling how a remote MCP server would authenticate, but no API documentation is linked from the homepage and no OpenAPI spec exists at any of the 6 standard paths checked.
- **pricing_legibility** null/100. Could not verify: this scan did not reach the pages that would show it.
- **agent_aware_instrumentation** 20/100. OAuth authorization metadata is published, which is the remote MCP convention for how an agent would authenticate to a service. No MCP manifest exists at any of the 3 standard paths checked.
- **machine_fetchable_trust** 15/100. No security.txt file is published at /.well-known/security.txt. The homepage refuses automated clients outright with HTTP 403, blocking the most basic trust signal: that the site is willing to be read by machines at all.
- **commercial_rails** 10/100. OAuth authorization metadata is published, but pricing is walled behind HTTP 403 to automated clients. No machine-readable pricing exists at /pricing.md or elsewhere.
## The human door
- **steps_to_first_value** 95/100. The product is usable immediately with no signup required. A visitor lands on the site and can access the product without creating an account or providing any information.
- **required_fields** 100/100. There is no signup form and no account system. The entry path walk counted 0 fields and 0 required fields. Nothing is asked of a visitor before they can use the product.
- **verification_walls** 100/100. There is no account system and no verification step. The site requires no email confirmation, phone verification or identity check. A visitor accesses the product immediately upon arrival.
- **error_recovery** 80/100. There is no form to submit, so there are no validation errors to recover from. A visitor cannot make a mistake during signup because signup does not exist.
---
Scored by SecondDoor. Method: https://www.seconddoor.io/methodology
Scan another site: https://www.seconddoor.io
Rate an issue or this report: POST https://www.seconddoor.io/api/feedback, or the rate_fix tool on https://www.seconddoor.io/api/mcp