Schedules

Schedules run an agent on a cron expression. See Scheduling & loops for concepts; scheduled runs only fire while the agent’s autonomy is on.

Endpoints

Endpoint	Method	Description
/api/agents/{name}/schedules	GET	List schedules
/api/agents/{name}/schedules	POST	Create a schedule
/api/agents/{name}/schedules/{id}	GET / PUT / DELETE	Read, update, delete
/api/agents/{name}/schedules/{id}/enable	POST	Enable
/api/agents/{name}/schedules/{id}/disable	POST	Disable
/api/agents/{name}/schedules/{id}/trigger	POST	Run now
/api/agents/{name}/schedules/{id}/executions	GET	Run history
/api/agents/{name}/schedules/{id}/webhook	POST / GET / DELETE	Webhook trigger

Create a schedule

curl -X POST https://acme.exohuman.cc/api/agents/research-analyst/schedules \
  -H "Authorization: Bearer $EXOHUMAN_API_KEY" -H 'Content-Type: application/json' \
  -d '{
        "name": "Weekly competitor report",
        "cron_expression": "0 8 * * 1",
        "timezone": "Europe/Madrid",
        "message": "Compile the weekly competitor report and post it to #strategy."
      }'

Field	Default	Description
name	—	Display name (required)
cron_expression	—	Standard 5-field cron (required)
message	—	What the agent should do (required)
timezone	UTC	IANA time zone
enabled	true	Whether it fires
description	—	Notes
model	agent default	Model override
allowed_tools	all	Restrict tools
timeout_seconds	agent timeout	Per-run timeout
max_retries	0	Retries on failure (1–5 to opt in)
retry_delay_seconds	60	Delay between retries (30–600)
validation_enabled	false	Run a post-execution validation pass
validation_prompt	default	Custom auditor instructions

The agent must exist and not be deleted. Creating and changing schedules requires permission to manage the agent’s schedules (the owner or an admin).

Trigger now

curl -X POST https://acme.exohuman.cc/api/agents/research-analyst/schedules/$SCHEDULE_ID/trigger \
  -H "Authorization: Bearer $EXOHUMAN_API_KEY"

The run appears in the schedule’s executions and in the agent’s logs.