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 scanUnclassified · Marketing site/Scanned 8 Sept 2026, 13:48 UTC/1 browser pass
A browser automation wall blocks assistant shopping while the API surface remains undocumented and inaccessible to agents.
Older scan
This report was produced by an earlier version of the scanner. Some findings may not match how the site is measured now.
Severe. Your human funnel and your agent funnel are different products.
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.
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 behind every number above. Not measured is not zero.
Machine discoverability
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.
4 observations recorded.
Programmatic onboarding
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.
3 observations recorded.
Pricing legibility
Could not verify: this scan did not reach the pages that would show it.
1 observation recorded.
Agent-aware instrumentation
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.
4 observations recorded.
Machine-fetchable trust
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.
2 observations recorded.
Commercial rails
.
2 observations recorded.
Steps to first value
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.
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 14.
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.