$ memescore docs errors
Error codes
API docs
API errors are JSON with one human-readable field, error. 429s from plan limits also include plan. Route-level errors (404, 405, 414, 500) are plain text.
{"error": "Missing or invalid API key. Send Authorization: Bearer ak_…"}| Status | Meaning | What to do |
|---|---|---|
200 + error | Token not found: {"mint": …, "error": "We couldn't find this token…"}. Counted. | Check the address. Don't retry. |
400 | Malformed mint, missing parameter, or search query outside 2–40 characters. | Fix the request. |
401 | Missing, malformed, revoked or downgraded API key (or not logged in, for /v1/feed). | Check the header and your plan. |
403 | Valid key, but your plan doesn't include this feature (the feed). | Upgrade, or don't call it. |
404 | Unknown route (plain-text body). | Check the path. There is no /v1/score. |
405 | Method other than GET/HEAD on an API route. | Use GET. |
414 | URL longer than 2,048 characters. | Shorten the request. |
429 | Plan cap, free cap, or an abuse limit. Has Retry-After. | Wait Retry-After seconds. |
500 | Unexpected server error (plain text). | Retry once later; email us if it repeats. |
503 | Busy, daily capacity reached, or an upstream source is down. Usually has Retry-After. | Back off and retry. |
Partial data
If RugCheck, Jupiter or the holder lookup fails during a check, you still get a 200 with whatever was available, and the matching field (rc_error, jup_error, smart_error) says "upstream error". For trading decisions, treat a partial result as incomplete, not as safe.
Each endpoint page lists its exact error messages.