Errors - Moontask API

Errors use a consistent JSON shape:

{
  "error": "error_code",
  "message": "Human-readable explanation"
}

Some responses include extra fields (e.g. api_credits_used, api_credits_limit on credit exhaustion).

HTTP status reference

Status	`error` (typical)	Meaning
400	`invalid_wallet`	Invalid Solana address (base58, 32–44 chars)
400	`wallet is required`	Missing wallet in path
401	`unauthorized`	Missing or invalid `X-Api-Key`
403	`subscription_inactive`	No active paid subscription
403	`cors_not_allowed`	Browser / cross-origin request
429	`credits_exhausted`	Monthly API credits used up
429	(rate limit)	Too many requests per minute
500	`internal_server_error`	Unexpected server error
502	`upstream_error`	Scoring backend error
503	`billing_unavailable`	Could not verify usage / credits
503	`server_misconfigured`	Server configuration issue

Do not document 404 as “wallet not registered.” The Partner API does not require prior registration; missing wallets are scored via the upstream engine, not rejected as unregistered.

Wallet validation

Solana addresses must match:

^[1-9A-HJ-NP-Za-km-z]{32,44}$

Invalid addresses return 400 without consuming credits (validation runs before billing).