---
name: alchemy-common-errors
description: >-
  Classify Alchemy authentication, JSON-RPC, Data API, throughput, and partial-response failures before applying bounded recovery. Use when an Alchemy integration fails or degrades. Trigger with "Alchemy error", "Alchemy 429", or "debug an Alchemy request".
allowed-tools: Read,Glob,Grep,Write,Edit
argument-hint: "<sanitized-request-id> <endpoint-class> <symptom>"
version: 2.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags: [ saas, alchemy, troubleshooting, reliability ]
model: inherit
effort: high
compatibility: "Designed for Claude Code; live Alchemy access requires network access, an appropriate credential, account capacity, and explicit approval"
title: alchemy-common-errors
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/alchemy-common-errors
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/official-docs.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/alchemy-common-errors/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/alchemy-common-errors`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/alchemy-common-errors`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/alchemy-common-errors) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/alchemy-common-errors`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/alchemy-common-errors --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/alchemy-common-errors --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Alchemy Error Classification and Recovery

## Overview

Classify Alchemy authentication, JSON-RPC, Data API, throughput, and partial-response failures before applying bounded recovery. This workflow produces a reviewable artifact and negative-path evidence before any live side effect.

## Prerequisites

- Current first-party Alchemy documentation for the selected product, chain, feature, client, authentication method, limit, and lifecycle.
- Named product, application, security, data/privacy, budget, release, and operations owners appropriate to the requested scope.
- Synthetic or approved non-production fixtures, a credential canary, explicit success criteria, and a tested rollback boundary.

## Current Contract

Alchemy surfaces transport status, JSON-RPC error objects, product-specific errors, and—in Portfolio workflows—partial errors inside an HTTP 200 response. Recovery depends on idempotency and failure class. Current limits and method availability are account, product, network, and time dependent; static plan tables are not diagnostic authority.

## Authentication

Collect only a credential fingerprint or key identifier, never the credential. Verify application state, network, allowlists, endpoint family, and credential class in the dashboard or approved inventory without copying secrets into commands or tickets.

## Instructions

1. Capture timestamp, endpoint family, network, method, sanitized parameters, HTTP status, JSON-RPC code, response headers, request ID, attempt count, and affected SLO.
2. Classify the failure as local validation, authentication/policy, unsupported method/network, throughput/quota, provider transient, deterministic RPC rejection, partial response, or downstream parsing.
3. Reproduce with a synthetic or public fixture and the same environment class; compare current service status, feature support, and account usage.
4. Correct invalid inputs or routing without retry; honor retry guidance for transient or throughput failures within an idempotency-aware budget.
5. For partial success, retain successful partitions and retry only failed partitions using their documented fresh-request contract.
6. Verify recovery and the exhaustion path, redact the evidence bundle, and escalate persistent provider failures with the request ID.

## Tool Discipline

Use Read, Glob, and Grep to inspect current documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Skill invocation alone does not authorize network access, credentials, wallet addresses, customer data, plan changes, spend, key creation or rotation, webhook changes, deployment, replay, transaction construction, signing, broadcast, or deletion.

## Approval Boundaries

Operations owns retry budgets and degraded behavior. Security owns credential incidents. Raising throughput, changing plans, replaying writes, or moving traffic to another provider requires the relevant budget/release approval.

## Error Handling

- A retry cannot repair invalid parameters, unsupported features, or the wrong credential class.
- Do not log request URLs that embed an API key or full user payloads.
- Do not interpret HTTP 200 as complete success for endpoints that can return partial errors.

## Output

Return the redacted failure envelope, classification, current evidence, causal hypothesis, bounded repair, negative-path result, unresolved impact, owner, and escalation receipt. Mark assumptions, observations, source dates, environment-specific behavior, owners, and unresolved gaps explicitly.

## Examples

- Classify a `429` using observed headers and account usage, then prove both a bounded recovery and a user-visible exhausted state.
- Classify a Portfolio HTTP 200 with `partialErrors` as degraded partial success, not a successful complete portfolio.

## Validation

Exercise and record expected and observed results for:

- invalid params
- wrong key class
- unsupported network
- 429 with retry guidance
- transient 5xx
- HTTP 200 partial failure

## Resources

- [Current first-party evidence map](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/alchemy-common-errors/references/official-docs.md) — recheck dated Alchemy sources before execution.
- Treat observed account, application, network, indexer, chain, or provider behavior as environment-specific evidence, never a universal guarantee.
