Coasty has documented how to chain its computer-use agent into longer jobs. In Orchestrating Multi-Step Automations with the Workflow DSL, the company describes a versioned JSON definition submitted to POST /v1/workflows and started with POST /v1/workflows/{id}/runs. Steps can be tasks, assertions, conditions, loops, parallel blocks, retries with backoff and human approvals, and a run moves through queued, running, succeeded, failed, cancelled or timed_out. The hardest number is the price: every task step is billed $0.05.
The claim worth testing is the one about brittleness. Coasty says selector-based automation breaks when a DOM shifts and that its agent “sees the screen and acts like a human,” which is a product claim the post does not support with numbers. Its own example still passes CSS selectors such as input[name=email] into the task params, so the DSL is not selector-free so much as selector-tolerant. The part that survives is the cost model. A per-step price plus the example’s hard limits — budget_cents, max_iterations and deadline_seconds — gives an agent run a ceiling before it starts, which is rarer in this market than it should be.
The catalog confirms the surface. The Coasty Workflows API page carries both paths from the post plus the ones it does not mention: run events, cancel, and resume, which is how a human approval step gets released. Runs started by the DSL also appear under the Coasty Runs API, and recurring and event-driven starts sit in the Coasty Schedules API and Coasty Triggers API. The agentic access profile counts 72 operations, 42 of them acting and 5 human-in-the-loop.
Coasty scores 62.7 on the Kin Score, strong, with access clarity at 84.2 and contract quality at 62.0, and contract governance at 18.2. Agent Readiness is 47.0, agent-native, with idempotency, reversibility, error semantics and pagination lit — the dimensions a five-cent-a-step automation needs if it is going to be retried safely. The unlit one is odd: the MCP server dimension is dark, while the catalog’s own description records a first-party server with 26 tools. A provider whose product is an agent, with an agent-native score, is being read as having no MCP server. That is a gap in what the probe found, not in what Coasty ships, and it is the kind of disagreement the record has to resolve.