Run API
Create goals, launch runs, approve gates and pull artifacts over a clean HTTP API. Everything the dashboard does is an endpoint.
Launch runs from your own code, stream their progress, and react to approvals and recovery — all over a typed, contract-first API.
Create goals, launch runs, approve gates and pull artifacts over a clean HTTP API. Everything the dashboard does is an endpoint.
Subscribe to a run over SSE and receive timeline, status, approval and recovery events the moment they happen.
Get notified when a run needs an approval, finishes, or trips recovery — wire it into Slack, PagerDuty or your own service.
Every payload is described by a versioned JSON Schema contract, so you can generate types and validate both sides of the wire.
Provision credentials a run is allowed to use, scoped per goal. They are injected at execution time and never written to logs.
Run the control plane and execution layer in your own environment when data residency or network isolation matters.
Post a goal and Automata interprets it, drafts a plan with approval gates, and begins executing. Stream the same events the dashboard renders and step in whenever a gate needs you.
curl -X POST https://api.automata.run/api/runs \
-H "Authorization: Bearer $AUTOMATA_KEY" \
-H "Content-Type: application/json" \
-d '{
"goal": "Deploy the landing page to staging",
"approvals": ["deploy"]
}'→ stream eventscurl -N https://api.automata.run/api/runs/$RUN_ID/stream \
-H "Authorization: Bearer $AUTOMATA_KEY"
event: plan 6 steps · 2 approvals
event: act open browser · fill deploy form
event: verify assert 200 · screenshot diff passGenerate a scoped key from the dashboard under Settings → Credentials.
POST a goal to /api/runs and Automata interprets it, plans it and starts executing.
Open the SSE stream to follow timeline and approval events in real time.
Grab a key from the dashboard, post a goal, and watch the run stream back — the whole platform is one API away.