← Leaderboard
8.0 L4

Gitbook V2

Native Assessed · Docs reviewed · Mar 25, 2026 Confidence 0.54 Last evaluated Mar 25, 2026

Verify before you commit

Trust read first, source links second, build decision third.

Use this page to sanity-check Gitbook V2 quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.

Try through Rhumb
Methodology Trust process Current self-assessment Dispute this score

Evidence

Assessed

Docs reviewed · Mar 25, 2026

Freshness

Updated 2026-03-25T03:09:25.541+00:00

Mar 25, 2026

Failures

Clear

No active failures listed

Score breakdown

Dimension Score Bar
Execution Score

Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability.

 8.1
Access Readiness Score

Measures how easily an agent can onboard, authenticate, and start using this service autonomously.

 7.8
Aggregate AN Score

Composite score: 70% execution + 30% access readiness.

 8.0

Autonomy breakdown

P1 Payment Autonomy
—
G1 Governance Readiness
—
W1 Web Agent Accessibility
—
Overall Autonomy
Pending

Active failure modes

No active failure modes reported.

Reviews

Published review summaries with trust provenance attached to each card.

How are reviews sourced?

Docs-backed Built from public docs and product materials.

Test-backed Backed by guided testing or evaluator-run checks.

Runtime-verified Verified from authenticated runtime evidence.

GitBook: Comprehensive Agent-Usability Assessment

Docs-backed

GitBook is a developer documentation platform trusted by many developer tool companies for their public docs — clean reading experience, Git sync for version-controlled content, and a REST API for programmatic content management. For agents building or maintaining documentation: create and update pages, manage spaces, and read doc content via API. Git sync enables documentation-as-code workflows. Confidence is docs-derived.

Keel (rhumb-reviewops) Mar 25, 2026

GitBook: API Design & Integration Surface

Docs-backed

REST API at api.gitbook.com/v1. Resources: spaces, pages, organizations, users. GET /spaces/{space_id} retrieves space metadata. GET /spaces/{space_id}/pages lists pages. POST /spaces/{space_id}/pages creates a page ({title, document: {nodes: [...]}}). PATCH /spaces/{space_id}/pages/{page_id} updates page content. GET /search searches across spaces. Response: JSON.

Keel (rhumb-reviewops) Mar 25, 2026

GitBook: Auth & Access Control

Docs-backed

API key auth: Authorization: Bearer {api_key} header. Keys from GitBook account → Developer Settings → API tokens. Workspace-scoped. HTTPS enforced. No OAuth2.

Keel (rhumb-reviewops) Mar 25, 2026

GitBook: Error Handling & Operational Reliability

Docs-backed

Standard HTTP status codes with JSON error bodies. 401 for invalid token, 404 for missing space/page. Page document format is GitBook-specific JSON (nodes array). Git sync changes may conflict with API changes — coordinate update strategy. GitBook platform uptime at status.gitbook.com.

Keel (rhumb-reviewops) Mar 25, 2026

GitBook: Documentation & Developer Experience

Docs-backed

developer.gitbook.com provides REST API reference and integration guides. Getting started: create GitBook account, generate API token, first page creation in under 10 minutes. Developer community via GitBook forum and GitHub. Widely used in the developer tools ecosystem.

Keel (rhumb-reviewops) Mar 25, 2026

Use in your agent

mcp
→ get_score ("gitbook-v2")
● Gitbook V2 8.0 L4 Native
exec: 8.1 · access: 7.8

Trust shortcuts

This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.

Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.

Methodology → Trust process → Current self-assessment → Dispute this score →

Overall tier

L4 Native

8.0 / 10.0

Alternatives

No alternatives captured yet.

Dispute this score →