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, 1:38 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
68/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability67%Agent Easeof Use71%Security& Trust62%GEO, AIO, AEO58%SEO92%Performance76%Accessibility69%
  • AI Discoverability 67 out of 100
  • Agent Ease of Use 71 out of 100
  • Security & Trust 62 out of 100
  • GEO, AIO and AEO 58 out of 100
  • SEO 92 out of 100
  • Performance 76 out of 100
  • Accessibility 69 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

The Context Layer for AI Agents | Airbyte favicon

The Context Layer for AI Agents | Airbyte

Airbyte turns every source into a queryable Context Store, giving AI agents the live context they need to reason across systems.

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
67
Needs work3310View details
Discoverability
67
Needs work800
Content Readiness
77
Mostly ready2200
Bot Access Control
58
Needs work310View details
Agent Ease of Use
71
Needs work4432View details
API
87
Mostly ready1100
Auth
65
Needs work1111View details
MCP
48
Priority fix100
Skill Discovery
62
Needs work500
Agent Commerce
66
Needs work1321View details
Google Agentic Browsing
100
Strong300
GEO, AIO and AEO
58
Needs work700
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable200
SEO
92
Strong900
SEO
92
Strong900
Security & Trust
62
Needs work1300
Security & Trust
62
Needs work1300
Performance
76
Mostly ready1600
Performance
76
Mostly ready1600

Prioritized recommendations

Issues ranked by score impact

3 items need attention

AI DiscoverabilityBot Access ControlEstablished

AI bot rules in robots.txt

AI bot rules in robots.txt failed at "Classify AI crawler rules".

69 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

No explicit User-agent rules were found for major AI crawler tokens.

Details

02

Why it matters

AI crawler product tokens have different meanings. Explicit robots.txt groups make training, search, and retrieval access policy auditable for compliant crawler operators.

Check name

AI bot rules in robots.txt

Score

31/100

Status

fail

Category

Bot Access Control

Maturity

Established

Goal

Declare deliberate robots.txt rules for major AI training, AI search, user-triggered, and dataset crawlers.

Result

AI bot rules in robots.txt failed at "Classify AI crawler rules".

Validation steps

  1. Classify AI crawler rules

    No explicit User-agent rules were found for major AI crawler tokens.

    robots.txt lacks explicit AI crawler rules
Evidence log1 step · 6 lines
Classify AI crawler rules [fail]! No explicit User-agent rules were found for major AI crawler tokens.INFOClassify AI crawler rulesINFOParsing User-agent groups and Allow/Disallow records for known AI crawler tokens evaluatedPath="/"INFOEvaluating exact User-agent matches before wildcard fallback exactAiPolicyCount=0 totalCrawlerTokens=18FAILNo explicit AI crawler User-agent groups were found examplesExpected=["GPTBot","OAI-SearchBot","ClaudeBot","Google-Extended","CCBot"]FAILCompare explicit AI crawler coverage actual=0 expected="> 0 explicit non-search AI crawler policies" missingTokens=["GPTBot","OAI-SearchBot","ChatGPT-User","ClaudeBot","Claude-SearchBot","Claude-User","Google-Extended","Applebot-Extended","Amazonbot","Amzn-SearchBot","Amzn-User","PerplexityBot"]INFOResolved effective root-path policy for crawler tokens blocked=0 allowed=21 unspecified=0

Agent Ease of UseAuthEmerging recommendation

Auth.md Agent Registration

Auth.md Agent Registration failed at "Fetch and validate /auth.md".

52 Fail

Needs attention

Auth.md Agent Registration

Failed check
01

Issue

auth.md response did not match Auth.md v1 agent registration guidance. missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance; missing credential usage, expiry, error, or revocation guidance.

Details

02

Why it matters

Human login and signup flows are often opaque to agents. Auth.md gives automated clients a stable registration contract instead of forcing them to scrape docs, automate browser forms, or guess credential flows.

Check name

Auth.md Agent Registration

Score

48/100

Status

fail

Category

Auth

Maturity

Emerging recommendation

Goal

Publish Auth.md v1 metadata so agents can discover how to register, claim a user, and obtain credentials.

Result

Auth.md Agent Registration failed at "Fetch and validate /auth.md".

Validation steps

  1. Fetch and validate /auth.md

    auth.md response did not match Auth.md v1 agent registration guidance. missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance; missing credential usage, expiry, error, or revocation guidance.

    /auth.md is missing or not usable as agent registration guidance
  2. Validate Auth.md authorization metadata

    OAuth authorization-server metadata did not include usable Auth.md v1 fields. agent_registration_endpoint issues: [{"field":"agent_registration_endpoint","issue":"Expected an absolute HTTPS URL."}]; missing credential_types_supported.

    Authorization-server metadata lacks Auth.md v1 fields
