Search docs
/api/v1/search_docsLITERAL-string search over the workspace's documentation files — for an exact token you already know: an error message, a CLI flag, a config key, a regex, a file path. In 'text' mode on a project with a semantic index the literal matches are fused with the index's meaning matches (engine: "hybrid"), so a section worded differently still surfaces; without an index it matches words only (engine: "literal"). Still NOT for a question or a topic ('where do we describe…', 'find the page about…', «где у нас описано», «найди в документации») — that is search_project_docs, which takes the whole question, splits it into its parts and ranks pages by MEANING; do not hunt for an answer here mode by mode. Modes: 'text' (default — full-text with snippets, hybrid when indexed), 'grep' (regex), 'symbol' (fuzzy heading match), 'paths' (glob over file paths). Returns numbered hits {n, title, headingPath, snippet, url}: 280-character snippets, not pages — call read_project_doc for the whole page before editing it. Available to any token regardless of read/write scope.
Price — $0.00009 per call (twice what serving it costs us), charged to the workspace balance, the same as over MCP.
Also reachable by name at POST /api/v1/tools/search_docs.
Authorization: Bearer dbk_YOUR_API_KEY.Sent from your browser straight to the API — never to Docsbook, never stored.200 with ok: false: the call was made and billed, and that refusal is its answer.Show child attributes5
ok to see whether it succeeded.curl 'https://docsbook.io/api/v1/search_docs?query=<query>' \
-H 'Authorization: Bearer dbk_YOUR_API_KEY'{
"ok": true,
"result": {
"mode": "<mode>",
"docs_language": "<docs_language>",
"count": 0,
"results": [],
"note": "<note>"
},
"duration_ms": 0
}