AI Catalog manifest · GitBook

GitBook

GitBook serves an AI Catalog manifest at /.well-known/ai-catalog.json on gitbook.com, declaring 5 agentic resources that a discovery service can index without asking anyone’s permission.

Open the live manifest → GitBook provider profile

Structural grade · AI Catalog 1.0

Flavored

Fails a hard check in the data model. A catalog in spirit rather than in schema.

ARD conformance-test v0.9.1 (ards-project/ard-spec)

FAIL

Run against this exact body with the project’s own conformance CLI — 3 critical errors.

Discovery path

predecessor

Answered only at /.well-known/ai-catalog.json. ARD v0.91 renamed the path to /.well-known/ard.json and made the old one an optional courtesy, so a consumer implementing only the current spec will not find this manifest.

Declared spec version

0.1

The specVersion in the manifest. 1.0 is current for the AI Catalog data model; anything lower is an earlier draft. ARD reads this field as transport-defined and ignores it.

⚠ Hard checks failed. An ARD client cannot assume this manifest parses to the model the specification defines.

host-no-identifier

Optional affordances missing. None of these break a client, but each one costs the publisher search relevance or verifiability.

content-type-not-ai-catalog-json
cors-not-readable-cross-origin

5 entries

3 media types

13 representative queries

0 trust manifests

Host identifier: none

What this manifest advertises

GitBook MCP server

urn:air:gitbook.com:mcp:gitbook-mcp

Create sites and spaces, open and review change requests, and read or edit GitBook content.

application/json

“Create a new GitBook documentation site”
“Open a change request against our docs”
“Update a page in our GitBook space”

GitBook documentation

urn:air:gitbook.com:docs:gitbook-docs

Product documentation index in LLM-readable form, with a Markdown version of every page.

text/plain artifact →

“How do I set up Git Sync in GitBook?”
“How does adaptive content work?”
“How do I publish a docs site on a custom domain?”

GitBook REST API reference

urn:air:gitbook.com:api:gitbook-api

Reference documentation for the GitBook REST API: organizations, sites, spaces, content, change requests and analytics.

text/markdown artifact →

“List all documentation sites in a GitBook organization”
“Push content to a GitBook space over the API”
“Authenticate against the GitBook API”

GitBook agent skills

urn:air:gitbook.com:skills:gitbook-skills

Skill documents that teach coding agents how to author GitBook content and configure sites.

text/markdown artifact →

“How should an agent write GitBook-flavored Markdown?”
“How do I scaffold a GitBook site from a repo?”

GitBook API catalog

urn:air:gitbook.com:api:gitbook-api-catalog

Machine-readable catalog of GitBook's public APIs, with links to reference documentation and status.

application/json artifact →

“What public APIs does GitBook offer?”
“Where is the GitBook API status page?”

How it is served

The publishing guide asks for three things at the transport layer, because a crawler is the consumer that matters and a crawler is a browser-shaped client.

HTTPS only — yes (HTTP 200)
Content-Type: application/json — yes
Access-Control-Allow-Origin: * — no — header absent

Evidence. Fetched https://gitbook.com/.well-known/ai-catalog.json on 2026-09-13, HTTP 200. The verbatim body is stored alongside its manifest in the GitBook repository as ai-catalog/gitbook-ai-catalog.json. Nothing on this page is derived or generated: an AI Catalog manifest is served from the publisher’s own domain or it does not exist, which makes it — like an A2A Agent Card — one of the few agent artifacts that cannot be produced on a provider’s behalf. Grades are recomputed on every build; the specification is a v0.9 draft and these verdicts will move when it does.

Work with this as data

Every descriptor here is available over the APIs.io API and to AI agents over MCP. Agent Discovery is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for agent discovery

3 MCP tools reach this

apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

Search the catalog

curl "https://apis.io/api/v1/search?q=gitbook&limit=10"

Everything under a tag

curl "https://apis.io/api/v1/tags/gitbook"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.