Some cookies are necessary for SecondDoor to work. Others are optional, and tell us how the site and the product are used. Accept all, or decline all optional ones. Without a selection, nothing optional is set. More in our cookie policy.
Basic scanSoftware and storefront · Storefront property/Scanned 8 Sept 2026, 16:15 UTC/1 browser pass
A hybrid storefront and software platform with no published API surface, no pricing visibility, and no agent checkout path.
Ordered by what the evidence says is costing most. Written for whoever owns the site, not whoever builds it.
1 piece of evidence and the recommended fix are recorded for this issue, with /compare/oura-vs-competitor written from your own pages.
This is a basic scan, so it raises the three issues the deterministic evidence supports. A deep scan sends two agents over the site and raises up to ten, each with cited evidence and the screens to prove it.
A deep scan walks the site with two agents, records cited evidence and screenshots, and keeps a mission timeline. It comes with the paid plans. Making an account costs nothing and gives you one basic scan a month.
The score and the audit trail stay public. The evidence and the files open with an account.
The audit trail. Not measured is not zero.
Machine discoverability
Oura allows all major AI crawlers in robots.txt, serves pages normally to automated clients, publishes a sitemap with 80 URLs, and includes Organization schema.
4 observations recorded.
Programmatic onboarding
The developer documentation at /developer contains 24,654 characters of text but no API credentials, endpoints, code samples, authentication documentation or self-serve key issuance. No GraphQL endpoint is published.
3 observations recorded.
Pricing legibility
The pricing page at /oura-preferred-pricing says 'starting at' once but provides no figure after it. No prices appear in the raw HTML or after rendering.
2 observations recorded.
Agent-aware instrumentation
No MCP manifest is published at any of the three standard paths checked. No ai-plugin.json, Web Bot Auth signals, or agent-specific instrumentation is present.
4 observations recorded.
Machine-fetchable trust
No security.txt is published at /.well-known/security.txt. The homepage responds normally to automated requests and no bot walls are present on key pages, but the absence of security contact information and vulnerability disclosure policy.
3 observations recorded.
Commercial rails
.
4 observations recorded.
Steps to first value
Could not verify: this scan did not reach the pages that would show it.
1 observation recorded.
Required fields
Could not verify: this scan did not reach the pages that would show it.
1 observation recorded.
Verification walls
Could not verify: this scan did not reach the pages that would show it.
1 observation recorded.
Error recovery
Could not verify: this scan did not reach the pages that would show it.
1 observation recorded.
It got through 8 of 18.
The agent got through 8 of 18 requests, but could not read the site's own guide for language models. It came up empty on 9 other checks too. That is enough missing for a machine to give up before it reaches a purchase.