is-agentic.com agent readiness score

Scanned 8 Oct 2026 · 42s

Agent readiness report

CPartial assessment#5 of 16 scanned businesses

59 of 114 checks verified. Unverified capabilities earn no points.

Agents can read your homepage without JavaScript. Document and demonstrate: The provider documents explicit least-privilege permission scopes or equivalent restricted credentials.

Vercel Inc.

Score how ready a website is for AI agents, then get evidence and recommendations to improve it.

What agents found

132 checks from this scan
Loading evidence breakdown…
Needs work

Scoped permissions

Source-backed documentation judgment; capability execution was not tested.

Group by

Readiness checks

Audit mapExplore the layers, evidence and fixes132 checks

Competitive analytics

Across 16 scanned businesses

Leaderboard →
Scanned businesses16
Average score36
Grade B or above0
Your rank5

Layer profile

Layer profile for is-agentic.com against the directory average. You: Discovery 53.8, Access 67.7, Usability 43. Directory average: Discovery 38.4, Access 46.8, Usability 27.6.

Layer profile for is-agentic.com against the directory average
MeasureYouDirectory average
Discovery53.838.4
Access67.746.8
Usability4327.6

Community neighbors

Score distribution

  • 1
    0–9
  • 1
    10–19
  • 7
    20–29
  • 1
    30–39
  • 0
    40–49
  • 3
    50–59
  • 3
    60–69
  • 0
    70–79
  • 0
    80–89
  • 0
    90–100

Your range is highlighted · 16 businesses

Score over time

54/100

Latest scan · 8 Oct 2026

Rescan after your fixes to measure progress.
Scan details & exports

Scanned 8 Oct 2026, 5:58:31 pm AWST · ae-readiness-2.2.2

Public collection: 80 probes, 75 seconds, 12 MiB, six declared hosts. Homepage, sitemap, published OpenAPI JSON and large Markdown responses allow 2 MiB; others 256 KiB. Crawler reachability uses response-head samples; full content is measured separately. Sitemap sample: four maps and first 200 locations per map. Developer resources: two namespace indexes, three declared child indexes, six entry points and six targeted second-hop pages plus up to four decision-selected observed documentation reads. No sign-in, form submission, tool execution or payment. Browser and external discovery have independent bounded measurements. Protocol discovery and documented capability do not prove a completed customer task. The api ranking was inconclusive; bounded code-approved probes use the declared order. The mcp ranking was inconclusive; bounded code-approved probes use the declared order. Inspected conventional public files in 1 provider-linked repositories; no qualifying artifact was established in this bounded sample. Inspected conventional public files in 1 provider-linked repositories; no qualifying artifact was established in this bounded sample. A package registry sample was unavailable; independently verified package evidence remains valid. No official npm or PyPI SDK was attributed in the bounded sample; package absence remains unverified. No official SDK was attributed in the bounded npm, PyPI, RubyGems and Go samples; package absence remains unverified. Brand search did not complete its bounded provider sample; no negative search verdict was assigned. App and skill search did not complete its bounded provider sample; no negative search verdict was assigned. Public skills.sh collection was partial; independently retrieved listing and SKILL.md receipts remain valid. Browser rendering was incomplete; captured markup cannot establish the full interactive surface. Browser collection: 14 public-read attempts (96-request limit), 654394/6291456 received bytes. 4 Connection: connect-src-restricted Documentation review uses jev-1.13 closed span choices and independent verification. 4 of five decision calls used, including discovery. Confidence is model judgment. Documentation allocation retained 7 sources and 24123 characters; omitted sections cannot establish absence.