CanAgentUse tools

UCP Suite

Validate Universal Commerce Protocol discovery, then test product search, carts, checkout links, and merchant handoff flows.

MCP Playground

Connect to remote MCP servers, inspect tools and resources, test prompts, auth, headers, notifications, and JSON-RPC responses.

A2A Playground

Inspect Agent Cards, validate advertised endpoints, and prepare safe requests for agent-to-agent workflows.

Agent Website Viewer

Enter a public URL and see the roles, names, landmarks, controls, and blockers that shape how AI agents understand the page.

SCANNED
Jul 5, 2026, 4:39 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
85/100

OVERALL SCORE

Level 4, Mostly Ready

Good readiness for AI agents
AIDiscoverability89%Agent Easeof Use79%Security& Trust91%GEO, AIO, AEO68%SEO92%Performance76%Accessibility100%
  • AI Discoverability 89 out of 100
  • Agent Ease of Use 79 out of 100
  • Security & Trust 91 out of 100
  • GEO, AIO and AEO 68 out of 100
  • SEO 92 out of 100
  • Performance 76 out of 100
  • Accessibility 100 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

CanAgentUse Scanner | AI Agent Readiness Audits favicon

CanAgentUse Scanner | AI Agent Readiness Audits

Run AI agent readiness audits across crawler policy, structured data, performance, accessibility, API discovery, OAuth, MCP, WebMCP, agent skills, and commerce signals.

Open Agent View

Next step

Turn this report into a fix workflow

3 failed checks are ready to move into MCP or CLI remediation. Generate a repair prompt, connect the scanner to your coding agent, or open the integration docs before your next rescan.

Fix with MCP / CLI
Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
89
Mostly ready5700
Discoverability
100
Strong1200
Content Readiness
83
Mostly ready3100
Bot Access Control
86
Mostly ready1400
Agent Ease of Use
79
Mostly ready6452View details
API
85
Mostly ready1211View details
Auth
82
Mostly ready1500
MCP
70
Needs work500
Skill Discovery
81
Mostly ready1511View details
Agent Commerce
59
Needs work1430View details
Google Agentic Browsing
100
Strong300
GEO, AIO and AEO
68
Needs work1000
GEO Readiness
Not Applicable
Not Applicable300
AIO Readiness
Not Applicable
Not Applicable400
AEO Readiness
Not Applicable
Not Applicable300
SEO
92
Strong900
SEO
92
Strong900
Security & Trust
91
Strong2300
Security & Trust
91
Strong2300
Performance
76
Mostly ready1400
Performance
76
Mostly ready1400

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Agent Ease of UseAgent CommerceInformational

ACP - Agentic Commerce Protocol

ACP - Agentic Commerce Protocol failed at "Validate ACP discovery shape".

55 Fail

Needs attention

ACP - Agentic Commerce Protocol

Failed check
01

Issue

ACP discovery is missing protocol.

Details

02

Why it matters

ACP discovery lets agents find the seller's ACP API base URL, supported versions, transports, and stable services before attempting authenticated checkout-session negotiation.

Check name

ACP - Agentic Commerce Protocol

Score

45/100

Status

fail

Category

Agent Commerce

Maturity

Informational

Goal

Expose valid ACP discovery when this origin supports Agentic Commerce Protocol workflows.

Result

ACP - Agentic Commerce Protocol failed at "Validate ACP discovery shape".

Validation steps

  1. Validate ACP discovery shape

    ACP discovery is missing protocol.

    ACP discovery protocol metadata is invalid

    ACP discovery is missing protocol.

    ACP discovery is missing api_base_url.

    ACP discovery is missing transports array.

  2. Validate ACP endpoint and transports

    api_base_url is missing or unsafe.

    ACP API endpoint or transport metadata is unsafe or incomplete
  3. Validate ACP capabilities

    ACP discovery is missing capabilities.

    ACP capability declarations are invalid or unstable
