Readiness
Readiness scores and right of reply
Scan any company's public pages for enterprise AI readiness, then claim your own page and correct a finding.
Transcript (30 seconds)
Readiness scores come only from public pages.
Scan any company and see twenty two checks.
Every finding shows a quote and its source.
Claim your own page with DNS or email.
Send corrections, and we rescan within days.
Before you start
- Nothing to scan. To claim a page: control of the domain's DNS or an email address at the domain
Steps
Scan a company
On Scan, enter a website. We read public pages only, with our crawler, and check 22 items across identity, assurance, data, deployment and agents.
Read the score
Each finding shows a quote and its source page. Anything we could not find says Not found in public pages, which says nothing about whether the company has it.
Claim your page
Add a DNS TXT record or confirm an email at your domain.
TXT promptcompute-verify=<token from the claim page>Send a correction
Link the public page that shows a finding. We review corrections within 2 business days and rescan from that page.
Show the badge
Claimed companies can embed the live grade.
<img src="https://promptcompute.ai/badge/example.com.svg" alt="AI readiness">
Use cases
Before a security review
- The situation
- A buyer will review your security pages next week.
- What to do
- Scan your site and fix what is Not found in public pages.
- What happens
- Your answers are on public pages before they ask.
A finding looks wrong
- The situation
- The scan missed your SOC 2 report page.
- What to do
- Claim the page and send a correction with the link.
- What happens
- We rescan from that page and update the score and changelog.
What you will see
A score page with a grade, every finding with its quote, and a changelog of changes.
It worked when
- The page shows Claimed after verification
- The changelog lists the correction and the new result
- The badge shows the current grade
Example output: Two findings on a score page
SOC 2 Type 2: Found
"Acme holds a SOC 2 Type II report..." (example.com/trust)
Customer-managed keys: Not found in public pagesIf something goes wrong
- The scan says the domain is not public
- We only scan public addresses. Check the spelling and that the site resolves.
- DNS verification fails
- TXT records can take time to appear. Check the value with a DNS lookup and try again.
- A check says Could not check
- robots.txt or the page limit kept us from the pages it needs, or the model was unavailable.