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 business · Marketing site/Scanned 8 Sept 2026, 14:48 UTC/1 browser pass
Stripe publishes prices only after JavaScript runs, blocking agents from computing cost before signup.
Older scan
This report was produced by an earlier version of the scanner. Some findings may not match how the site is measured now.
Wide. Agents are dropping out well before humans do.
Ordered by what the evidence says is costing most. Written for whoever owns the site, not whoever builds it.
3 pieces of evidence and the recommended fix are recorded for this issue, with pricing page 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 behind every number above. Not measured is not zero.
Machine discoverability
No AI crawler is blocked by robots.txt; the homepage is served to automated clients; llms.txt is published with 380 lines of guidance; a sitemap lists 52 URLs; 7 schema.org types appear in the homepage JSON-LD.
4 observations recorded.
Programmatic onboarding
API credentials are documented, authentication is documented, code samples are provided.
3 observations recorded.
Pricing legibility
The pricing page renders 52 prices after JavaScript runs, but the raw HTML contains zero prices. A machine that fetches the page without rendering JavaScript sees no cost information at all.
1 observation recorded.
Agent-aware instrumentation
No MCP manifest, developer documentation describes an API, but only in prose.
4 observations recorded.
Machine-fetchable trust
security.txt is published at /.well-known/security.txt with a contact route for machines. The homepage answers automated HTTP requests with a 200 status.
2 observations recorded.
Commercial rails
The pricing page routes to sales without publishing any prices.
2 observations recorded.
Steps to first value
The signup page is 2 steps from the homepage via the 'Get started' call to action. The browser received an automated traffic challenge when attempting to read the form, so the number of fields, required fields, and validation attributes.
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 10 of 15.
The agent got through 10 of 15 requests, but could not find a published agent interface. It came up empty on 4 other checks too. That is enough missing for a machine to give up before it reaches a purchase.