Alchemy MCP integration for AI agents.
Connect AI agents to Alchemy through 5 structured actions, including get asset transfers, get nft metadata, and get nfts for owner. Review authentication, in…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Alchemy integration exposes
The Alchemy Agent App exposes 5 provider-backed actions for developer tools, data, and finance work. Its current contract lets an authorized agent retrieve historical asset transfers for ethereum mainnet addresses through alchemy, retrieve metadata for a specific nft from alchemy ethereum mainnet, and retrieve nfts currently owned by an address from alchemy ethereum mainnet. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Alchemy account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Alchemy capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_asset_transfersREADRetrieve historical asset transfers for Ethereum mainnet addresses through Alchemy.
INPUTS: fromBlock / toBlock / fromAddress / toAddress / excludeZeroValue
get_nft_metadataREADRetrieve metadata for a specific NFT from Alchemy Ethereum mainnet.
INPUTS: contractAddress / tokenId / tokenType / tokenUriTimeoutInMs
get_nfts_for_ownerREADRetrieve NFTs currently owned by an address from Alchemy Ethereum mainnet.
INPUTS: owner / contractAddresses / withMetadata / orderBy / tokenUriTimeoutInMs
get_token_balancesREADRetrieve ERC-20 token balances for a wallet address from Alchemy Ethereum mainnet.
INPUTS: address / tokenSpec / pageKey / maxCount
get_token_metadataREADRetrieve ERC-20 token metadata for one contract from Alchemy Ethereum mainnet.
INPUTS: contractAddress
INPUT CONTRACTS
Know what the action needs before it runs.
get_asset_transfers
fromBlockOPTIONAL- Starting block tag or hex block number.
toBlockOPTIONAL- Ending block tag or hex block number.
fromAddressOPTIONAL- A 0x-prefixed 20-byte hex address.
toAddressOPTIONAL- A 0x-prefixed 20-byte hex address.
excludeZeroValueOPTIONAL- Whether zero-value transfers should be excluded.
get_nft_metadata
contractAddressREQUIRED- A 0x-prefixed 20-byte hex address.
tokenIdREQUIRED- NFT token identifier in decimal or hex form.
tokenTypeOPTIONAL- NFT token type forwarded to Alchemy.
tokenUriTimeoutInMsOPTIONAL- Timeout in milliseconds for live token URI fetches when metadata is requested.
get_nfts_for_owner
ownerREQUIRED- Owner address or ENS name accepted by Alchemy.
contractAddressesOPTIONAL- NFT contract addresses used to filter the response.
withMetadataOPTIONAL- Whether NFT metadata should be returned.
orderByOPTIONAL- NFT ordering mode accepted by Alchemy.
tokenUriTimeoutInMsOPTIONAL- Timeout in milliseconds for live token URI fetches when metadata is requested.
get_token_balances
addressREQUIRED- A 0x-prefixed 20-byte hex address.
tokenSpecOPTIONAL- Token selection forwarded to Alchemy Token API.
pageKeyOPTIONAL- Pagination key returned by a previous Alchemy token-balance call.
maxCountOPTIONAL- Maximum number of balances to request per page.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Asset Transfers
Retrieve historical asset transfers for Ethereum mainnet addresses through Alchemy. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_asset_transfersVerify with Get Nft Metadata
Retrieve metadata for a specific NFT from Alchemy Ethereum mainnet. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_nft_metadataSAFETY BOUNDARY
Operate Alchemy with explicit limits
- Authorize Alchemy with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Alchemy data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Alchemy rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Alchemy task completed successfully.
CONNECTION MODEL
API key
Alchemy API key used with the Authorization: Bearer header. Copy it from your app details page in the Alchemy Dashboard, as shown in the official guide: https://www.alchemy.com/docs/create-an-api-key.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Alchemy.