Is Your Site Agent-Ready?

Scan your website to see how ready it is for AI agents. We check multiple emerging standards — from robots.txt and Markdown negotiation to MCP, OAuth, Agent Skills and agentic commerce.

Results for https://primus-design.com

DiscoverabilityContentBot Access ControlAPI, Auth, MCP & Skill Discovery

Level 1

Basic Web Presence

Discoverability

3/4

robots.txt

Goal: Publish /robots.txt with clear crawl rules
Result: robots.txt exists with valid format

Resources

robots.txt

GET /robots.txt 200

content-type	text/plain; charset=utf-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f4eaeecdeb7-NRT

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://primus-design.com/sitemap.xml

Received valid robots.txt (200, text/plain; charset=utf-8)

Validate robots.txt structure

Contains valid User-agent directive(s)

Conclusion

robots.txt exists with valid format

Completed in 0ms

Sitemap

Goal: Publish a sitemap and reference it from robots.txt
Result: sitemap.xml exists with valid structure

Resources

Sitemap

Extract Sitemap directives from robots.txt

Found 1 Sitemap directive(s) in robots.txt

GET /sitemap.xml 200

content-type	text/xml; charset=utf-8
cf-ray	a1cb3f503f50deb7-NRT

Found valid xml sitemap at https://primus-design.com/sitemap.xml

Conclusion

sitemap.xml exists with valid structure

Completed in 397ms

Link headers

Goal: Include Link response headers for agent discovery (RFC 8288)
Result: Found agent-useful Link relations: alternate

Resources

RFC 8288 RFC 9727 Skill

Link headers

GET / 200

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/", <https://primus-design.com/wp-json/wp/v2/pages/14>; rel="alternate"; title="JSON"; type="application/json", <https://primus-design.com/>; rel=shortlink
cf-ray	a1cb3f563923deb7-NRT

Homepage returned 200 with Link header

Parse Link header (RFC 8288)

Parsed 3 link(s) from header

Match agent-useful relations

Found agent-useful relations: alternate

Conclusion

Found agent-useful Link relations: alternate

Completed in 1598ms

DNS for AI Discovery (DNS-AID)

Goal: Publish DNS for AI Discovery (DNS-AID) records for DNS-based agent discovery
Issue: DNS for AI Discovery (DNS-AID) well-known entrypoint records not found

How to implement

Publish DNS for AI Discovery (DNS-AID) records under your domain, for example _index._agents.example.com or _a2a._agents.example.com, using ServiceMode SVCB/HTTPS records with alpn and endpoint parameters. Sign the public discovery zone with DNSSEC so validating resolvers return authenticated data.

Resources

IETF Draft RFC 9460 Skill

DNS for AI Discovery (DNS-AID)

DoH SVCB _index._agents.primus-design.com 200

Request

application/dns-json

Response

content-type

application/dns-json

{"Status":3,"TC":false,"RD":true,"RA":true,"AD":false,"CD":false,"Question":[{"name":"_index._agents.primus-design.com","type":64}],"Authority":[{"name":"primus-design.com","type":6,"TTL":600,"data":"ns1.value-domain.com. hostmaster.primus-design.com. 2026062415 3600 900 604800 600"}]}

No SVCB answers (NXDOMAIN)

DoH HTTPS _index._agents.primus-design.com 200

Request

application/dns-json

Response

content-type

application/dns-json

{"Status":3,"TC":false,"RD":true,"RA":true,"AD":false,"CD":false,"Question":[{"name":"_index._agents.primus-design.com","type":65}],"Authority":[{"name":"primus-design.com","type":6,"TTL":600,"data":"ns1.value-domain.com. hostmaster.primus-design.com. 2026062415 3600 900 604800 600"}]}

No HTTPS answers (NXDOMAIN)

DoH SVCB _a2a._agents.primus-design.com 200

Request

application/dns-json

Response

content-type

application/dns-json

{"Status":3,"TC":false,"RD":true,"RA":true,"AD":false,"CD":false,"Question":[{"name":"_a2a._agents.primus-design.com","type":64}],"Authority":[{"name":"primus-design.com","type":6,"TTL":600,"data":"ns1.value-domain.com. hostmaster.primus-design.com. 2026062415 3600 900 604800 600"}]}

No SVCB answers (NXDOMAIN)

DoH HTTPS _a2a._agents.primus-design.com 200

Request

application/dns-json

Response

content-type

application/dns-json

{"Status":3,"TC":false,"RD":true,"RA":true,"AD":false,"CD":false,"Question":[{"name":"_a2a._agents.primus-design.com","type":65}],"Authority":[{"name":"primus-design.com","type":6,"TTL":600,"data":"ns1.value-domain.com. hostmaster.primus-design.com. 2026062415 3600 900 604800 600"}]}

