Skip to main content
The Sharpe API enforces rate limits per API key to keep usage fair and the platform stable. Limits are applied as requests per minute and requests per month, and they come from your plan.

Plans and limits

The API is paid-only: every key belongs to a plan, and there is no free tier. Each account has one API key. REST calls and MCP tool calls use that key and draw on the same monthly quota. Hobbyist is for personal projects and Pro for personal trading and research. Commercial covers use inside your own product; reselling the data is not allowed. A year costs ten months.

Trial

Every account gets one trial before it needs a plan: 7 days and 250 requests, at 10 requests a minute, across REST and MCP. Create a key at /dashboard/api-keys; no payment is asked for. The 7 days start with the key’s first request. A key issued before 2026-11-11 gets the same trial, starting with its first request after that day. When the 7 days are over the key answers 401 expired_api_key, and when the 250 requests are used it answers 429 monthly_quota_exceeded, until the account has a plan. Paying keeps the same key. The monthly quota resets on the 1st of each month (UTC), whatever day your plan started.

Paying and renewing

Plans are paid in USDC, or in any token swapped at checkout, through MoonPay Commerce at /dashboard/billing. There is no card payment and nothing is charged automatically: you get a renewal reminder on each of the 5 days before the paid period ends, and the key keeps working for 3 days after it. Then the key stops and answers 401 expired_api_key until you renew; the same key works again once the plan is active. An upgrade starts a new paid period.
Creating a key needs an active plan or an unused trial: with neither, key creation answers 402. Choose a plan at /pricing.

Rate limit and quota headers

Every authenticated v1 API response includes headers so you can track per-minute rate limits and monthly quota usage in real time:
integer
Maximum requests allowed per minute on your plan.
integer
Requests remaining in the current one-minute window.
integer
Unix timestamp (seconds) when the current window resets.
integer
Monthly request quota of your plan.
integer
Monthly requests remaining in the current billing period.
string
ISO 8601 timestamp when the monthly quota resets. Included when the quota store returns a reset timestamp.
string
Unique identifier for this request. Include when contacting support.
Example response headers

429 Too Many Requests

Both limits return a 429: the per-minute rate limit with type rate_limit_exceeded, and the monthly quota with type monthly_quota_exceeded. Both are temporary and retryable, and both carry a Retry-After header with the seconds until the limit reopens. The response body follows the standard RFC 9457 error format. The type and detail fields tell you whether you hit the per-minute rate limit or the monthly quota.

Response properties

string
rate_limit_exceeded for per-minute limits, monthly_quota_exceeded for monthly caps. Both return status 429.
string
Human-readable explanation of which limit was exceeded.
string
Link to relevant documentation page for the error.
Quota exhaustion used to answer 403, which tells most HTTP clients and agent frameworks never to retry. It is now a 429 so a key that will work again at the next monthly reset is not permanently parked.
429 response body
429 response headers
Monthly quota response body

Best practices

Monitor your usage

Read X-RateLimit-Remaining and X-Quota-Remaining on every authenticated v1 response. When either drops below 10% of its limit, slow down, queue requests, or move heavy jobs to the next reset window.

Implement backoff

When you receive a 429, use the Retry-After header when present, or fall back to X-RateLimit-Reset to calculate how long to wait before retrying. A monthly_quota_exceeded 429 sets Retry-After to the seconds until the quota resets, which can be days: queue the work rather than spinning on retries.
Backoff example

Cache responses

Many Sharpe API endpoints return data that updates on a known schedule (for example, current funding rates refresh every 5 minutes, while heatmap data refreshes every 3 hours). Cache responses locally and respect Cache-Control headers to avoid redundant requests.

Use bulk endpoints

Prefer endpoints that return data for multiple symbols in a single request rather than making one request per symbol. For example, /v1/funding/rates?type=current without a coin parameter returns all rates at once. Learn about authentication