# Ora: agent door 77, human door not measured
- Site: ora.ai
- Scanned: 2026-09-10
- Scan type: Basic scan
- Business type: unknown
- Report: https://www.seconddoor.io/r/ora-y4qw64
- Scanner version: 49
- Scanner release: c49d1def936f56a5ab0871f38c5e6412433ec37a
- Scoring methodology: 1
- Evidence schema: 1
0 human and 3 agent dimensions measured from the pages checked; remaining dimensions are not scored.
## Scores
| Measure | Score |
| --- | --- |
| Humans | not measured |
| Agents | 77/100 (3/6 dimensions) |
| Composite | 77/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 scanner recorded successful observations for 10 of 11 checks, but could not find a contact route for machines. 2 checks could not be measured; see the report limitations.
- 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
- ok      read the site's own guide for language models
- ok      find out what pages exist
- missing find a contact route for machines
- ok      find an MCP manifest at the standard paths checked
- ok      find an agent plugin manifest
- ok      find out whether verified agents are recognised
- ok      read the homepage as data rather than as a page
- ok      read the developer documentation
## What a visitor meets
1. **Entry observation** (observed). Reached the linked “Contact” page. No form was submitted, payment made or account created; this route has no applicable signup or checkout score.
## Top issues
1. **No valid security.txt was identified at /.well-known/security.txt.** (machine_fetchable_trust)
The evidence and the recommended fix for each are on the report page: https://www.seconddoor.io/r/ora-y4qw64
## Files generated from this scan
- **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/ora-y4qw64
## The agent door
- **machine_discoverability** 90/100. Robots.txt blocks 2 training crawlers, a choice about model weights rather than about buyers. On its first visit, our browser read the homepage. No user agent rule refused the tested retrieval crawler names. A sitemap listing 1723 URLs.
- **programmatic_onboarding** not measured. Not applicable to this scanned surface.
- **pricing_legibility** not measured. Not applicable to this scanned surface.
- **agent_aware_instrumentation** 100/100. An MCP manifest is published. An ai-plugin.json is published. Web Bot Auth signals are published, so verified agents can be recognised. Robots.txt explicitly names 9 AI crawler tokens; policies differ by token.
- **machine_fetchable_trust** 40/100. No security.txt was identified at the checked path. The homepage answers automated requests.
- **commercial_rails** not measured. Not applicable to this scanned surface.
## The human door
- **steps_to_first_value** not measured. Not applicable to this scanned surface.
- **required_fields** not measured. Not applicable to this scanned surface.
- **verification_walls** not measured. Not applicable to this scanned surface.
- **error_recovery** not measured. Not applicable to this scanned surface.
---
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