Agent readiness

Agent readiness scans your public website, and any documentation and application addresses you add, the way AI agents meet them. Each finished scan gets a score from 0 to 100, a grade, and a list of every check it ran, with the evidence behind each result and the steps to fix what failed.

​

What it’s for

• Finding what stops agents. A scan shows where an agent can’t find your site, gets blocked, can’t read a page or can’t use your API.
• Fixing it. Every check explains what it looked at and how to fix it. You can copy a fix prompt for the findings you pick and hand it to the coding agent that works on your site.
• Tracking progress. Scans run again on a schedule, and you can compare any two finished scans to see what changed.

Open Agent readiness in the sidebar. The page shows your Latest score, the Active scan and the History of every scan.

​

What a scan covers

Every scan covers your workspace’s Website, the one you gave in Setup. An Admin can add documentation and application addresses in Settings; each is scanned together with the website. A scan looks at four layers: Every check in each layer is listed in The four layers and their checks.

​

Run a scan

A workspace runs one scan at a time. If a scan is already waiting, running or scoring, Scan now starts no new one and you see the active scan instead.

​

Scan on a schedule

Your first scan starts when someone selects Scan now or an Admin saves the settings with readiness on. After that, a new scan starts on its own once the number of days in Scan every has passed since the last scan started. With nothing changed, readiness is on and scans every 7 days. An Admin changes the schedule and the addresses on Agent readiness settings: Each added address must be a public http or https URL of at most 2,048 characters, with no user name, password, #fragment or credential in it. You can’t list the same address twice, or add your website again. Members can open Settings and read the same values, but only Admins can change them.

​

Read the overview

Latest score shows the score and grade of the latest finished scan, when it finished and How started. If a newer scan failed or was interrupted, the last finished score stays and the newer scan’s cause shows under it. History lists every scan, newest first: Sign-in required means the address scanned asked for sign-in before it answered, so nothing could be read. Time budget ran out means the scan stopped before it read everything it found; its results cover what it read.

​

Read a scan

A scan’s page is titled Scan of and the time it started. At the top it shows its State, How started, Coverage, how long it Took and the addresses Scanned. A scan that hasn’t ended says so; its score and findings appear once it finishes. Only a finished scan has a score.

​

Score and grade

The score is a whole number out of 100. The grade names it: Under the score you find:

• Summary: one line on the result, when one is available.
• Layers: each layer’s points out of what it can add to the score, or N/A when nothing in that layer counted, such as Payments for a product you don’t sell.
• Pages: how many pages the scan captured, and how many it read completely.
• Left out of the score: the checks that were Not applicable and those it Couldn’t check, each with its reason.

​

Checks

Checks lists every check, layer by layer. Each row shows the check’s Tier, its Result and its Points. The Tier is Required, Recommended or Emerging. Some checks also carry a badge:

• Emerging and Beta checks run and show, but never count. Their Points read Not counted.
• A Bonus check adds what it earns and never lowers the score.

A check that counts and fell short shows how many points the score would gain if it passed, such as +2 points if fixed. Start with the biggest gains. Open a check with the arrow at the start of its row to see:

• what it found on your site;
• What we checked;
• How to fix: the steps, what to watch out for, and a Reference link to the standard it follows;
• Findings: each thing it checked, with its result.

Other checks, below the checks, holds checks from before the current scoring method. They still run on every scan and show their findings, but never count toward the score.

​

Findings and evidence

A finding is one result of one check, usually for one address. Findings tables show the Check, the URL, the Result, a Reason code and the check’s Points. Under Other checks, Show findings filters by result: Failed, Couldn’t check, Not applicable, Passed or All. It opens on Failed, and the filter you pick stays in the page’s address, so you can share a view of one result. Open a finding to see:

• Parts: each part of the check, with its own result and reason;
• How to fix: the check’s fix steps;
• Evidence: one button per piece of evidence the finding rests on.

Select an Evidence button to open what the scan requested and what came back: the address requested and where it Landed on, the response Status, the Headers and the Body as it was kept, shown as text.

​

Copy a fix prompt

A fix prompt gathers the findings you pick, their evidence and the fix steps into one prompt for a coding agent. The prompt is built from what the scan recorded. Copying it doesn’t scan your site again. To clear what you picked, select the cross at the end of the bar.

​

See what the scan found

On a finished scan, select Resource map. It lists the pages the scan found, whether each was Fetched, and how many Links it has. Open a page to see what it links to; each link is marked Link, Sitemap or Reference. If the scan didn’t reach or read everything it found, the map says so, and pages or links may be missing.

​

Compare two scans

Below, Findings sorts every finding into four tabs:

• Appeared: in the later scan only.
• Disappeared: in the earlier scan only, often because you fixed it.
• Changed: in both, with a different result.
• Not compared: the check’s logic changed between the scans, so its results are not compared.

Select Open earlier scan or Open later scan to go to either scan.

​

Delete a scan

An Admin can delete a scan that has ended. Open it, select Delete scan, then confirm with Delete scan. You see Scan deleted. A deleted scan disappears from every view, comparison and fix prompt. It still counts as the last scan when deciding whether the next scheduled one is due.

​

The four layers and their checks

Not every check applies to every site. A check about your API applies only if you have an API, a payment check only if you sell something, and an MCP check only if you have an MCP server. A check that doesn’t apply shows Not applicable and is left out of the score. When the scan can’t tell whether a check applies, it shows Couldn’t check. Checks in the Emerging tier, and the one Beta check, run and show but never count toward the score. Checks marked Bonus add what they earn and never lower the score.

​

Discovery

Whether agents can find you.

​

Access

Whether agents can get into your pages and read them.

​

Usability

Whether agents can use your product once they are in.

​

Payments

Whether agents can pay you. These checks apply only if you sell something, and every one of them is a Bonus check.

​

Who can do what

Roles are set per organization. See People and roles.

​

Limits

• One scan runs at a time in each workspace.
• Up to 20 documentation and application URLs, together, besides your website.
• Scan every takes a whole number of days, 1 or more.
• A scan has a time budget. When it runs out, Coverage shows Time budget ran out and the results cover what the scan read.
• Only finished scans have a score, a resource map, fix prompts and comparisons.
• Only an ended scan can be deleted, and a deleted scan still counts toward the schedule.

​

Related