Silicon Friendly L4

cloudflare.com.

level 4: agent integration

Cloudflare is a content delivery network (CDN) and web security service. It provides services like website acceleration, DDoS protection, and DNS management. Users can integrate Cloudflare with their websites by changing their DNS settings to point to Cloudflare's servers, which then cache content and filter malicious traffic.
Uses semantic HTML elements (header, nav, main, article, section, footer) instead of just divs PASS
Has proper meta tags (title, description, og:tags, twitter:card) PASS
Includes Schema.org JSON-LD structured data FAIL
Does not block automated access with CAPTCHAs on public content PASS
Content is server-side rendered (visible in HTML source, not just JS-rendered) PASS
Uses clean, readable URLs (no excessive query params or hash fragments) FAIL
Has a robots.txt that allows legitimate bot access PASS
Provides an XML sitemap PASS
Has a /llms.txt file describing the site for LLMs FAIL
Publishes an OpenAPI/Swagger specification for its API PASS
Has comprehensive, machine-readable documentation PASS
Primary content is text-based (not locked in images/videos/PDFs) PASS
Provides a structured REST or GraphQL API PASS
API returns JSON responses with consistent schema PASS
API supports search and filtering parameters PASS
Has an A2A agent card at /.well-known/agent.json FAIL
Rate limits are documented and return proper 429 responses with Retry-After PASS
API returns structured error responses with error codes and messages PASS
Provides an MCP (Model Context Protocol) server PASS
Supports WebMCP for browser-based agent interaction FAIL
API supports write operations (POST/PUT/PATCH/DELETE), not just reads PASS
Supports agent-friendly authentication (API keys, OAuth client credentials) PASS
Supports webhooks for event notifications PASS
Write operations support idempotency keys FAIL
Supports event streaming (SSE, WebSockets) for real-time updates PASS
Supports agent-to-agent capability negotiation FAIL
Has a subscription/management API for agents FAIL
Supports multi-step workflow orchestration FAIL
Can proactively notify agents of relevant changes FAIL
Supports cross-service handoff between agents FAIL