GitBook
GitBook is a platform that allows users to create, publish, and share online books and documentation. It provides a simple and user-friendly interface for writing and organizing content, as well as tools for collaborating with other authors or team members. With GitBook, users can easily create a professional-looking book or documentation site with features such as version control, markdown formatting, and customizable themes.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles GitBook the way a machine reads it — 56 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — GitBook scores 36.9/100 (thin), with a separate agent-readiness read of 23/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from GitBook's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/gitbook/"
title="GitBook on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/gitbook.svg"
alt="GitBook Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/gitbook/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/gitbook/"
title="GitBook on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/gitbook/card.svg"
alt="GitBook Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile GitBook
Each block below is one kind of artifact we hold for GitBook. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 19
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
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 within the panel for all 19 ·
Open Collections 20
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
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 within the panel for all 20 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Gitbook Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Gitbook Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
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 give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Gitbook Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
GitBook API Rules
SPECTRALGitBook API Rules
SPECTRALJSON Schema 7
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
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 within the panel for all 7 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for GitBook — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/gitbook · machine-readable index on apis.io
This is an independent, third-party profile of GitBook, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.