Retire context

GET/api/v1/retire_context

Features

A FILE IN THIS ORGANIZATION'S FOLDER STOPPED BEING TRUE — take it out of every later run's reading. Free. ⚡ Retired, not deleted: a rejected claim is the expensive half of what a customer knows, and deleting it is how the same idea gets proposed again next quarter. It stays findable with include_retired.

Price — $0.00003 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/retire_context.

Input1

Authorizationheaderrequired

Your API key, sent as Authorization: Bearer dbk_YOUR_API_KEY.Sent from your browser straight to the API — never to Docsbook, never stored.

pathstring · queryrequired

Exactly as list_context printed it.

Output3

okboolean

Whether the tool itself succeeded. A tool that ran and refused — an exhausted balance, a plan restriction, a bad argument — answers 200 with ok: false: the call was made and billed, and that refusal is its answer.

resultstring

The tool's own JSON answer, already parsed — not a string to parse a second time.

duration_msinteger

Server-side wall time for the call.

Use cases

Use it when the product changed under a fact, when a question got answered (write the answer into decisions/ first), or when a file turned out to be wrong.

Limitations

Not for a claim you measured — that gets a verdict, which is a finding.

Responses

200The tool ran. Read ok to see whether it succeeded.

401Missing or invalid API key.

Example input

curl 'https://docsbook.io/api/v1/retire_context?path=<path>' \
  -H 'Authorization: Bearer dbk_YOUR_API_KEY'

Example output

{
  "ok": true,
  "result": "<result>",
  "duration_ms": 0
}

更新于 Sep 24, 2026