No HTTPS answers (NXDOMAIN)

DoH SVCB _mcp._agents.primus-design.com 200

Request

application/dns-json

Response

content-type

application/dns-json

{"Status":3,"TC":false,"RD":true,"RA":true,"AD":false,"CD":false,"Question":[{"name":"_mcp._agents.primus-design.com","type":64}],"Authority":[{"name":"primus-design.com","type":6,"TTL":600,"data":"ns1.value-domain.com. hostmaster.primus-design.com. 2026062415 3600 900 604800 600"}]}

No SVCB answers (NXDOMAIN)

DoH HTTPS _mcp._agents.primus-design.com 200

Request

application/dns-json

Response

content-type

application/dns-json

{"Status":3,"TC":false,"RD":true,"RA":true,"AD":false,"CD":false,"Question":[{"name":"_mcp._agents.primus-design.com","type":65}],"Authority":[{"name":"primus-design.com","type":6,"TTL":600,"data":"ns1.value-domain.com. hostmaster.primus-design.com. 2026062415 3600 900 604800 600"}]}

No HTTPS answers (NXDOMAIN)

DoH TXT _index._agents.primus-design.com 200

Request

application/dns-json

Response

content-type

application/dns-json

{"Status":3,"TC":false,"RD":true,"RA":true,"AD":false,"CD":false,"Question":[{"name":"_index._agents.primus-design.com","type":16}],"Authority":[{"name":"primus-design.com","type":6,"TTL":600,"data":"ns1.value-domain.com. hostmaster.primus-design.com. 2026062415 3600 900 604800 600"}]}

No TXT answers (NXDOMAIN)

Parse DNS for AI Discovery (DNS-AID) SVCB/HTTPS records

No DNS for AI Discovery (DNS-AID) SVCB or HTTPS records found at well-known entrypoints

Conclusion

DNS for AI Discovery (DNS-AID) well-known entrypoint records not found

Completed in 347ms

Content

0/1

Markdown Negotiation

Goal: Return HTML responses as markdown when agents request it
Issue: Site does not support Markdown for Agents

How to implement

Enable Markdown for Agents so requests with Accept: text/markdown return a markdown version of your HTML response while HTML stays the default for browsers. Confirm the response uses Content-Type: text/markdown (and x-markdown-tokens if available).

Resources

Cloudflare Docs Skill

Markdown Negotiation

GET homepage (Accept: text/markdown) 200

Request

text/markdown

Response

content-type

text/html; charset=UTF-8

Response content-type is text/html; charset=UTF-8, not text/markdown -- site does not support markdown content negotiation

Conclusion

Site does not support Markdown for Agents

Completed in 1319ms

Bot Access Control

1/2

AI bot rules in robots.txt

Goal: Add User-agent rules for AI crawlers like GPTBot, Claude-Web, and others
Result: No AI-specific bot rules; wildcard rules apply to all crawlers including AI bots

Resources

RFC 9309 Cloudflare Docs Skill

AI bot rules in robots.txt

GET /robots.txt 200

content-type	text/plain; charset=utf-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f4eaeecdeb7-NRT

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://primus-design.com/sitemap.xml

Received valid robots.txt (200, text/plain; charset=utf-8)

Scan for AI bot User-agent directives

Checked 15 AI bot user agents -- none found, but wildcard rules apply

Conclusion

No AI-specific bot rules; wildcard rules apply to all crawlers including AI bots

Completed in 0ms

Web Bot Auth request signing

Goal: Let your site identify itself as a bot with Web Bot Auth
Note: Web Bot Auth directory not found (informational only)

How to implement

Publish a JWKS at /.well-known/http-message-signatures-directory so your site can identify itself when it sends bot or agent requests. Receiving sites can use it to verify those signed requests.

Resources

IETF Working Group Cloudflare Docs Skill

Web Bot Auth request signing

GET /.well-known/http-message-signatures-directory 404

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f503f51deb7-NRT

Server returned 404 -- Web Bot Auth directory not found

Conclusion

Web Bot Auth directory not found

Completed in 762ms

Content Signals in robots.txt

Goal: Declare AI content usage preferences with Content Signals in robots.txt
Issue: No Content Signals found in robots.txt

How to implement

Add Content-Signal directives to your robots.txt declaring preferences for ai-train, search, and ai-input. For example: Content-Signal: ai-train=no, search=yes, ai-input=no

Resources

contentsignals.org IETF Draft Skill

Content Signals in robots.txt

GET /robots.txt 200

content-type	text/plain; charset=utf-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f4eaeecdeb7-NRT

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://primus-design.com/sitemap.xml

