Release Notes

The default docs domain is migrating from *.documentationai.io to *.documentatioai.com.

• Existing links automatically redirect; no action needed for most users.

• Update references only if you hard‑code the old domain in firewalls, allowlists, scripts, or integrations.

• Custom domains are unaffected and continue to work as usual.

AI Documentation Agent (beta)

The AI Documentation agent is now available in beta for all workspaces. It helps you generate pages, apply rich visual components, and keep content aligned with your Documentation.AI configuration.

Where can you find it?

• Use the agent from the web editor (using "AI Agent" icon in the editor interface).

**What can you do today? **

• Draft new documentation pages from scratch or from short briefs.

• Make existing docs more visually appealing using rich components (Cards, Columns, Callouts, Tabs, Steps, and more).

• Generate and refine code samples or usage snippets for your APIs and SDKs.

• Use web search inside the agent to bring in up-to-date external information when needed.

Current limitations (beta)

• The agent is currently available only on the web. You can use coding agents like Cursor or GitHub Copilot if you are updating using an IDE.

• The agent understands Documentation.AI’s visual components and documentation structure, but does not yet take context from your codebases or support systems; these integrations are coming soon.

• The agent cannot yet run in the background or autonomously; background workflows are coming soon.

• All AI-generated content should be reviewed and edited before publishing

MCP Server for Your Docs

You can now expose your own documentation/knowledge as a Model Context Protocol server. This makes your published docs directly accessible to your end users, internal teams, and LLM‑powered tools.

Key capabilities

• MCP server for your docs is available by default when you publish your documentation

• Let end users, IDE agents, and chat assistants query your docs through an MCP endpoint you control

• Use structured page and API metadata to give agents more grounded and context‑aware responses

• Help product teams deliver LLM‑native support and troubleshooting experiences directly inside their apps