Optimizing Developer Relations for AI Agents
AI Engineergo watch the original →
the gist
Developer relations must evolve to treat AI agents as primary users, requiring machine-readable documentation, agent-specific benchmarks, and generative engine optimization to ensure tools are recommended during developer workflows.
The Shift to Agent-Centric Advocacy
Developer advocacy is shifting from human-to-human evangelism to a model that includes AI agents as critical users and recommenders. Because agents now influence tool adoption by installing libraries and suggesting solutions during coding sessions, developer relations teams must instrument the agent experience just as they would a human developer's journey. This involves treating the agent as a persona that reads documentation, encounters API errors, and requires specific, machine-readable content to function effectively.
Benchmarking and Generative Engine Optimization
To improve tool discoverability, teams should move beyond traditional SEO and focus on Generative Engine Optimization (GEO). Experiments show that while agents may recommend a tool for general queries, they often fail to suggest it when developers describe specific pain points, such as breaking downstream services due to lack of visibility.
- Build Agent Benchmarks: Develop a suite of lifecycle tasks to test how agents interact with your tool. Use these logs to identify where agents burn turns due to incorrect parameter assumptions or ambiguous tool descriptions.
- Optimize for Pain Points: Map your product's capabilities to specific developer frustrations. If an agent suggests a wiki page instead of your tool, update your documentation to explicitly link your product to that specific problem.
- Combat Stale Content: LLMs often surface outdated product information, which compounds over time. Maintain authoritative, machine-readable sources like
llms.txtfiles to provide a single source of truth. - Reduce Adoption Friction: Ensure your tool is available in MCP (Model Context Protocol) registries. If an agent discovers your tool, the path to implementation must be immediate, avoiding multi-step sales processes that prevent the agent from recommending the tool to the human user.
The Curb Cut Effect
Improving the experience for agents creates a 'curb cut' effect, where optimizations designed for machines simultaneously clear the path for human developers. By providing structured, clear, and up-to-date documentation, teams improve the overall developer experience while ensuring their product remains a top-of-mind recommendation for the agents orchestrating modern software development.