# Oura Ring: agent door 34, human door not measured
- Site: ouraring.com
- Scanned: 2026-09-08
- Scan type: Basic scan
- Business type: ecommerce
- Report: https://www.seconddoor.io/r/ouraring-vh74n3
- Scanner version: 15
A wearable retailer with prices visible but no product pages discoverable, blocking both agent and human shoppers from reaching checkout.
## Scores
| Measure | Score |
| --- | --- |
| Humans | not measured |
| Agents | 34/100 (5/6 dimensions) |
| Composite | 34/100 |
Agent door only. The human door could not be measured on this scan. A Door Gap needs both doors, so this scan does not report one.
## What the machine actually did
The agent got through 8 of 17 requests, but could not read the site's own guide for language models. It came up empty on 8 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 read the product catalogue as data
- ok      read a product page as data
- missing read the returns and shipping terms
- ok      walk the way a visitor would, to a signup form or a product
## Top issues
1. **No MCP manifest was found at the 3 standard paths checked, so an agent has no published machine door to this site.** (agent_aware_instrumentation)
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. **The /developer page publishes no API credentials, endpoints, code samples, or authentication documentation.** (programmatic_onboarding)
The evidence and the recommended fix for each are on the report page: https://www.seconddoor.io/r/ouraring-vh74n3
## Files generated from this scan
- **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.
- **Returns and refunds page** at `/returns`, 30 minutes, no developer needed. Verify: The next scan reads the returns policy page as text without JavaScript and finds it linked from a product page.
- **Shipping and delivery page** at `/shipping`, 30 minutes, no developer needed. Verify: The next scan reads the shipping policy page as text without JavaScript and finds it linked from a product page.
- **Agent checkout: where you stand** at `notes`, 10 minutes, no developer needed. Verify: The next scan finds a UCP manifest, a storefront MCP endpoint or another discovery file answering, and the checkout check passes.
- **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.
- **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.
- **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.
- **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/ouraring-vh74n3
## The agent door
- **machine_discoverability** 77/100. Robots.txt allows all major AI crawlers by name, a real browser is served normally, and a sitemap declares 80 URLs. However, no product pages could be found from the sitemap, homepage links, or a product feed, so the catalogue itself.
- **programmatic_onboarding** 10/100. No API surface exists. The /developer page was fetched and contains 25,100 characters of text but shows no credentials, endpoints, code samples, or authentication documentation.
- **pricing_legibility** 35/100. 15 prices appear in the homepage HTML itself, ranging from $0.60 to $10 and including some in KR currency. However, no product pages were reachable to verify whether prices carry currency codes, availability status, or return and shipping.
- **agent_aware_instrumentation** 8/100. No MCP manifest exists at any of the three standard paths checked. No UCP manifest, commerce platform detection, or paid crawl signals were found. An agent has no published route to integrate with this storefront.
- **machine_fetchable_trust** 40/100. No security.txt file is published at /.well-known/security.txt. The homepage responds to automated requests with HTTP 200 and serves content normally to a browser.
- **commercial_rails** not measured. Could not verify: this scan did not reach the pages that would show it.
## The human door
- **steps_to_first_value** not measured. Could not verify: this scan did not reach the pages that would show it.
- **required_fields** not measured. Could not verify: this scan did not reach the pages that would show it.
- **verification_walls** not measured. Could not verify: this scan did not reach the pages that would show it.
- **error_recovery** not measured. 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