The Knowledge API

The REST routes behind pages, search, Ask and AI Knowledge, and where to find their OpenAPI reference.

Applies To

liveknowledge

The app, the MCP server and the CLI all use the same REST API, so anything they do, your own script can do too. This article is a map of the routes a Knowledgebase adds to the API every liveworkspace app has. For request and response shapes, read the OpenAPI document the product serves, which is always current:

curl https://www.liveknowledge.app/api/openapi.json

How to authenticate, the error shape and the rate limits are the same as every app's: see API Overview, Authentication and Errors and Rate Limits.

The Routes

Every route is under /api/documents/{id}, where {id} is the Knowledgebase's id. In a page route, {tabId} is the page's id, or its title where one page alone has it.

Pages

RouteDoesMCP tool
GET pagesThe page tree, each page with its trustlist_pages
POST pagesA new page from Markdowncreate_page
GET pages/{tabId}One page as Markdown, its trust, backlinks and subpagesread_page
PUT pages/{tabId}Replace a page's writing, or append to itwrite_page
POST pages/{tabId}/moveMove a page and its subpagesmove_page
GET pages/{tabId}/backlinksLinked From

Trust

RouteDoes
POST pages/{tabId}/verifyVerify a page (a signed-in Editor)
GET pages/{tabId}/healthPage Health
PUT pages/{tabId}/knowledgeChange a page's owner or Always in Context
GET, PUT knowledge-settingsThe Review Period

Finding things

RouteDoesMCP tool
GET searchTitles first, then passages, at most 20search_pages
POST askAsk, streamed as server-sent events
GET contextThe Always in Context pages within 8,000 tokensget_context
GET ai, PUT ai/key, PUT ai/model, DELETE ai/keyAI Settings

AI Knowledge

RouteDoesMCP tool
GET knowledgeThe whole AI Knowledge view in one read
POST pages/{tabId}/suggestionsSuggest an editsuggest_edit
GET suggestionsThe suggestions waiting
POST suggestions/{id}/accept, …/dismissAccept or dismiss one
POST questionsReport a question nobody could answerreport_gap
PUT agents/{tokenId}/scopesAllow a connection to write, or stop it (an Editor in person)
Every page and passage answer carries its trust, here as search_pages shows it.

Good to Know

  • Every page and passage answer carries the trust fields described in The liveknowledge MCP Tools.
  • Roles are checked on the server for every route. A token acts with its person's role, narrowed by its scopes: without write it acts as a Participant at most, and a read-only token as a Viewer.
  • Some actions take an Editor in person, never a token: emailing the owners, and allowing a connection to write.
  • Ask, AI Knowledge's model calls and Describe to Set Up run on built-in AI (Cloudflare Workers AI, with daily limits), or on the team's own AI key once one is saved. GET ai answers builtIn: whether this server has built-in AI.

Was this article helpful?

Still need help?

Try Troubleshooting, or tell us what you were trying to do.

Contact us