Articles

AI share of voice and prompt monitoring make it possible to observe how API capabilities appear in AI-generated answers. This article looks at how practitioners establish baselines, choose and refine prompts, interpret share of voice and investigate visibility gaps. It also considers what changes when these methods are applied to API products, where the evidence can inform API documentation, competitive positioning and portfolio decisions beyond AI visibility itself.

Different MCP implementation patterns lead to different developer portal information architecture and publishing strategies. Rather than introducing a separate MCP portal, organizations can evolve their developer portal CMS to model new interface types alongside existing APIs, preserving a coherent organizational layer for discovery, governance, documentation, and AI-facing interfaces.

The 2026 Developer Portal Awards are now open for nominations. This year’s programme focuses on four complementary perspectives that reflect the questions we see organisations grappling with today: managing large API portfolios, presenting API products in their business context, documenting API data products, and rethinking onboarding experiences. Rather than prescribing a single model of excellence, the awards recognise observable examples of thoughtful developer portal design across different operating models and organisational contexts.

Organizations usually know what their APIs make possible. They are often much less certain that the outside world understands the same thing. This article follows what happens as technical documentation, developer portals, solution content, and business language gradually drift apart. It considers why that matters for developers, partners, buyers, and AI-assisted discovery, why API teams often notice the problem first, and why making those relationships legible is becoming part of business leadership rather than documentation alone. 

In AI-mediated hybrid workflows, developer portals act simultaneously as product marketplaces and technical workbenches. Cross-dependency is reduced during discovery, but not in organizational commitment. Developer portals evolve to support hybrid human-AI evaluation with accessible, machine-legible, and authoritative documentation for both technical and business stakeholders.

As autonomous agents increasingly interact with technical documentation, traditional HTML can introduce challenges by filling limited context windows with layout elements, navigation, and scripts. This structural cluttering not only drains computing resources but directly causes context pollution and AI hallucinations. Discover how you can reduce this “token tax” and create cleaner, more AI-friendly documentation experiences.