GitBook
GitBook is a documentation and knowledge platform, positioned as "the knowledge layer for AI", that connects a company's docs, product and users, answers user questions with AI, and identifies gaps in its knowledge. Teams write and publish product and API documentation with docs-as-code support and AI insights built in.
GitBook publishes 19 APIs on the APIs.io network, including Change Request Content API, Change Request Reviewers API, Change Requests API, and 16 more. Tagged areas include Content, Documentation, Experience, Integration, and Platform.
The GitBook catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 2 Spectral governance rulesets.
GitBook’s developer surface includes authentication, pricing, engineering blog, signup flow, getting-started guide, changelog, API reference, and 11 more developer resources.
Kin Score
What adopting GitBook moves on the Kin Score 7
GitBook is an area vendor: providers adopt it to run part of their developer surface. This is the Kin Score checks its features can move for a provider that adopts it, what each one really earns, and what it earns nothing for.
GitBook earns a provider llms.txt and a docs MCP server without configuration, plus the ordinary documentation, reference, changelog and try-it pointers once the provider declares them. It stops there: GitBook serves no api-catalog, no A2A agent card and no customer-facing Agent Skills (its own SKILL.md teaches agents to edit GitBook, not to use the provider’s API), and the per-site MCP server is one template, graded platform. Contract Quality is untouched because GitBook renders the OpenAPI it is given.
| Check | Earns | Through |
|---|---|---|
| MCP Serverplatform Agent Readiness · customers +4.5 pts vs controlOne GitBook-hosted template on every published site that reads docs and does not call the API; 0.22.0 grades that platform (0.25 of 12). It is also disabled if page actions are off. |
3.0 of 12 | MCP server for published docs |
| Request/Response Examplespartial Agent Readiness · customers -11.6 pts vs controlThe dimension reads examples inside the OpenAPI first; code samples GitBook renders reach only the Examples / Code Samples link fallback. |
1.8 of 7 | Custom code samples |
| Change log Operational Transparency · customers -18.5 pts vs controlUse the updates block on a paid plan, keep posting, and declare the page as a ChangeLog pointer. |
6.0 of 6 | Updates block (changelog) with RSS |
| Publishes llms.txt Discoverability · customers +11.7 pts vs controlGenerated from the provider’s own pages on the provider’s domain, so it reads as the provider’s llms.txt (rule 2’s own-content, own-domain case). |
4.0 of 4 | llms.txt, llms-full.txt and Markdown pages |
| Documentationsaturated Developer Ergonomics · customers +5.1 pts vs control95% of providers with a contract, docs and a reference already earn this; the vendor cannot move it for most of its buyers. |
4.0 of 4 | Published docs site on a custom domain |
| Console or sandbox Developer Ergonomics · customers -1.3 pts vs controlDeclare the reference page as a Console / Playground pointer. |
3.0 of 3 | OpenAPI reference blocks with Test it |
| API referencesaturated Developer Ergonomics · customers +3.8 pts vs control94% of providers with a contract, docs and a reference already earn this; the vendor cannot move it for most of its buyers. |
3.0 of 3 | OpenAPI reference blocks with Test it |
What GitBook ships that earns nothing (3)
- GitBook's own SKILL.md — The skill teaches agents to use GitBook itself; it says nothing about the provider’s API and is not served as the provider’s skill.
- MCP server card — An MCP server card is not one of the four documents the check reads, and GitBook serves no api-catalog.
- OpenAPI reference blocks with Test it — Rendering the spec writes no examples back into it.
A model, not a score. Adopting this vendor changes a provider's Kin Score only when the provider publishes the resulting artifacts on its own surface; nothing here writes a score, and no sponsorship or partnership can. The rating is not for sale → · Full vendor facets artifact
APIs 19
Individual APIs this provider publishes, each with its own machine-readable definition.
GitBook Change Request Content API
Manage content within a change request.
GitBook Change Request Reviewers API
Manage reviewers for change requests.
GitBook Change Requests API
Create, list, review, merge, and update change requests for collaborative editing.
GitBook Collections API
Organize and manage grouped sets of spaces.
GitBook Custom Hostnames API
Configure custom hostnames for docs sites.
GitBook Docs Sites API
Manage published documentation sites.
GitBook Imports API
Import content into spaces.
GitBook Integrations API
Install and manage third-party integrations.
GitBook OpenAPI Specs API
Upload and manage OpenAPI specifications.
GitBook Organization Members API
Manage members and their roles within an organization.
GitBook Organization Teams API
Manage teams within an organization.
GitBook Organizations API
Create and configure organizations to group users, spaces, and collections.
GitBook Search API
Search content across an organization.
GitBook Site Spaces API
Manage spaces within a docs site.
GitBook Space Content API
Manage pages and content within a space.
GitBook Space Users API
Manage user permissions within a space.
GitBook Spaces API
Manage spaces which are containers for documentation or knowledge base content.
GitBook URLs API
Resolve and manage content URLs.
GitBook Users API
Manage user accounts and profiles.
Scroll for all 19
Open Collections 20
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONGitBook Change Request Content API
OPEN COLLECTIONGitBook Change Request Content Change Requests API
OPEN COLLECTIONGitBook Change Request Content Collections API
OPEN COLLECTIONGitBook Change Request Content Custom Hostnames API
OPEN COLLECTIONGitBook Change Request Content Docs Sites API
OPEN COLLECTIONGitBook API
OPEN COLLECTIONGitBook Change Request Content Imports API
OPEN COLLECTIONGitBook Change Request Content Integrations API
OPEN COLLECTIONGitBook Change Request Content OpenAPI Specs API
OPEN COLLECTIONGitBook Change Request Content Organization Members API
OPEN COLLECTIONGitBook Change Request Content Organization Teams API
OPEN COLLECTIONGitBook Change Request Content Organizations API
OPEN COLLECTIONGitBook Change Request Content Search API
OPEN COLLECTIONGitBook Change Request Content Site Spaces API
OPEN COLLECTIONGitBook Change Request Content Space Content API
OPEN COLLECTIONGitBook Change Request Content Space Users API
OPEN COLLECTIONGitBook Change Request Content Spaces API
OPEN COLLECTIONGitBook Change Request Content URLs API
OPEN COLLECTIONGitBook Change Request Content Users API
OPEN COLLECTIONScroll for all 20
Pricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Gitbook Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Gitbook Finops
FINOPSEvent Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
GitBook Webhook Events
AsyncAPI specification for GitBook webhook events. GitBook emits webhook notifications when key events occur within organizations, spaces, pages, change requests, docs sites, co...
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts and semantic vocabularies used across these APIs.
Gitbook Context
JSON-LDSpectral Rules 2
Spectral governance rulesets for linting and validating these APIs.
GitBook API Rules
SPECTRALGitBook API Rules
SPECTRALJSON Schema 7
Standalone JSON Schema definitions for this provider's data models.
GitBook Change Request
JSON SCHEMAGitBook Collection
JSON SCHEMAGitBook Docs Site
JSON SCHEMAGitBook Organization
JSON SCHEMAGitBook Page
JSON SCHEMAGitBook Space
JSON SCHEMAGitBook User
JSON SCHEMAScroll for all 7
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.