API reference
Errors & retries
Handle authentication failures, request limits, and temporary outages.
Check the HTTP status and the JSON error body before processing a REST response. Error identifiers describe what happened; the message explains the next step.
| Status | Meaning | Next step |
|---|---|---|
| 400 | Invalid request | Correct the parameters or JSON body before retrying. Use the catalog for valid assets and indicators. |
| 401 | Missing or invalid key | Check Authorization: Bearer ek_... and the key value. Repeating the same request will not fix authentication. |
| 403 | Revoked key | Stop requests with this key and resolve access with the account operator. |
| 404 | Unknown claim token | Check the saved token from checkout. Do not start another paid checkout to recover an already purchased key. |
| 409 | Key already claimed | Check your secure key storage. Stop polling the claim endpoint; it cannot return the same key again. |
| 429 | Request limit reached | Honor Retry-After when present. Key quotas reset at 00:00 UTC; checkout throttling uses a separate limit. |
| 500 / 503 | Temporary server or upstream failure | Retry read requests with bounded exponential backoff and jitter. Stop after a limited number of attempts and surface the error. |
Read the quota headers
When a key quota is available, REST responses and MCP tool responses include X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset. The reset value is an ISO 8601 timestamp. Missing or invalid keys have no quota snapshot; absent headers do not mean zero remaining requests.
For MCP, HTTP 200 alone does not mean the tool succeeded. Inspect result.isError and the error in result.structuredContent. Protocol failures instead use the top-level JSON-RPC error field.
Handle checkout separately
A claim response with status: pending uses HTTP 200. Wait for retry_after_seconds before checking again. A successful claim uses status: active; save its key immediately.
Do not apply automatic read-request retries to purchases. If a checkout or successful claim response is lost, follow the access recovery steps below. API keys are returned once.
Support & access recovery
For a lost key, missing claim response or purchase problem, check your secure key storage first. Repeating a successful claim cannot return the original key. Do not pay for another checkout to recover an existing purchase.
Get help in the Eclipse Discord ↗Ask Eclipse staff how to open a private support conversation. Have your checkout email, receipt reference and approximate purchase time ready for that conversation. Never post API keys, claim tokens or payment details in a public channel.
Recovery requires assistance from Eclipse staff. This link opens Discord; it does not rotate a key or submit a recovery request automatically.