Alchemy connector
Back to the connector overview, authentication methods, and actions.
releasePromoted to GA. Version normalized to 1.0.0 in line with the GA versioning policy (GA connectors are versioned 1.0.0 or higher); no functional changes in this version.bug-fix description-fixFixed summarize_nft_attributes — removed the in-flight lowercasing of contractAddress that was regressing every request to 400 ‘contractAddress should be a valid address’, and updated the action, input, and step descriptions to make the EIP-55 checksum requirement explicit so callers pass the correctly-cased address through. Extended get_nft_metadata_batch’s description to mirror get_nft_metadata’s Network-Subdomain scoping caveat — cross-chain contracts (e.g. Base/Polygon tokens surfaced by the multi-chain Portfolio API) return tokenType NOT_A_CONTRACT when batched into the default-network endpoint.Changed · 2 actions updated
Changed · 2 actions updated
alchemy_get_nft_metadata_batch, alchemy_summarize_nft_attributesguide-changes connection-testing description-fix bug-fixRefined the connection guide against the live Alchemy portal — renamed Default Network to Network Subdomain, switched to an Enable-first flow on the Endpoints page, fixed the alch_ API key placeholder, and tightened auth field descriptions. Replaced the Prices test action with a chain-scoped JSON-RPC probe that validates the API Key, the subdomain, and chain enablement — works across every chain type Alchemy hosts (EVM, Solana, Starknet, Sei, Mantle, Sonic, and future additions). Tightened action descriptions from AGI-17581 findings — get_nft_metadata flags Network-Subdomain scoping (cross-chain contracts return NOT_A_CONTRACT); search_contract_metadata now instructs comparing the returned name/symbol against the user’s intent before any downstream use, and refining the query or asking the user on mismatch (beta ranking is not canonical); get_nfts_by_address, get_nft_contracts_by_address, and get_token_balances spell out the hex-only requirement and how to route name-only vs name-plus-hex prompts (prefer hex when both are provided, ask the user or fall back to the single-chain NFT-API sibling when only a name is available). summarize_nft_attributes lowercases contractAddress in-flight so mixed-case inputs that sibling actions accept no longer hit its stricter EIP-55 validation.Changed · 8 actions updated
Changed · 8 actions updated
alchemy_get_contracts_for_owner, alchemy_get_nft_contracts_by_address, alchemy_get_nft_metadata, alchemy_get_nfts_by_address, alchemy_get_nfts_for_owner, alchemy_get_token_balances, alchemy_search_contract_metadata, alchemy_summarize_nft_attributes