Received valid robots.txt (200, text/plain; charset=utf-8)

Parse Content-Signal directives

No Content-Signal directives found in robots.txt

Conclusion

No Content Signals found in robots.txt

Completed in 0ms

API, Auth, MCP & Skill Discovery

0/7

API Catalog

Goal: Publish an API catalog for automated API discovery (RFC 9727)
Issue: API Catalog not found

How to implement

Create /.well-known/api-catalog returning application/linkset+json with a "linkset" array. Each entry should include an "anchor" URL for the API and link relations for service-desc (OpenAPI spec), service-doc (documentation), and status (health endpoint). See RFC 9727 Appendix A for examples.

Resources

RFC 9727 RFC 9264 Skill

API Catalog

GET /.well-known/api-catalog 404

Request

application/linkset+json, application/json

Response

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f53984cdeb7-NRT

Server returned 404 -- API Catalog not found

Conclusion

API Catalog not found

Completed in 977ms

OAuth / OIDC discovery

Goal: Publish OAuth/OIDC discovery metadata so agents can authenticate with your APIs
Issue: No OAuth/OIDC discovery metadata found

How to implement

If your site has protected APIs, publish /.well-known/openid-configuration (for OpenID Connect) or /.well-known/oauth-authorization-server (for pure OAuth 2.0) with your issuer, authorization_endpoint, token_endpoint, jwks_uri, and grant_types_supported. This allows AI agents to programmatically discover how to authenticate.

Resources

OpenID Spec RFC 8414 Skill

OAuth / OIDC discovery

GET /.well-known/oauth-authorization-server 404

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f50ff93deb7-NRT

oauth-authorization-server returned 404

GET /.well-known/openid-configuration 404

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f50ef92deb7-NRT

openid-configuration returned 404

Conclusion

No OAuth/OIDC discovery metadata found at either well-known path

Completed in 597ms

OAuth Protected Resource

Goal: Publish OAuth Protected Resource Metadata so agents can discover how to authenticate
Issue: No OAuth Protected Resource Metadata found

How to implement

Publish /.well-known/oauth-protected-resource with your resource identifier, authorization_servers (list of OAuth/OIDC issuer URLs that can issue tokens for this resource), and scopes_supported. This tells agents how to obtain access tokens for your protected APIs.

Resources

RFC 9728 Skill

OAuth Protected Resource

GET /.well-known/oauth-protected-resource 404

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f50ff94deb7-NRT

Returned 404

GET / 200

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/", <https://primus-design.com/wp-json/wp/v2/pages/14>; rel="alternate"; title="JSON"; type="application/json", <https://primus-design.com/>; rel=shortlink
cf-ray	a1cb3f50ff95deb7-NRT

Homepage returned 200 (no WWW-Authenticate header)

Conclusion

No OAuth Protected Resource Metadata found

Completed in 769ms

Auth.md agent registration

Goal: Publish Auth.md metadata for agent registration
Issue: auth.md not found

How to implement

Serve /auth.md at the site root with agent registration instructions, publish /.well-known/oauth-protected-resource, and include an agent_auth block in /.well-known/oauth-authorization-server with register_uri, supported identity types, credential types, and claim/revocation URLs where applicable.

Resources

workos.com workos/auth.md Skill

Auth.md agent registration

GET /auth.md 404

Request

