Troubleshooting

Common errors — 402, 429, chain guards, deposit timing — and exactly how to resolve them.

HTTP 402 Payment Required

Cause: free tier exhausted (500 calls/day per IP) or your key's credit balance is zero.

Fix: the 402 body itself contains the remediation — registration endpoint, deposit calldata, and the current real minimum. Either deposit USDT (Billing) or wait for the UTC-midnight free-tier reset.

HTTP 429 Too Many Requests

Cause: the abuse limiter — very high volume from automated, non-developer traffic that keeps hammering after 402.

Fix: honor the Retry-After header. If you're a legitimate high-volume caller, register a key and deposit credits; paid keys are not subject to the free-tier gate.

My deposit hasn't appeared

  • Deposits credit after ~25 block confirmations (~5 minutes) on Polygon.
  • The deposit history on the console refreshes every 30 seconds.
  • Verify the transaction reached the vault (0x577D3716d6Ad5b676d230f5409deF9838FABaCEF) on Polygonscan.
  • Wrong chain? USDT sent on any network other than Polygon PoS (137) cannot be credited. The console blocks this before it happens; raw transfers from other chains are unrecoverable by us.
  • Wrong wallet? Deposits credit the sending wallet's account. If you deposited from a wallet that isn't bound to your key, the credit went to that wallet's account.

"No usage data yet" on the dashboard

Charts populate after your first metered call with the selected key. The empty state shows an exact curl command that works as-is.

Provider or chain looks down

Check GET /rpc/health — per-provider success rates, latency, and last errors, publicly. The gateway routes around unhealthy providers with circuit breakers; if every provider for a chain is down, calls to that chain fail fast rather than hang.

Still stuck?