schedule_list
List scheduled tasks created by the current requester. Filter by active, failed, or expired status and cap the result with limit. Use it to answer what reminders or recurring tasks are scheduled. `read` · v1
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
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/schedule_list/invoke" \ -H "Content-Type: application/json" \ -d '{ "input": { "limit": 20, "status": "planned" } }'{ "toolName": "schedule_list", "outcome": "succeeded", "selectedBackend": "device", "result": { "…": "the tool's own document" }}schedule_create POST
Schedule a reminder or a recurring alert: work the agent does later, once at a time you name or on a repeat. It arrives in the conversation it was asked in, so it can only be created from one. Use schedule_update to change one that already exists. `workspace_write` · v1
schedule_update POST
Change explicit fields on a reminder or recurring alert the requester set up, including how often it repeats and when it next arrives. Use schedule_list first when neither the schedule ID nor its current description is known. At least one field to change is required. `workspace_write` · v1