Assess the public site
Run a Cloudflare Agent Readiness assessment without requiring access to the customer’s Cloudflare account.
Agent readiness, made actionable
AgentReadyToday turns a technical assessment into a controlled improvement workflow. Understand what agents can discover, prioritize what matters, approve supported fixes, and verify the result.
Public assessment first. No site changes without authorization and explicit approval.
Assessment status
Beyond another score
A scan should lead somewhere useful. AgentReadyToday connects assessment, explanation, planning, controlled remediation, and verification in one traceable path.
Run a Cloudflare Agent Readiness assessment without requiring access to the customer’s Cloudflare account.
Translate technical checks into a clearer score, categories, evidence, and practical guidance.
Separate findings that need attention from checks that already pass, then build a reviewable remediation plan.
For supported fixes, request limited authorization and show the exact proposed change before anything runs.
Verify an applied change, rescan the public site, and compare the new result with the baseline.
The working flow
Your first assessment does not require customer Cloudflare access. Authorization enters the workflow later, only when a supported automatic fix is available and you choose to apply it.
Add a public URL. The initial assessment works without a customer Cloudflare token.
See normalized categories, findings, evidence, guidance, and a plain-language explanation.
Follow manual guidance or, where a fix is supported, connect Cloudflare with limited permissions.
Review the proposed provider operation and explicitly approve the unchanged plan.
Confirm the live outcome and compare the post-change scan with the original baseline.
Controls that matter
Public assessments use AgentReadyToday’s own scanner credential, separate from optional customer remediation access.
Customers are directed to grant only the permissions needed for supported Cloudflare operations.
Supported operations are shown before approval. A changed plan requires approval again.
Connected provider credentials are encrypted server-side and are not returned to the browser.
Site-changing events record their actor, target, outcome, request identifier, and timestamp.
Applied supported fixes are checked against the live site and followed by a fresh assessment.
Cloudflare-first, not Cloudflare-only
The current product supports Cloudflare Agent Readiness analysis and a limited set of approved Cloudflare remediations. The architecture is intended to support more site platforms, APIs, agent capabilities, and connector ecosystems over time. Those adapters are planned, not current production capabilities.
Start with the evidence