Imported from jeremylongshore/tons-of-skills-marketplace (plugins/saas-packs/alchemy-pack/skills/alchemy-common-errors/SKILL.md). Install upstream with npx skills add jeremylongshore/tons-of-skills-marketplace --skill alchemy-common-errors. Copyright stays with the author (MIT).

Alchemy Common Errors

Overview

Troubleshooting guide for Alchemy SDK errors covering rate limits, RPC failures, invalid parameters, and network-specific issues.

Prerequisites

• A reproducible failing request that records its network, method, sanitized parameters, timestamp, response code, and request/correlation ID where available—never the API key or private key.
• Access to the appropriate Alchemy dashboard and a non-production key when testing a fix.
• A defined retry budget and an application fallback for requests that cannot safely be retried.

Instructions

1. Classify the failure with the error reference and confirm the intended network, RPC method, and parameter shape.
2. Reproduce it with a scoped development key or a public test fixture, then inspect account limits and service status without exposing credentials.
3. Apply the smallest appropriate repair: correct parameters, back off for 429, paginate a large query, or switch to the documented supported API.
4. Verify the corrected request and record the sanitized outcome; escalate persistent provider failures with the correlation or request ID.

Error Reference

Authentication & Rate Limits

Alchemy Rate Limits by Plan

RPC & Query Errors

// Common RPC error handler
import { Alchemy, Network } from 'alchemy-sdk';

async function safeAlchemyCall<T>(
  operation: () => Promise<T>,
  context: string
): Promise<T | null> {
  try {
    return await operation();
  } catch (error: any) {
    const code = error.code || error.response?.status;

    switch (code) {
      case -32602: // Invalid params
        console.error(`[${context}] Invalid parameters: ${error.message}`);
        console.error('Common causes: wrong address format, invalid block number, missing 0x prefix');
        break;

      case -32600: // Invalid request
        console.error(`[${context}] Malformed JSON-RPC request`);
        break;

      case -32601: // Method not found
        console.error(`[${context}] RPC method not available on this network`);
        console.error('Some Enhanced APIs are Ethereum-only');
        break;

      case -32000: // Server error
        console.error(`[${context}] Node server error — usually transient, retry`);
        break;

      case 429:
        const retryAfter = error.response?.headers?.['retry-after'] || 1;
        console.error(`[${context}] Rate limited — retry after ${retryAfter}s`);
        break;

      default:
        console.error(`[${context}] Unknown error: ${code} — ${error.message}`);
    }
    return null;
  }
}

NFT API Errors

Enhanced API Errors

Network-Specific Issues

// Diagnostic function
async function diagnoseAlchemyIssue(alchemy: Alchemy): Promise<string[]> {
  const issues: string[] = [];

  try {
    const blockNumber = await alchemy.core.getBlockNumber();
    console.log(`Connected: block #${blockNumber}`);
  } catch (err: any) {
    if (err.message?.includes('apiKey')) issues.push('API key invalid or missing');
    else if (err.code === 'ECONNREFUSED') issues.push('Cannot reach Alchemy servers — check network');
    else issues.push(`Connection error: ${err.message}`);
  }

  return issues;
}

Quick Diagnostic

# Test Alchemy API directly
curl -s "https://eth-mainnet.g.alchemy.com/v2/${ALCHEMY_API_KEY}" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":0}' | jq .

# Check CU usage (requires auth token)
curl -s "https://dashboard.alchemy.com/api/stats" \
  -H "Authorization: Bearer ${ALCHEMY_AUTH_TOKEN}" | jq .

Output

• Error classified by type (auth, rate limit, RPC, network)
• Root cause identified with specific fix
• Diagnostic function for automated troubleshooting

Examples

When a testnet getAssetTransfers call returns 429, retain the sanitized method, network, response headers, and request ID, then make the retry helper honor Retry-After within the configured budget. Confirm the retry succeeds against the expected testnet or produces a controlled unavailable result when the budget is exhausted. If the dashboard shows a disabled key or depleted quota, stop retries and correct the account configuration; do not substitute a production credential or place it in a curl command committed to the project.

Error Handling

Resources

• Alchemy Error Codes
• Alchemy Rate Limits
• JSON-RPC Error Codes

Next Steps

For collecting debug bundles, see alchemy-debug-bundle.