Prerequisites
- An agent you can run, built in the Agent UI or defined as code under
.dinoai/agents/<name>.yml. - A Bolt schedule you can edit.
- API credentials with DinoAI Agent capabilities set as Bolt schedule environment variables:
PARADIME_API_ENDPOINT,PARADIME_API_SECRET(an account API key,prdm_cmp_...), andPARADIME_WORKSPACE_UID.
Steps
1
Add the Run DinoAI Agent command
In the Bolt schedule editor, select Add command, then Run Paradime DinoAI Agent.
- Agent name: pick the agent (the list comes from
.dinoai/agents/*.ymlon the schedule’s git branch). - Task: describe what you want the agent to do. This becomes the agent’s opening message.
- Select Save command.
2
Set the trigger and deploy
Configure the trigger (cron, on merge, on run completion, or Turbo CI), then deploy the schedule.
The schedule runs and the agent’s messages stream into the Bolt command’s logs. The Bolt run inherits the agent’s outcome: it passes when the agent completes and fails when the agent fails. Each Bolt run starts a fresh agent session, so there’s no continuity between runs.
Define it as code
The UI writes aparadime dinoai command into the schedule. If you manage schedules as code, add it directly:
Trigger from the API (optional)
When you orchestrate the run yourself (Airflow, Lambda, a webhook), trigger the agent through the API withtriggerDinoaiAgentRun instead. Use the API when you need multi-turn continuity, which a Bolt run does not provide.
API and SDK reference
Trigger, poll, and message agents programmatically.
Next steps
Triggering from Bolt reference
Every field of the Run DinoAI Agent command.
Browse templates
Start from a proven agent recipe.