# Atlassian: 50 point Door Gap
- Site: atlassian.com
- Scanned: 2026-09-08
- Scan type: Basic scan
- Business type: unknown
- Report: https://www.seconddoor.io/r/atlassian-pyrzcf
- Scanner version: 12
A browser automation wall blocks assistant shopping while the API surface remains undocumented and inaccessible to agents.
## Scores
| Measure | Score |
| --- | --- |
| Humans | 80/100 |
| Agents | 30/100 |
| Composite | 55/100 |
| Door Gap | 50 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 agent got through 8 of 14 requests, but could not find a published agent interface. It came up empty on 5 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
- ok      read the site's own guide for language models
- ok      find out what pages exist
- ok      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
- ok      read the prices without running JavaScript
- ok      walk the way a visitor would, to a signup form or a product
## Top issues
1. **No developer documentation is linked from the homepage, in raw HTML or the rendered page, so integration starts with a search engine.** (programmatic_onboarding)
2. **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)
3. **No API surface, credentials, endpoints or code samples are published in the developer documentation.** (programmatic_onboarding)
The evidence and the recommended fix for each are on the report page: https://www.seconddoor.io/r/atlassian-pyrzcf
## 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.
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/atlassian-pyrzcf
## The agent door
- **machine_discoverability** 38/100. Atlassian publishes a sitemap with 924 URLs and llms.txt to declare intent for AI crawlers, and robots.txt permits major AI agents by name. However, no schema.org markup appears on the homepage, and a real browser is refused with an.
- **programmatic_onboarding** 10/100. No API credentials, endpoints, code samples, authentication documentation or self-serve key issuance were found in the developer documentation at developer.atlassian.com or /developers.
- **pricing_legibility** null/100. Could not verify: this scan did not reach the pages that would show it.
- **agent_aware_instrumentation** 8/100. No MCP manifest was published at any of the 3 standard paths checked (/.well-known/mcp.json, /.well-known/mcp, /mcp.json). No Web Bot Auth signals or ai-plugin.json were found.
- **machine_fetchable_trust** 85/100. security.txt is published at /.well-known/security.txt with a contact route for machines. The homepage serves HTTP 200 to automated requests in 1,006ms.
- **commercial_rails** 10/100. .
## The human door
- **steps_to_first_value** 80/100. A Get Started link reaches the signup page in 2 steps from the homepage. However, a real browser attempting to access the signup form is refused with an automated traffic challenge, so the form itself could not be read or counted.
- **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