DevRel Didn't Die, Its Audience Changed

说明与用途

开发者和产品团队在创建面向代理的体验时遇到困难，因为现有文档是为人类而非 AI 代理设计的。

问题

Developers and product teams struggle to create agent‑friendly experiences because existing documentation and onboarding flows are designed for human developers, not AI agents.

结果

Agents can successfully complete product workflows when hidden steps are explicitly exposed, but current documentation and UI flows are insufficient for agent‑first use. The experiments demonstrate that agents can navigate dashboards, perform QA, and even bypass fraud checks when presented with the right information.

工作流

• 1. Identify a product that needs agent support. 2. Build an agent (e.g., Grok Bot) to interact with the product’s UI or API. 3. Observe the agent’s behavior and note missing steps (e.g., guardrails). 4. Expose hidden steps to the agent via API or UI changes. 5. Iterate until the agent completes the full workflow. 6. Document the agent‑friendly workflow for future reference.

证据

AI agents are already using your APIs and skipping everything else. [...] DevRel isn't dead. But the old playbook is.

来源

In 30 days of traffic to the docs Mintlify hosts, AI coding agents made 45.3% of requests, nearly as much as browsers at 45.8%.

来源

The agent didn't even send me through the guardrail section. When I first built it in their builder, rather than with an agent, it showed me that this was the next step I had to take. The agent skipped it.

My agents ran Playwright MCP locally, put it online with ngrok, and connected it to Grok on grok.com. In about 34 seconds it found a bug we’d planted in a tiny shop.