# Peloton: 47 point Door Gap
- Site: peloton.com
- Scanned: 2026-09-08
- Scan type: Basic scan
- Business type: b2b_saas
- Report: https://www.seconddoor.io/r/peloton-zmuvw4
- Scanner version: 12
A fitness hardware and content platform blocks automated signup and publishes no pricing, API access, or developer documentation.
## Scores
| Measure | Score |
| --- | --- |
| Humans | 80/100 |
| Agents | 33/100 |
| Composite | 57/100 |
| Door Gap | 47 points |
| Percentile | 29th |
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 agent got through 7 of 15 requests, but could not read the site's own guide for language models. It came up empty on 7 other checks too. That is enough missing for a machine to give up before it reaches a purchase.
- ok      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
- missing read the site's own guide for language models
- ok      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
- ok      read the homepage as data rather than as a page
- missing find a machine readable API spec
- missing read the developer documentation
- ok      read the prices without running JavaScript
- missing find a comparison page worth citing
- ok      walk the way a visitor would, to a signup form or a product
## Top issues
1. **No comparison or alternatives page exists, which is the page an assistant cites when a buyer asks it to shortlist vendors.** (machine_discoverability)
2. **No developer documentation is linked from the homepage, in raw HTML or the rendered page, so integration starts with a search engine.** (programmatic_onboarding)
3. **No OpenAPI specification was found at the 6 standard paths checked, so a client must be written from prose instead of generated.** (programmatic_onboarding)
The evidence and the recommended fix for each are on the report page: https://www.seconddoor.io/r/peloton-zmuvw4
## Files generated from this scan
- **A comparison page brief** at `/compare/peloton-vs-competitor`, 3 hours, no developer needed. Verify: The next scan finds a comparison page listed in the sitemap or linked from the homepage, and reads its text without JavaScript.
- **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.
- **llms.txt** at `/llms.txt`, 15 minutes, no developer needed. Verify: The next scan fetches /llms.txt as text and the llms.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/peloton-zmuvw4
## The agent door
- **machine_discoverability** 86/100. Robots.txt explicitly names and allows 14 AI crawlers including GPTBot, Claude, Perplexity and others. A real browser is served the page normally. Sitemap lists 76 URLs. Homepage carries 8 schema.org types.
- **programmatic_onboarding** 10/100. No API documentation is linked from the homepage or discoverable in raw HTML. No OpenAPI spec exists at any of the 6 standard paths checked. An agent cannot obtain credentials or understand integration without a sales conversation.
- **pricing_legibility** null/100. Could not verify: this scan did not reach the pages that would show it.
- **agent_aware_instrumentation** 20/100. Robots.txt names 14 AI crawlers and allows them, showing awareness of agent traffic. No MCP manifest exists at any of the 3 standard paths. No ai-plugin.json or Web Bot Auth signals are published.
- **machine_fetchable_trust** 40/100. No security.txt file is published at /.well-known/security.txt. The homepage answers automated requests normally. No vulnerability disclosure policy or machine-readable trust signals are available to agents evaluating the vendor.
- **commercial_rails** 10/100. The signup path is blocked by an automated traffic challenge that a real browser can pass but an agent cannot. No pricing.md or OAuth authorization metadata is published.
## The human door
- **steps_to_first_value** 80/100. The signup call to action is 2 steps from the homepage. The signup page itself was blocked by an automated traffic challenge, so the form fields and verification steps could not be counted. A human following the same link reaches the form.
- **required_fields** null/100. Could not verify: this scan did not reach the pages that would show it.
- **verification_walls** null/100. Could not verify: this scan did not reach the pages that would show it.
- **error_recovery** null/100. Could not verify: this scan did not reach the pages that would show it.
---
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