Evidence log3 steps · 16 lines
Validate ACP discovery shape [fail]! ACP discovery is missing protocol.INFOValidate ACP discovery shape status="fail"INFOValidate ACP protocol object, name, date version, and supported_versions orderingFAILCheck protocol object and name actual={"hasProtocol":false} expected={"hasProtocol":true,"protocolName":"acp"}FAILCheck protocol version history actual={"supportedVersionCount":0,"supportedVersionsOrdered":true,"supportedVersionsEndWithCurrent":false} expected="date version with chronological supported_versions ending in current version"FAILACP discovery is missing protocol.Validate ACP endpoint and transports [fail]! api_base_url is missing or unsafe.INFOValidate ACP endpoint and transports status="fail"INFOValidate ACP API base URL and supported transportsFAILCheck safe HTTPS api_base_url actual=false expected=trueFAILCheck REST transport support actual=false expected=true transports=[] transportWarnings=[]FAILapi_base_url is missing or unsafe.Validate ACP capabilities [fail]! ACP discovery is missing capabilities.INFOValidate ACP capabilities status="fail"INFOValidate ACP services, extensions, intervention types, currencies, and localesFAILCheck capabilities object actual=false expected=trueFAILCheck stable ACP service declarations actual=[] expected="one or more known services such as checkout, orders, or delegate_payment"FAILCheck ACP capability values use stable service, extension, intervention, currency, and locale names actual="no compatibility warnings" expected="no unknown or unstable capability values" warnings=[]FAILACP discovery is missing capabilities.

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

A2A Agent Card failed at "Probe same-origin A2A endpoint".

26 Fail

Needs attention

A2A Agent Card

Failed check
01

Issue

The same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.

Details

02

Why it matters

A2A Agent Cards provide protocol-specific discovery for agent identity, skills, input and output modes, transport bindings, capabilities, and security requirements. Legacy A2A also used /.well-known/agent.json, so scanners must classify the card shape before reporting readiness.

Check name

A2A Agent Card

Score

74/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish a version-appropriate A2A Agent Card so A2A-compatible clients can discover agent skills and invoke the declared endpoint safely.

Result

A2A Agent Card failed at "Probe same-origin A2A endpoint".

Validation steps

  1. Review public-card safety

    The A2A Agent Card security declarations need review.

    A2A Agent Card exposes unsafe public metadata
  2. Probe same-origin A2A endpoint

    The same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.

    Advertised same-origin A2A endpoint did not answer a safe probe
Evidence log2 steps · 9 lines
Review public-card safety [warning]! The A2A Agent Card security declarations need review.INFOReview public-card safetyWARNCompare public secret findings actual=0 expected=0WARNSecurity declaration needs review warning="security scheme \"cookieSession\" is declared but not referenced by security requirements"WARNSecurity declaration needs review warning="security scheme \"bearerAuth\" is declared but not referenced by security requirements"WARNThe A2A Agent Card security declarations need review.Probe same-origin A2A endpoint [fail]! The same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.INFOProbe same-origin A2A endpointINFOProbe same-origin A2A endpoint when scanner policy allows itFAILA2A endpoint probe did not validate url="https://canagentuse.com/api/a2a" statusCode=404 rpcError={"code":-32601,"message":"Method not found. Use SendMessage.","data":{"availableActions":[{"action":"list_actions","description":"Return available CanAgentUse A2A actions and expected metadata."},{"action":"create_scan","description":"Create an agent-readiness scan for a URL. Optional auth enables private scans and plan-based rate limits.","metadata":{"skillId":"create_scan","url":"https://example.com","private":false,"checks":{"include":["robots.txt","sitemap","oauth-discovery","performance","accessibility"]}}},{"action":"get_scan_status","description":"Track scan progress and retrieve status/report readiness.","metadata":{"skillId":"get_scan_status","id":"task-id"}},{"action":"get_rate_limits","description":"Return current scan usage, remaining quota, reset time, plan key, and export capabilities.","metadata":{"skillId":"get_rate_limits"}},{"action":"get_report","description":"View report links and a report preview/snapshot when ready.","metadata":{"skillId":"get_report","id":"task-id"}},{"action":"list_agent_skills","description":"Return the published CanAgentUse Skill Markdown remediation catalog.","metadata":{"skillId":"list_agent_skills","count":53,"indexUrl":"/.well-known/agent-skills/index.json"}},{"action":"get_agent_skill","description":"Return one published CanAgentUse Skill Markdown remediation guide.","metadata":{"skillId":"get_agent_skill","slug":"robots-txt"}}]}}FAILThe same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.

