Developers/Skylit API (Beta)

Authentication

Authenticate with a Skylit API key, and how credits and rate limits work.

Beta. The Skylit API and MCP server are in Beta with limited access. Request access and we'll let you know when yours opens.

The Skylit Public API uses bearer authentication. Send your API key in the Authorization header on every request:

Terminal
Authorization: Bearer <your-api-key>

Getting a key

Generate and manage keys on the Developer page (API keys tab). New accounts are seeded with 5,000 credits.

curl "https://api.skylit.ai/v1/heatmap?symbols=SPY" \
  -H "Authorization: Bearer $SKYLIT_API_KEY"

Credits

Every chargeable request debits a fixed cost from your credit balance.

EndpointCost
/v1/heatmap1
/v1/gex/levels1
/v1/historical5
/v1/stream1 to open + 1 per minute open
/v1/account, /v1/openapi.json0

Every chargeable response carries X-Credits-Remaining: <balance>. Failed calls are free: a request answered with any 4xx or 5xx is refunded, and its X-Credits-Remaining already reflects the refund.

402 insufficient_credits

You're out of credits. Top up in the account console.

403 account_suspended

The account has been administratively suspended.

Rate limits

A safety ceiling of 600 requests / minute per key is enforced by the Skylit gateway. This is runaway protection, not your quota — credit metering does the per-customer accounting. The X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers describe the key's quota, which is unlimited (-1, 0, 0). They don't count toward the per-minute ceiling, so don't throttle on them.

StatusMeaning
401 UnauthorizedMissing or invalid API key.
403 ForbiddenKey revoked/expired, or account suspended.
429 Too Many RequestsRate ceiling hit. The gateway's 429 has no Retry-After: back off and retry after the current minute. 429s from the API itself (concurrency or stream limits) carry Retry-After.
Make your first call

Jump to GET /v1/heatmap and try it live in the playground.

Last updated

Was this page helpful?