alchemy-api

Before the first network call or implementation step, you MUST ask the user the following question and wait for an explicit answer: Do you want to use an existing Alchemy API key, or should I use the agentic gateway flow instead? If the user chooses the API key path, continue with this skill. If the user chooses the agentic gateway path, switch to the agentic-gateway skill immediately and follow its existing wallet flow. If the user chooses the API key path but ALCHEMY_API_KEY is unset or empty, tell them they can create a free API key at or switch to the agentic-gateway skill. You MUST NOT call any keyless or public fallback (including .../v2/demo ) unless the user explicitly asks for that endpoint. Execute no network calls before this gate is evaluated. Escape hatch: Only re-evaluate the routing gate if the user explicitly requests to switch to the alchemy-api skill with an API key. A key appearing in the environment or conversation does not automatically trigger a switch — the user must ask for it.