Invoke a tool
`input` follows that tool's own input schema. `toolName`, `actor` and `context` come from the token and the descriptor, so a body that carries them is ignored.
Authorization
memberToken The tools internkim uses inside a company, callable from outside it. A token belongs to a person, and every call runs as that person, so a token can never do more than its owner can.
The first token is made signed in, from the settings screen. After that a token makes its own
successors: POST /token for a new one, DELETE /token for the old one, so a script rotates
without a browser. A token can neither mint a rung above its own nor revoke itself.
Send Authorization: Bearer <token> on every request.
In: header
Path Parameters
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
text/plain
text/plain
text/plain
text/plain
text/plain
text/plain
text/plain
curl -X POST "https://example.com/tools/string/invoke" \ -H "Content-Type: application/json" \ -d '{ "input": {} }'{ "toolName": "string", "outcome": "succeeded", "selectedBackend": "string", "effects": [ { "objectType": "string", "effect": "string", "id": "string" } ], "message": "string", "errorCode": "string", "failureStage": "string", "retryable": true, "result": null}Read the existing work-history view as a company administrator GET
Read host diagnostics through the same execution records, event ledger, model exchanges, turn inputs, connector events, service logs and request metrics as the work-history web page. Only a company administrator may ask. Use recorded IDs for detail views. This reads existing evidence and executes no commands supplied by the caller.
List the tools this token may call GET
Returns only the tools the token's permission reaches. Tools that come and go with circumstance are discovered here.