What the API does and how a turn works
Introduction
Introduction, at a glance
What the API does and how a turn works
task → machine → verified result- 01Describeone observable goal
- 02Attachmanaged or external machine
- 03Runobserve, reason, act
- 04Verifyconfirm terminal state
Start with Submit & forget: give Coasty one observable goal while it provisions the machine, runs the control loop, verifies the outcome, and cleans up. Use workflows when an automation needs many tasks, branches, loops, approvals, or shared outputs. Schedules run a Task later, repeatedly, or from an authenticated webhook. Machines provide the execution target: a managed VM or your enrolled external machine.
The prediction endpoints are lower-level primitives for teams that need to own the control loop themselves. Use sessions for a stateful screenshot loop, predict for a stateless step, grounding for coordinates, and parse for structured actions. Everything is normal HTTPS to https://coasty.ai/v1, so you can choose the highest-level surface that fits the job and drop down only when you need finer control.