Heykadima

No Markdown content negotiation

Server doesn't return Markdown when requested with Accept: text/markdown. AI agents consume HTML which wastes context and introduces parsing errors. Markdown responses are the emerging standard for agent-optimised content delivery.

Fix: Enable Markdown content negotiation so AI agents can request clean, token-efficient versions of your pages. Quickest path: enable Cloudflare's 'Markdown for Agents' feature (Pro plan+) which auto-converts HTML to Markdown at the CDN edge when an AI agent requests it. No origin changes required. Alternatively, in Next.js you can detect the Accept header and serve .md files: if (req.headers.accept?.includes('text/markdown')) { res.setHeader('Content-Type', 'text/markdown'); } This is one of the highest-leverage changes you can make for AI agent accessibility.

No MCP Server

No MCP Server Card or live endpoint detected. Model Context Protocol (MCP) is the dominant standard for AI agent integrations, adopted by Claude, Cursor, VS Code, GitHub Copilot, Gemini CLI, and 30+ others. Without it, agents can't take actions in your product.

Fix: Publish a machine-readable MCP Server Card at /.well-known/mcp.json: { "mcpVersion": "1.0", "name": "Your Company MCP Server", "description": "What AI agents can do with your product", "endpoint": "https://yourdomain.com/mcp", "capabilities": ["tools", "resources"], "auth": { "type": "bearer" } } If you don't have an MCP server yet, consider building one , it lets AI agents like Claude take actions in your product directly (create accounts, run searches, fetch data). This is the fastest-growing AI integration standard right now.

No Agent Skills file

No Agent Skills file. Agent Skills is an open standard (from Anthropic, now adopted by 30+ agent tools) for packaging specialized knowledge and workflows that AI agents load on demand. Sites that publish skills make it dramatically easier for agents to work with their platform.

Fix: Create a skills folder with a SKILL.md file at /skills/SKILL.md: --- name: your-product-name description: What AI agents can do with your product. Used for skill discovery. --- # [Your Product] Agent Skill ## Overview This skill teaches AI agents how to work with [Your Product]. ## Key workflows 1. How to authenticate 2. How to perform the main action 3. Common troubleshooting For the full spec see agentskills.io

API or developer documentation

No /docs or /api page found. Autonomous purchasing agents need to know how to integrate with you.

Fix: Create a publicly accessible developer documentation page at /docs. At minimum: what your API does, authentication method, key endpoints with examples.

No OAuth discovery

No OAuth discovery endpoint. AI agents that need to act on behalf of users can't automatically discover your auth flow.

Fix: If your product supports OAuth, publish a discovery document at /.well-known/openid-configuration following the OpenID Connect Discovery spec. This enables AI agents to authenticate users automatically without hardcoded auth URLs.