Docsbook agent stop
MCP
docsbook_agent_stopWRITE$0.008 / callStop a Docsbook agent job. Work already committed stays — stopping is not an undo, and what landed is ordinary git history you can revert — and the agent's credential for that job is revoked immediately.
Arguments
The job to stop.
Why, for the record.
Call it#
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "docsbook_agent_stop",
"arguments": {
"task_id": "<task_id>"
}
}
}curl -X POST 'https://docsbook.io/api/mcp/server' \
-H 'Authorization: Bearer dbk_YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"docsbook_agent_stop","arguments":{"task_id":"<task_id>"}}}'Try it over REST#
The same tool is callable as a plain HTTP request, no MCP client required. It runs on the same server, at the same price.
POST
/api/v1/tools/docsbook_agent_stopAuthorization
Your API key, sent as Authorization: Bearer dbk_YOUR_API_KEY.Sent as the Authorization header. Your key is used only by your browser for this request — it is never sent to Docsbook or stored.
Body
The arguments above, as one JSON object.
Request
curl -X POST 'https://docsbook.io/api/v1/tools/docsbook_agent_stop' \
-H 'Authorization: Bearer dbk_YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{"args":{"task_id":"<task_id>"}}'