How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Coasty sessions API

Stateful CUA sessions with persistent trajectory.

Coasty sessions API is one of 8 APIs that Coasty publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Sessions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 6 operations across 4 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://coasty.ai, https://coasty.ai.

6 operations 4 paths 10 schemas 1 DELETE2 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://coasty.ai
Authentication
API Key, HTTP Bearer, API Key, API Key
License
MIT
Terms of Service
Resource Areas
1

Authentication & Security 4

Coasty sessions API declares 4 security schemes for authenticating requests. An API key is passed in the header as X-API-Key (apiKey). It accepts HTTP bearer tokens (Coasty API key (sk-coasty-{live,test}-...)) (bearerAuth). An API key is passed in the header as Coasty-Signature (webhookHmac). An API key is passed in the header as X-Coasty-Signature (webhookHmacLegacy). By default, every request must be authenticated.

  • apiKey — Coasty API key. Live: sk-coasty-live-.... Sandbox: sk-coasty-test-....
  • bearerAuth — Equivalent to X-API-Key. Use whichever your client supports.
  • webhookHmac — HMAC-SHA256 credential for external schedule webhooks: t= ,v1= .
  • webhookHmacLegacy — Compatibility alias for the Coasty-Signature HMAC credential.

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

sessions 6

Stateful CUA sessions with persistent trajectory.

POST
/v1/sessions
Create a stateful CUA session
createSession 4 params body → 200400401402403404409413
GET
/v1/sessions
List active sessions
listSessions → 200400401403404409413422
GET
/v1/sessions/{session_id}
Get session info
getSession 1 param → 200400401403404409413422
DELETE
/v1/sessions/{session_id}
Delete a session
deleteSession 1 param → 200400401403404409413422
POST
/v1/sessions/{session_id}/predict
Predict within an existing session
sessionPredict 2 params body → 200400401402403404409413
POST
/v1/sessions/{session_id}/reset
Reset session state
resetSession 1 param → 200400401403404409413422

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are CreateSessionRequest (10 properties), SessionPredictResponse (9 properties), CreateSessionResponse (7 properties), SessionInfoResponse (7 properties). Each schema is shown below with its type and property counts.

SessionMutationResponse
object
2 properties 2 required
SessionPredictRequest
object
4 properties 2 required
ActionResponse
object
4 properties 1 required
LlmConfig
object
Opt-in BYOK model selection. provider 'managed' (or omitting llm) keeps the platform default. There is deliberately no apikey field (422 if attempted): keys ri…
5 properties
ApiError
object
1 property 1 required
CreateSessionRequest
object
10 properties
SessionInfoResponse
object
7 properties 5 required
CreateSessionResponse
object
7 properties 7 required
UsageInfo
object
6 properties
SessionPredictResponse
object
9 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

coasty-sessions-api-openapi.yml Raw ↑

Other APIs Coasty publishes across the network.

Coasty keys API
Coasty machines API
Coasty predict API
Coasty runs API
Coasty schedules API
Coasty triggers API
Coasty workflows API
Where this information came from

This is an independent, third-party profile of Coasty sessions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.