$ memescore docs limits
Rate limits and quotas by plan
API docs
Limits are per account. The website and every API key on the account share the same counters.
| Plan | Price | Checks | Burst | API keys | /v1/feed | Traders list |
|---|---|---|---|---|---|---|
| Free | $0 | 10/day without an account · 30/day with one | 6/min | — | — | top 5 |
| Trader | $29/mo | 150/day | 15/min | — | — | all |
| API | $199/mo | 2,000/day | 80/min | 5 | yes | all |
| Enterprise | $499/mo | 12,000/day | 200/min | 20 | yes | all |
How the counters work
- Daily: resets at 00:00 UTC.
- Per minute: a rolling 60-second window.
- What counts: each
/v1/checkand/v1/feedcall, and each check on the website. Cached results (X-Cache: HIT) still count. - What doesn't:
/v1/usage,/v1/search,/v1/traders,/v1/ledger,/proof.json,/healthz. Search (about 120/min per IP) and traders (60/min) have their own abuse limits. - No overage billing. When you hit a cap, calls return 429 until the window resets.
Headers on every counted call
HTTP/1.1 200 OK X-RateLimit-Limit: 1500 X-RateLimit-Remaining: 1499 X-RateLimit-Reset: 1795046400 X-RateLimit-Limit-Minute: 60 X-RateLimit-Remaining-Minute: 59 X-Cache: MISS
Handling a 429
Read Retry-After (seconds) and wait. It's 60 when you hit the minute cap and the seconds until midnight UTC when you hit the daily cap. Don't retry in a tight loop. Results are cached for 60 seconds per mint, so polling the same coin faster than that just spends checks.
HTTP/1.1 429 Too Many Requests
Retry-After: 60
X-RateLimit-Remaining-Minute: 0
{"error": "Rate limit reached for your plan.", "plan": "api"}Need more than the biggest plan? Email [email protected].