GitBook Agent Can Now Publish an OpenAPI Spec as a Full API Reference
GitBook's Oct. 15 update lets its Agent, API and MCP server turn an OpenAPI spec into a full API reference, and adds a size count to change requests.

GitBook Agent, the GitBook API and the GitBook MCP server can now publish an OpenAPI spec as a complete API reference instead of a single page, GitBook said in its Oct. 15 changelog.
A spec becomes a reference without the editor
The new publishing path works from three entry points: the Agent, the API and the MCP server. GitBook described the result as a full API reference rather than one page holding the spec.
Change requests now show their size
Change requests carry a Git-style count of additions, modifications and deletions, with a bar showing each share. The overview also lists the merge target and the sites the change will publish to. Attached links appear as chips.
GitBook redesigned the site overview. It adds a Get started section, import options, MCP connection buttons, recent activity and analytics. Empty spaces and pages show the same import and MCP options.
Smaller changes for sign-in, crawls and Markdown
GitBook added a visitor.isAuthenticated condition for adaptive content. It checks whether a visitor is signed in. The older visitor.isSet is deprecated. Reading a page as Markdown through the API with dereferenced=false now keeps reusable content references.
Website connections get more time to crawl large or slow sites, and a crawl that times out now reports a timeout instead of bot protection. GitBook Agent also knows the name and role of the person asking.
Fixes include table duplication when change request conflicts are resolved, editor scroll jumps in Chrome and Edge on Windows, and redirects on the old URLs of deleted sites. Published sites behind Vercel’s firewall now pass its security checkpoint.
Key takeaways
- Agent, API and MCP server can publish an OpenAPI spec as a full API reference.
- Change requests show additions, modifications and deletions at a glance.
visitor.isAuthenticatedreplaces the deprecatedvisitor.isSet.
The take
We think the API reference change matters more than the redesign. Publishing through the API means a release script can update the reference each time a spec changes.
That also moves the risk. A published spec is a public promise about an API. An agent that publishes fast can publish a wrong spec fast. A person should still read the spec diff before it goes live.
We’d try it on one internal API first. Publish its spec through the API and compare the result with the hand-built reference. Check that the change request size count matches what you expect to ship. Move the rest over when the two match.
Switch any pages that use visitor.isSet to visitor.isAuthenticated.