text/markdown, text/plain, */*

Response

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f514fa4deb7-NRT

Server returned 404 - auth.md not found

Conclusion

auth.md not found

Completed in 629ms

MCP Server Card

Goal: Publish an MCP Server Card for agent discovery
Issue: MCP Server Card not found

How to implement

Serve an MCP Server Card (SEP-1649) at /.well-known/mcp/server-card.json with serverInfo (name, version), transport endpoint, and capabilities. The schema is being standardized at https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2127

Resources

SEP-2127 Skill

MCP Server Card

GET /.well-known/mcp/server-card.json 404

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f526ff6deb7-NRT

/.well-known/mcp/server-card.json returned 404

GET /.well-known/mcp.json 404

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f527801deb7-NRT

/.well-known/mcp.json returned 404

GET /.well-known/mcp/server-cards.json 404

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f527fffdeb7-NRT

/.well-known/mcp/server-cards.json returned 404

Conclusion

MCP Server Card not found at any candidate path

Completed in 812ms

Agent Skills index

Goal: Publish an agent skills discovery index
Issue: Agent Skills index not found

How to implement

Publish a skills discovery index at /.well-known/agent-skills/index.json (per the Agent Skills Discovery RFC v0.2.0). Include a $schema field, and a skills array where each entry has name, type, description, url, and a sha256 digest.

Resources

cloudflare/agent-skills-discovery-rfc agentskills.io Skill

Agent Skills index

GET /.well-known/agent-skills/index.json 404

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f538846deb7-NRT

v0.2.0 path returned 404 — trying legacy path

GET /.well-known/skills/index.json 404

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f565937deb7-NRT

Server returned 404 — Agent Skills index not found

Conclusion

Agent Skills index not found

Completed in 1423ms

WebMCP

Goal: Support WebMCP to expose site tools to AI agents via the browser
Issue: No WebMCP tools detected on page load

How to implement

Implement the WebMCP API by calling navigator.modelContext.provideContext() with tool definitions that expose your site's key actions to AI agents. Each tool needs a name, description, inputSchema (JSON Schema), and an execute callback function.

Resources

webmachinelearning.github.io developer.chrome.com Skill

WebMCP

WebMCP detection

Checking page for WebMCP tool registrations

Navigate to https://primus-design.com

Loading page to detect WebMCP tool registrations

Check imperative WebMCP API

No tools registered via navigator.modelContext

Conclusion

No WebMCP tools detected on page load

Completed in 5823ms

Commerce Optional

0/0

No e-commerce signals were detected on this site. These checks are shown for informational purposes and do not affect the score.

x402 Protocol

Goal: Support x402 protocol for agent-native HTTP payments
Note: x402 payment protocol not detected (not a commerce site)

How to implement

Add x402 payment middleware to your API routes to enable AI agents to pay for access via HTTP. Use @x402/express, @x402/hono, or @x402/next middleware with a facilitator URL and wallet address. Protected routes will return HTTP 402 with payment requirements that agents can fulfill automatically.

Resources

x402.org coinbase/x402 docs.x402.org Skill

x402 Protocol

GET /api 404

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f54086fdeb7-NRT

/api returned 404 (not 402)

GET /api/v1 404

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f54d8a9deb7-NRT

/api/v1 returned 404 (not 402)

GET / 200

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/", <https://primus-design.com/wp-json/wp/v2/pages/14>; rel="alternate"; title="JSON"; type="application/json", <https://primus-design.com/>; rel=shortlink
cf-ray	a1cb3f53d85edeb7-NRT

/ returned 200 (not 402)

GET /platform/v2/x402/discovery/resources 200

content-type	application/json
cf-ray	a1cb3f53d85bdeb7-NRT

GET Bazaar discovery API

Network error querying Bazaar API

Conclusion

x402 payment protocol not detected

Completed in 2171ms

MPP (Machine Payment Protocol)

Goal: Support MPP (Machine Payment Protocol) for agent-native HTTP payments
Note: MPP payment discovery not detected (not a commerce site)

How to implement

Publish an OpenAPI document at /openapi.json with x-payment-info extensions on payable operations. Each operation should declare intent (charge or session), method (tempo, stripe, lightning, card), amount, and currency. Use the MPP SDK (mppx for TypeScript, pympp for Python) with framework middleware for Hono, Express, Next.js, or Elysia to add MPP payment handling.

Resources

mpp.dev paymentauth.org Skill

MPP (Machine Payment Protocol)

GET /openapi.json 404

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f5508b2deb7-NRT

/openapi.json returned 404

Conclusion

MPP payment discovery not detected

Completed in 1219ms

Universal Commerce Protocol

Goal: Enable content payments via Universal Commerce Protocol
Note: UCP profile not found (not a commerce site)

How to implement

Serve /.well-known/ucp with protocol version, services, capabilities, and endpoints, and ensure spec URLs and schemas are reachable.

Resources

ucp.dev Skill

Universal Commerce Protocol

GET /.well-known/ucp 404

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f53c852deb7-NRT

Server returned 404 -- UCP profile not found

Conclusion

UCP profile not found

Completed in 1009ms

ACP (Agentic Commerce Protocol)

Goal: Publish ACP discovery metadata so agents can discover your commerce API
Note: ACP discovery document not found (not a commerce site)

How to implement

Serve /.well-known/acp.json at the origin root with protocol.name "acp", protocol.version, api_base_url, supported transports, and capabilities.services so agents can discover your ACP implementation without creating a checkout session first.

Resources

agenticcommerce.dev rfc.discovery Skill

ACP (Agentic Commerce Protocol)

GET /.well-known/acp.json 404

content-type	text/html; charset=UTF-8
link	<https://primus-design.com/wp-json/>; rel="https://api.w.org/"
cf-ray	a1cb3f5518b4deb7-NRT

Server returned 404 -- ACP discovery document not found

Conclusion

ACP discovery document not found

Completed in 1222ms

These are AI-generated recommendations. AI can make mistakes. Please use your professional judgment when implementing these tips, as they are provided "as-is" and Cloudflare assumes no liability for any actions taken or outcomes based on this automated content.