Bolti

Bolti Documentation Audit

One-line summary: A well-organized table of contents wrapped around a hollow core — the central API Reference 404s, entire marketed sections are "coming soon" placeholders, and the pages that do have content contradict each other on built-in tools, default models, and the API path prefix.

1. The API Reference 404s while being linked across the docs (critical)

Location: /api-reference (and cross-links from /intro, /platform-concepts, /getting-started/overview, /conversation-intelligence/webhooks, /calling/making-outbound-calls, /tool-calling/workspace-http-tools, and others)

Problem: docs.bolti.co.in/api-reference returns HTTP 404 (page_not_found), yet "API Reference" is the linked destination for nearly every "exact request/response shapes → see the API Reference" pointer in the docs. The platform-concepts page instead cites a different host, api.bolti.co.in/reference, and that page renders empty except for the title "Bolti API Reference" — a JS-only spec with no server-rendered body and no discoverable OpenAPI file or llms.txt.

Consequence: Bolti markets itself as "Open API + open dashboards — everything you can do in the dashboard, you can do via the REST API," but there is no reachable endpoint reference. Every page that defers schema detail ("→ See API Reference for the exact endpoint and payload shape") dead-ends. A developer — or an AI coding agent trying to scaffold a client — cannot discover endpoints, parameters, or response shapes at all. With no OpenAPI spec and a JS-rendered page, agents get nothing parseable.

The fix: Publish the API Reference at the URL the docs actually link (/api-reference), and ship a static OpenAPI/Swagger spec plus an llms.txt/llms-full.txt so both humans and agents can index endpoints. If the canonical spec lives at api.bolti.co.in/reference, server-render it or provide a downloadable spec, and update the in-docs links to point there.

2. "How do I authenticate an API request?" points to an unreachable page (critical)

Location: /getting-started/workspaces-and-organizations

Problem: The one place that tells a developer how to authenticate says: "The currently active workspace is also baked into every API request you make — see API Reference → Authentication for the header your client should send." That anchor lives under /api-reference, which 404s (see Issue 1). No page in the scraped docs states the auth header name, the credential format, or how to obtain a token for REST calls. (This is downstream of Issue 1 — the same missing reference — but it is called out separately because authentication is the single highest-stakes gap and its fix is distinct: it needs an inline, reachable home regardless of where the rest of the reference lands.)