Evidence log2 steps · 16 lines
Fetch and validate /auth.md [fail]! auth.md response did not match Auth.md v1 agent registration guidance. missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance; missing credential usage, expiry, error, or revocation guidance.INFOFetch and validate /auth.mdINFOFetch Auth.md-related resource path="/auth.md" statusCode=200 contentType="text/markdown; charset=utf-8" bytes=1537FAILCompare response Content-Type with expected Auth.md media type actual=true expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILCompare Auth.md content length actual=1445 expected=">= 80 characters"WARNAuth.md validation warning warning="missing agent_verified/user_claimed or claim ceremony guidance"WARNAuth.md validation warning warning="missing credential usage, expiry, error, or revocation guidance"FAILAuth.md validation issue issue="auth.md response did not match Auth.md v1 agent registration guidance. missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance; missing credential usage, expiry, error, or revocation guidance."FAILauth.md response did not match Auth.md v1 agent registration guidance. missing Auth.md credential type guidance; missing agent_verified/user_claimed or claim ceremony guidance; missing credential usage, expiry, error, or revocation guidance.Validate Auth.md authorization metadata [warning]! OAuth authorization-server metadata did not include usable Auth.md v1 fields. agent_registration_endpoint issues: [{"field":"agent_registration_endpoint","issue":"Expected an absolute HTTPS URL."}]; missing credential_types_supported.INFOValidate Auth.md authorization metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-authorization-server" statusCode=200 contentType="application/json; charset=utf-8" bytes=1120WARNCompare response Content-Type with expected Auth.md media type actual=true expected=trueWARNCompare Auth.md/OAuth metadata validation result actual=false expected=trueWARNCompare supported credential type count actual=0 expected="> 0"WARNAuth.md validation issue issue="OAuth authorization-server metadata did not include usable Auth.md v1 fields. agent_registration_endpoint issues: [{\"field\":\"agent_registration_endpoint\",\"issue\":\"Expected an absolute HTTPS URL.\"}]; missing credential_types_supported."WARNOAuth authorization-server metadata did not include usable Auth.md v1 fields. agent_registration_endpoint issues: [{"field":"agent_registration_endpoint","issue":"Expected an absolute HTTPS URL."}]; missing credential_types_supported.

Agent Ease of UseAgent CommerceInformational

ACP - Agentic Commerce Protocol

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

45 Fail

Needs attention

ACP - Agentic Commerce Protocol

Failed check
01

Issue

protocol.version must be a YYYY-MM-DD date string.

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

55/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

    protocol.version must be a YYYY-MM-DD date string.

    ACP discovery protocol metadata is invalid

    protocol.version must be a YYYY-MM-DD date string.

    protocol.supported_versions must be a non-empty array.

    transports must include rest.

  2. Validate ACP endpoint and transports

    transports does not include rest.

    ACP API endpoint or transport metadata is unsafe or incomplete

    Transport "https" is not recognized for this ACP check version.

  3. Validate ACP capabilities

    Service "discovery" is not recognized for this ACP check version.

    ACP capability declarations are invalid or unstable

    Service "discovery" is not recognized for this ACP check version.

    Service "documentation" is not recognized for this ACP check version.

Evidence log3 steps · 16 lines
Validate ACP discovery shape [fail]! protocol.version must be a YYYY-MM-DD date string.INFOValidate ACP discovery shape status="fail"INFOValidate ACP protocol object, name, date version, and supported_versions orderingFAILCheck protocol object and name actual={"hasProtocol":true,"protocolName":"acp"} expected={"hasProtocol":true,"protocolName":"acp"}FAILCheck protocol version history actual={"protocolVersion":"0.1.0","supportedVersionCount":0,"supportedVersionsOrdered":true,"supportedVersionsEndWithCurrent":false} expected="date version with chronological supported_versions ending in current version"FAILprotocol.version must be a YYYY-MM-DD date string.Validate ACP endpoint and transports [fail]! transports does not include rest.INFOValidate ACP endpoint and transports status="fail"INFOValidate ACP API base URL and supported transportsFAILCheck safe HTTPS api_base_url actual=true expected=true apiBaseUrl="https://airbyte.com"FAILCheck REST transport support actual=false expected=true transports=["https"] transportWarnings=["Transport \"https\" is not recognized for this ACP check version."]FAILtransports does not include rest.Validate ACP capabilities [warning]! Service "discovery" is not recognized for this ACP check version.INFOValidate ACP capabilities status="warning"INFOValidate ACP services, extensions, intervention types, currencies, and localesWARNCheck capabilities object actual=true expected=trueWARNCheck stable ACP service declarations actual=["discovery","documentation"] expected="one or more known services such as checkout, orders, or delegate_payment"WARNCheck ACP capability values use stable service, extension, intervention, currency, and locale names actual="2 compatibility warning(s)" expected="no unknown or unstable capability values" warnings=["Service \"discovery\" is not recognized for this ACP check version.","Service \"documentation\" is not recognized for this ACP check version."]WARNService "discovery" is not recognized for this ACP check version.

Sign in to see 41 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.

2 reports
Public score history report links
Scan dateScoreReadinessReport
71/100Level 3, Bot-AwareView report
68/100Level 3, Bot-AwareCurrent report