Someone on LinkedIn told me to look at how AssemblyAI approaches their documentation after I shared a link with an API / MCP / Skills documentation prototype I had developed. AssemblyAI is a platform for building Voice AI applications, but it is the button in the top right hand corner of their documentation page that I think reveals a step forward in how we are communicating within our developer portals.
At the top of each page is a “Copy Page” button, but when you look closer it has a drop-down that gives a set of options that reflect the changing landscape in how we engage with our developers. There are seven options available for each page.
- Copy Page — Copy this page as Markdown for LLMs.
- Ask a question — Chat with an AI assistant.
- View as Markdown — View this page as plain text.
- Open in Claude — Ask questions about this page.
- Open in ChatGPT — Ask questions about this page.
- Connect to Cursor — Install MCP server on Cursor.
- Connect to Claude Code — Copy MCP server command for Claude Code.
The copy page, from a context engineering perspective is key. The ability to ask a question via assistant isn’t that novel, but with more context it moves things forward a bit. The view as markdown is showing the entropy occurring across our portal content. Then the open in Claude, Claude Code, ChatGPT, and Cursor provide the next generation client and interface.
I have been exploring what the agentic front door looks like for any domain, pushing forward apis.io when it comes to robots.txt, sitemap.xml, MCP, Agent Skills and more, but this is the human to copilot bridge primarily. I will need to think through more the overlap of protocols here, but how the automated agent and human in the loop, or human led engagement within portals, with our APIs, and how I can best inject Naftiko, API Evangelist, and APIs.io into the stream of consciousness happening here.