Agent Ease of UseAPIEstablished

API Catalog

API Catalog failed at "Validate API catalog targets".

23 Fail

Needs attention

API Catalog

Failed check
01

Issue

API catalog target https://canagentuse.com/.well-known/agent.json (agent-json) advertised application/agent+json but returned application/json.

Details

02

Why it matters

API catalogs help agents find API endpoints, service descriptions, documentation, status resources, auth metadata, and related machine-readable contracts without guessing entry points.

Check name

API Catalog

Score

77/100

Status

fail

Category

API

Maturity

Established

Goal

Publish an API catalog for automated public API discovery using RFC 9727 when this origin exposes public APIs.

Result

API Catalog failed at "Validate API catalog targets".

Validation steps

  1. Validate API catalog media type

    The API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter.

    API catalog media type is not application/linkset+json
  2. Validate API catalog targets

    API catalog target https://canagentuse.com/.well-known/agent.json (agent-json) advertised application/agent+json but returned application/json.

    API catalog targets are unreachable or media types mismatch
Evidence log2 steps · 37 lines
Validate API catalog media type [warning]! The API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter.INFOValidate API catalog media typeWARNCompare API catalog media type actual="application/linkset+json" expected="application/linkset+json"WARNCompare RFC 9727 profile parameter actual=false expected=trueWARNThe API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter. status="warning"Validate API catalog targets [fail]! API catalog target https://canagentuse.com/.well-known/agent.json (agent-json) advertised application/agent+json but returned application/json.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsPASSAPI catalog target is reachable rel="profile" href="https://canagentuse.com/llms.txt#agent-and-api-discovery" statusCode=200 contentType="text/markdown; charset=utf-8" advertisedType="text/markdown"PASSAPI catalog target is reachable rel="service-desc" href="https://canagentuse.com/openapi.json" statusCode=200 contentType="application/json" advertisedType="application/vnd.oai.openapi+json"PASSAPI catalog target is reachable rel="service-doc" href="https://canagentuse.com/llms.txt" statusCode=200 contentType="text/markdown; charset=utf-8" advertisedType="text/markdown"FAILAPI catalog target failed validation rel="agent-json" href="https://canagentuse.com/.well-known/agent.json" statusCode=200 contentType="application/json" advertisedType="application/agent+json" typeMatches=falseFAILAPI catalog target failed validation rel="agent-json" href="https://canagentuse.com/agent.json" statusCode=200 contentType="application/json" advertisedType="application/agent+json" typeMatches=falsePASSAPI catalog target is reachable rel="agent-card" href="https://canagentuse.com/.well-known/agent-card.json" statusCode=200 contentType="application/json" advertisedType="application/json"FAILAPI catalog target fetch failed rel="mcp" href="https://canagentuse.com/.well-known/mcp/server-card.json" error="The operation was aborted due to timeout"PASSAPI catalog target is reachable rel="mcp" href="https://canagentuse.com/mcp.json" statusCode=200 contentType="application/json" advertisedType="application/json"PASSAPI catalog target is reachable rel="mcp" href="https://canagentuse.com/.well-known/mcp.json" statusCode=200 contentType="application/json" advertisedType="application/json"PASSAPI catalog target is reachable rel="agent-skills" href="https://canagentuse.com/.well-known/agent-skills/index.json" statusCode=200 contentType="application/json" advertisedType="application/json"PASSAPI catalog target is reachable rel="agents-json" href="https://canagentuse.com/agents.json" statusCode=200 contentType="application/json" advertisedType="application/json"PASSAPI catalog target is reachable rel="agents-json" href="https://canagentuse.com/.well-known/agents.json" statusCode=200 contentType="application/json" advertisedType="application/json"PASSAPI catalog target is reachable rel="openid-configuration" href="https://canagentuse.com/.well-known/openid-configuration" statusCode=200 contentType="application/json" advertisedType="application/json"FAILAPI catalog target failed validation rel="oauth-authorization-server" href="https://canagentuse.com/.well-known/oauth-authorization-server" statusCode=200 contentType="application/json; charset=utf-8" advertisedType="application/oauth-authz-server+json" typeMatches=falseFAILAPI catalog target failed validation rel="oauth-protected-resource" href="https://canagentuse.com/.well-known/oauth-protected-resource" statusCode=200 contentType="application/json; charset=utf-8" advertisedType="application/oauth-protected-resource+json" typeMatches=falsePASSAPI catalog target is reachable rel="agent-auth" href="https://canagentuse.com/auth.md" statusCode=200 contentType="text/markdown; charset=utf-8" advertisedType="text/markdown"PASSAPI catalog target is reachable rel="web-bot-auth" href="https://canagentuse.com/.well-known/http-message-signatures-directory" statusCode=200 contentType="application/http-message-signatures-directory+json" advertisedType="application/http-message-signatures-directory+json"PASSAPI catalog target is reachable rel="webmcp" href="https://canagentuse.com/.well-known/webmcp.json" statusCode=200 contentType="application/webmcp+json; charset=utf-8" advertisedType="application/webmcp+json"PASSAPI catalog target is reachable rel="indexnow-key" href="https://canagentuse.com/52e163cb29f13843a5b58d2854fe46c9.txt" statusCode=200 contentType="text/plain; charset=utf-8" advertisedType="text/plain"PASSAPI catalog target is reachable rel="ai-policy" href="https://canagentuse.com/ai.txt" statusCode=200 contentType="text/plain; charset=utf-8" advertisedType="text/plain"PASSAPI catalog target is reachable rel="tdmrep" href="https://canagentuse.com/.well-known/tdmrep.json" statusCode=200 contentType="application/json; charset=utf-8" advertisedType="application/json"PASSAPI catalog target is reachable rel="commerce-non-support" href="https://canagentuse.com/.well-known/acp" statusCode=200 contentType="application/json" advertisedType="application/json"PASSAPI catalog target is reachable rel="commerce-non-support" href="https://canagentuse.com/.well-known/acp.json" statusCode=200 contentType="application/json" advertisedType="application/json"PASSAPI catalog target is reachable rel="commerce-non-support" href="https://canagentuse.com/.well-known/ucp" statusCode=200 contentType="application/json" advertisedType="application/json"PASSAPI catalog target is reachable rel="rate-limit-status" href="https://canagentuse.com/api/scans" statusCode=200 contentType="application/json" advertisedType="application/json"FAILAPI catalog target failed validation rel="docs" href="https://canagentuse.com/docs" statusCode=404 contentType="text/html; charset=utf-8" advertisedType="text/html" typeMatches=truePASSAPI catalog target is reachable rel="api" href="https://canagentuse.com/api" statusCode=200 contentType="text/html; charset=utf-8" advertisedType="text/html"PASSAPI catalog target is reachable rel="sitemap" href="https://canagentuse.com/sitemap.xml" statusCode=200 contentType="application/xml; charset=utf-8" advertisedType="application/xml"PASSAPI catalog target is reachable rel="robots" href="https://canagentuse.com/robots.txt" statusCode=200 contentType="text/plain; charset=utf-8" advertisedType="text/plain"FAILCompare API catalog target failure count actual=6 expected=0FAILAPI catalog target https://canagentuse.com/.well-known/agent.json (agent-json) advertised application/agent+json but returned application/json.

Sign in to see 35 other issues and the full report

Create a free account to unlock every issue, evidence details, exports, and higher free limits.

Email code

Fix with MCP or CLI

Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.

Fix with MCP / CLI

Score history

Public scan score over time

Public reports for this website origin. Select any point or report link to open that canonical report.

6 reports
Public score history report links
Scan dateScoreReadinessReport
79/100Level 4, Mostly ReadyView report
96/100Level 5, Agent-ReadyView report
96/100Level 5, Agent-ReadyView report
98/100Level 5, Agent-ReadyView report
97/100Level 5, Agent-ReadyView report
85/100Level 4, Mostly ReadyCurrent report