As AI agents become more prevalent, websites and documentation need new optimization strategies. This article explores practical approaches to serving content that works better for both human users and AI agents.
The conversation around AI agents often gets bogged down in hype and misinformation. One persistent myth suggests that optimizing content for AI agents is pointless because 'AIs are as smart as humans and can just use APIs.' This perspective misses a crucial point: while AI agents may be powerful, they have different constraints and behaviors than humans, requiring thoughtful content optimization.
The reality is that frontier models and the agents built on top of them share similar constraints and optimization needs. They process information differently, have context limitations, and benefit from structured content. As these agents become more common, websites that adapt to their needs will have a significant advantage.
Understanding Agent Behavior
AI agents exhibit distinct behaviors that content creators should understand:
Context Management: Agents often avoid reading entire files to prevent context bloat. They might only read the first N lines, bytes, or characters of a document.
Information Discovery: Agents behave differently when explicitly told information exists versus having to discover it independently.
Content Preferences: Agents process markdown more efficiently than HTML, with significant tokenization savings and improved accuracy.
Navigation Patterns: Unlike humans who browse, agents often follow specific pathways through content based on their goals.
Implementing Content Negotiation
The key to optimizing for agents lies in content negotiation—the practice of serving different content based on the requesting client. When a request includes the header Accept: text/markdown, you can confidently assume an agent is making the request.
This approach provides a clean separation between content optimized for humans and content optimized for agents. The implementation is straightforward:
- Detect the
Acceptheader in your server-side logic - Serve appropriately formatted content based on the request type
- Maintain both versions as needed
Practical Optimization Strategies
Documentation Optimization
For technical documentation, several simple optimizations can dramatically improve agent experience:
- Serve true markdown content: This provides massive tokenization savings and improved accuracy
- Remove browser-specific elements: Strip out navigation, JavaScript, and other elements that only make sense in a browser context
- Optimize link hierarchy: Structure content with clear information architecture
- Focus on scannability: Use consistent formatting, clear headings, and logical organization
At Sentry, we've implemented these changes with MDX to allow certain pages to render differently for agents. The result is documentation that's more actionable for both humans and AI.

Comments
Please log in or register to join the discussion