Coasty/

Developer API

Name: Coasty AI Employee
Brand: Coasty
Price: 19 USD
Availability: InStock
Rating: 4.8 (1250 reviews)

OpenAPI llms.txt

Schedules

Fire immediately and inspect durable execution history

Run now & history

Run now & history, at a glance

Fire immediately and inspect durable execution history

POST /v1/schedules/{id}/run

Request map4 boundaries

01
Trigger
run now or due
02
Attempt
unique execution fence
03
Execute
task on machine
04
History
terminal record

Manual, due, webhook, and chained fires all produce attempt-fenced run-history records that expose the exact outcome.

POST /v1/schedules/{id}/run queues one immediate fire. Its optional body is { task_prompt_override?, triggered_context? }; triggered context must be JSON and is capped at 1 MB. Send an Idempotency-Key when a network retry must not enqueue another run. The response is { schedule_id, run_id, status, message, request_id }.

Every execution path, run-now, due cron/run-at, inbound webhook, or schedule chain, uses the schedule's fixed non-secret LLM preference. At each live BYOK fire, Coasty resolves the current encrypted stored provider key. A missing, deleted, or unreadable key fails loudly with no managed fallback. Successful BYOK execution opens no Coasty billing session and records zero Coasty credits; the selected provider can bill its actual tokens.

Endpoint	Scope	Result
`GET /v1/schedules/{id}/runs`	`schedules:read`	Cursor-paginated history; filter by `status` and set `limit` 1-200.
`GET /v1/schedules/{id}/runs/{run_id}`	`schedules:read`	One ownership-scoped history record.

A history record contains id, schedule_id, status, trigger, duration, credits_charged, error, and execution time. It deliberately does not contain llm, provider credentials, screenshots, prompts, or token totals. For managed non-Unlimited schedules, credits_charged is consumer subscription-credit quota, not Developer API wallet cents. It is zero for BYOK, test, Unlimited-bypass, and other non-billable runs, with no fixed USD conversion.