Alchemy Redacted Diagnostic Bundle

Overview

Collect a deterministic, secret-safe Alchemy diagnostic bundle for triage and escalation. 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

A useful diagnostic bundle captures configuration identity, endpoint class, chain, dependency locks, sanitized request and response envelopes, request IDs, timing, retry history, and status observations. It never contains API keys, Admin keys, Notify tokens, signing keys, private keys, raw customer payloads, or credential-bearing URLs.

Authentication

Use a redaction allowlist, not a blacklist. Replace embedded endpoint credentials with a stable one-way fingerprint only when policy permits correlation. Keep the unredacted source in its existing protected system rather than copying it into the bundle.