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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Coasty

Coasty keys API

API key management and usage reporting.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 8 operations across 6 paths, and defines 13 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.

8 operations 6 paths 13 schemas 2 DELETE4 GET1 POST1 PUT

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
Contact
Coasty Developer Support
License
MIT
Terms of Service
View terms
Resource Areas
1

Authentication & Security 4

Coasty keys 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 8

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

keys 8

API key management and usage reporting.

GET
/v1/usage
Usage summary for a billing period
getUsage 1 param → 200400401403404409413422
GET
/v1/idempotency/{key}
Fetch a result by Idempotency-Key
getIdempotencyResult 1 param → 200400401403404429500503
POST
/v1/keys
Create an API key
createApiKey body → 200400401403404409413422
GET
/v1/keys
List API keys
listApiKeys → 200400401403404409413422
DELETE
/v1/keys/{key_id}
Revoke an API key
revokeApiKey 1 param → 200400401403404409413422
GET
/v1/llm/keys
List stored BYOK LLM keys
listLlmKeys → 200400401403404409413422
PUT
/v1/llm/keys/{provider}
Store (upsert) your own provider LLM key
storeLlmKey 1 param body → 200400401403404409413422
DELETE
/v1/llm/keys/{provider}
Delete your stored BYOK LLM key
deleteLlmKey 1 param → 200400401403404409413422

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are UsageSummaryResponse (8 properties), APIKeyListItem (7 properties), APIKeyResponse (6 properties), IdempotencyLookupResponse (4 properties). Each schema is shown below with its type and property counts.

ListLlmKeysResponse
object
1 property 1 required
StoreLlmKeyResponse
object
3 properties 3 required
APIKeyListItem
object
7 properties 6 required
IdempotencyLookupResponse
object
Result of GET /v1/idempotency/{key}. 'completed' returns the original response body + originalstatus; 'processing' means the original is still running; an unkn…
4 properties 2 required
EndpointUsage
object
2 properties
ApiError
object
1 property 1 required
UsageSummaryResponse
object
8 properties 1 required
LlmKeyListItem
object
4 properties 2 required
RevokeAPIKeyResponse
object
2 properties 2 required
CreateAPIKeyRequest
object
2 properties 1 required
APIKeyResponse
object
6 properties 6 required
StoreLlmKeyRequest
object
1 property 1 required
DeleteLlmKeyResponse
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

coasty-keys-api-openapi.yml Raw ↑

Other APIs Coasty publishes across the network.

Coasty machines API
AE Profile APIs.io
Coasty predict API
AE Profile APIs.io
Coasty runs API
AE Profile APIs.io
Coasty schedules API
AE Profile APIs.io
Coasty sessions API
AE Profile APIs.io
Coasty triggers API
AE Profile APIs.io
Coasty workflows API
AE Profile APIs.io
#Keys
← Back to C APIs
API Details
ID
coasty:coasty-keys-api
Base URL
https://coasty.ai
Docs
https://coasty.ai/docs
Provider
Coasty
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=coasty-keys-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/coasty-keys-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Coasty keys 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.