List schedules
List the scheduled eval runs (cron jobs) for the agent you're editing, each with its name, cron expression, a human-readable schedule, timezone, whether it's enabled, and its last-run status. A cron job runs this agent's eval suite automatically on a recurring schedule. Call this FIRST to see what's already scheduled before create_cron_job so you don't duplicate a schedule.
Authorization
bearerAuth A personal access token from Settings > API tokens.
In: header
Header Parameters
A key you choose, such as a UUID, that makes this POST safe to retry. Within 24 hours the same key and request answers with the first successful answer and runs nothing, the same key with a different request answers 422 idempotency_key_reused, and a key whose request is still running answers 409 idempotency_key_in_use. A failed request keeps nothing, so the same key runs it again.
1 <= length <= 255Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Target agent as 'workspace-slug/agent-slug' (e.g. 'luke/support-bot').
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X POST "https://example.com/operations/list_cron_jobs" \ -H "Content-Type: application/json" \ -d '{ "agent": "string" }'{}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}Schedule run history POST
List a schedule's past batch runs (its run history), every batch that cron job fired, newest first, each with its status (running / complete / error), progress (completed/total), failed and errored counts, and start/finish times. Pass the cron job id from list_cron_jobs. Use this to answer "how has this schedule been doing?" or to find a batch to re-score. A pure read, it does not fire the schedule.
List dashboards POST
List the saved Overview dashboards in this workspace, workspace-wide and per agent, with their name, scope, saved time range and widgets (each widget's id, title, data field, chart type, grouping and filters). Call this FIRST before create_dashboard so you don't duplicate one that already exists, to answer 'what dashboards are set up?', and to get the widget id that drill_chart_calls and delete_dashboard_widget take. Overview dashboards are saved views over our own calls; listing them runs no chart queries and spends no credits.