Alchemy is a blockchain development platform that provides powerful APIs and developer tools for building and scaling Ethereum applications
Alchemy is a blockchain development platform that provides powerful APIs and developer tools for building and scaling Ethereum applications On Nagent, Alchemy is exposed as a fully-configurable developer tools integration that any agent can call — 36 actions, and API key authentication. No code is required to wire Alchemy into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Alchemy to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Alchemy into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Alchemy, with input parameters and output schema. Drop these into any step of an agent built in Helix.
ALCHEMY_COMPUTE_RARITY_V3Tool to compute the rarity of each attribute for a specific NFT based on its collection. Returns prevalence data for each trait, indicating how common or rare each attribute is compared to other NFTs in the same collection. Use when analyzing NFT rarity for trading decisions, collection analysis, or valuation purposes.
Input parameters
The ID of the specific NFT token within the collection. Can be provided in hexadecimal (e.g., '0x2c') or decimal format (e.g., '44').
The Ethereum contract address for the NFT collection. Supports both ERC721 and ERC1155 standards.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_COLLECTION_METADATATool to get metadata for an NFT collection using its marketplace slug (OpenSea, LooksRare, etc). Use when you need collection-level information such as name, description, social links, and floor price. This is useful for discovering collection details without needing the contract address.
Input parameters
OpenSea slug for the NFT collection (e.g., 'boredapeyachtclub', 'cryptopunks')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_COLLECTIONS_FOR_OWNERTool to retrieve all NFT collections held by a specified owner address. Use when you need to get a comprehensive view of what NFT collections a wallet owns, including collection metadata, ownership counts, and spam classification. Only supported on Ethereum. Supports pagination for large collections and filtering options to include or exclude spam/airdrops.
Input parameters
Address for NFT owner (can be in ENS format for Ethereum Mainnet). This is the wallet address whose NFT collections you want to retrieve
Key for pagination. If more results are available, a pageKey will be returned in the response. Pass back the pageKey to fetch the next page of results
Number of NFT collections to be returned per page. Defaults to 100. Max is 100
If set to true, returns NFT metadata. Setting to false reduces payload size and may result in faster API calls. Defaults to true
Array of filters that will be applied to the query. NFTs matching one or more of these filters will be excluded. Options: SPAM (NFTs classified as spam), AIRDROPS (NFTs that were airdropped). May not be used with includeFilters. Note: SPAM filter is available exclusively on paid tiers
Array of filters that will be applied to the query. Only NFTs matching one or more of these filters will be included. Options: SPAM (NFTs classified as spam), AIRDROPS (NFTs that were airdropped). May not be used with excludeFilters. Note: SPAM filter is available exclusively on paid tiers
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_CONTRACT_METADATA_BATCH_V3Tool to retrieve metadata for multiple NFT contracts in a single batch request. Use when you need to fetch contract information for several NFT collections at once to improve efficiency and reduce API calls.
Input parameters
List of contract addresses to batch metadata requests for. Supports both ERC721 and ERC1155 contracts.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_CONTRACT_METADATA_V3Tool to get the metadata for an NFT contract including name, symbol, total supply, and token type (ERC721/ERC1155). Use when you need to retrieve comprehensive contract information such as deployer address, deployment block, OpenSea metadata, and collection details.
Input parameters
Contract address for the NFT contract (ERC721 and ERC1155 supported).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_CONTRACTS_FOR_OWNER_V3Tool to get all NFT contracts owned by an address with contract metadata. Use when you need to retrieve a comprehensive list of NFT collections held by a specific wallet address, including detailed contract information such as token type, total supply, deployer info, spam classification, and OpenSea metadata. Supports pagination for addresses with large NFT holdings.
Input parameters
Address for NFT owner (can be in ENS format for Eth Mainnet)
Ordering scheme for NFTs
Key for pagination. If more results are available, a pageKey will be returned in the response. Pass back the pageKey as a param to fetch the next page of results
Number of NFTs to be returned per page. Defaults to 100. Max is 100
If set to true, returns NFT metadata. Setting this to false will reduce payload size and may result in a faster API call. Defaults to true
Array of filters that will be applied to the query. NFTs that match one or more of these filters will be excluded from the response. May not be used in conjunction with includeFilters. Filter Options: SPAM (NFTs classified as spam), AIRDROPS (NFTs that were airdropped to the user). Note: SPAM filter is available exclusively on paid tiers
Array of filters that will be applied to the query. Only NFTs that match one or more of these filters will be included in the response. May not be used in conjunction with excludeFilters. Filter Options: SPAM (NFTs classified as spam), AIRDROPS (NFTs that were airdropped to the user). Note: SPAM filter is available exclusively on paid tiers
Spam confidence levels
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_FLOOR_PRICE_V3Tool to get the floor price for an NFT collection across multiple marketplaces (OpenSea, LooksRare, etc). Use when you need to check the current floor price of an NFT collection or compare prices across different marketplaces. Returns floor price data including price, currency, collection URL, and timestamp of when the price was retrieved.
Input parameters
OpenSea slug for the NFT collection. Optional parameter to help identify the collection
Contract address for the NFT contract (ERC721 and ERC1155 supported)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_HISTORICAL_PRICESRetrieves historical price data for a token over a specified time range with configurable intervals. Identify the token either by symbol (e.g., ETH, BTC) or by network and contract address. Use this to build price charts, analyze price trends, calculate historical returns, or display historical price information in your application. Important: Provide either symbol OR both network and address (not both methods simultaneously). Time range is specified with start_time and end_time (Unix timestamps or ISO 8601 strings). The interval parameter controls data point granularity (5m, 1h, or 1d).
Input parameters
Token symbol to query (e.g., 'ETH', 'BTC', 'USDC'). Required if network and address are not provided. Cannot be used together with network/address.
Token contract address on the specified network. Required if symbol is not provided. Must be used together with network.
Blockchain network identifier (e.g., 'eth-mainnet', 'polygon-mainnet'). Required if symbol is not provided. Must be used together with address.
End of the time range for historical data. Can be either a Unix timestamp (integer, seconds since epoch) or ISO 8601 formatted string. Example Unix timestamp: 1707782400 for Feb 13, 2024.
Supported interval types for historical price data
Start of the time range for historical data. Can be either a Unix timestamp (integer, seconds since epoch) or ISO 8601 formatted string. Example Unix timestamp: 1707696000 for Feb 12, 2024.
Whether to include market capitalization and total volume data in the response. Defaults to false. Set to true if you need market cap and volume metrics alongside price data.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_NFT_CONTRACTS_BY_ADDRESSTool to retrieve NFT contracts associated with one or more wallet addresses across multiple blockchain networks. Use when you need to discover which NFT collections a wallet owns tokens from, across networks like Ethereum, Base, Polygon, Arbitrum, and Optimism. Returns contract details including metadata, spam classification, and OpenSea data.
Input parameters
Pagination cursor from a previous response. Use this to retrieve the next page of results.
Number of results to return per page. Default is 100 if not specified.
Array of address-network pairs to query. Maximum 2 addresses, each with up to 15 networks.
Include detailed metadata for each contract (OpenSea data, spam info, etc.). Defaults to true.
Filter out specific categories from results (e.g., SPAM, AIRDROPS). Excludes matching contracts.
Include only specific categories in results (e.g., SPAM, AIRDROPS). If set, only matching contracts are returned.
Spam confidence level filter options.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_NFT_METADATATool to retrieve comprehensive metadata for a specific NFT, including contract details, media URLs, attributes, ownership info, and OpenSea data. Use when you need detailed information about a particular NFT token, such as its image, traits, description, or contract metadata.
Input parameters
The ID of the token. Can be in hex or decimal format.
NFT token standard types
If true, will refresh metadata for the given token. If false (default), will check cache first and use it or refresh if cache doesn't exist.
Contract address for the NFT contract (ERC721 and ERC1155 supported). Must be a valid Ethereum address.
Timeout (in milliseconds) for the website hosting the metadata to respond. Set to 0 to only access cache and not live fetch metadata for cache misses.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_NFT_METADATA_BATCHTool to retrieve metadata for multiple NFTs in a single request (up to 100 NFTs), including contract details, media URLs, attributes, and collection data. Use when you need detailed information about multiple NFT tokens efficiently. More efficient than making individual calls for each NFT.
Input parameters
List of token objects to batch request NFT metadata for. Maximum 100 tokens per request.
If true, will refresh metadata for the given tokens. If false (default), will check cache first and use it or refresh if cache doesn't exist.
Timeout (in milliseconds) for the website hosting the metadata to respond. Set to 0 to only access cache and not live fetch metadata for cache misses.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_NFT_SALES_V3Retrieves NFT sales that have occurred through on-chain marketplaces using Alchemy's v3 API. Supports Ethereum (Seaport, Wyvern, X2Y2, Blur, LooksRare, Cryptopunks), Polygon (Seaport), and Optimism (Seaport) mainnets. Use this to track NFT sales activity, analyze market trends, monitor specific collections or tokens, and gather comprehensive sales data including prices, fees, and transaction details. Supports flexible filtering by block range, marketplace, contract, token, buyer, seller, and taker role.
Input parameters
Maximum number of sales to return. Defaults to 100
Sort order for NFT sales results.
Taker role in NFT trade.
Pagination key returned from a previous response. Use to fetch the next page of results
Ending block number to fetch NFT sales to. Accepts decimal integers, hex integers, or 'latest'. Defaults to 'latest'
Filter by specific token ID. Can be in hex or decimal format. Must be used with contract_address
Starting block number to fetch NFT sales from. Accepts decimal integers, hex integers (e.g., '0x0'), or 'latest'. Defaults to '0'
Supported NFT marketplaces.
Filter sales by buyer's Ethereum address. Returns sales involving any buyer if not specified
Filter sales by seller's Ethereum address. Returns sales involving any seller if not specified
Filter by NFT contract address (supports ERC721 and ERC1155). Returns sales for all contracts if not specified
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_NF_TS_FOR_COLLECTION_V3Retrieves all NFTs in a collection using OpenSea collection slug or contract address. Use when you need to fetch NFTs by collection name rather than contract address. Similar to getNFTsForContract but uses collection slug for easier querying. Supports pagination for large collections.
Input parameters
Number of NFTs to return. Defaults to 100
Token ID offset for pagination. Can be hex or decimal. Use nextToken from previous response
If true, returns NFT metadata. Setting to false reduces payload size and may result in faster response. Defaults to true
OpenSea slug for the NFT collection. Required if contract_address is not provided
Contract address for the NFT collection (ERC721 and ERC1155 supported). Required if collection_slug is not provided
Timeout in milliseconds for fetching token metadata. Set to 0 to only use cached data. No timeout by default
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_NF_TS_FOR_CONTRACTRetrieves all NFTs for a given NFT contract address. Supports both ERC721 and ERC1155 token standards. Returns detailed NFT data including token IDs, metadata, images, and attributes. Use this to analyze NFT collections, build marketplace features, track collection holdings, or create analytics dashboards. Supports pagination to handle large collections efficiently (returns up to 100 NFTs per request).
Input parameters
Sets the total number of NFTs returned in the response. Defaults to 100. Maximum is 100
Token ID to start pagination from. Supports both hex (0x...) and decimal format. Use the pageKey from previous response
When true, returns NFT metadata. Set to false to reduce payload size. Defaults to true
The contract address of the NFT collection (supports ERC721 and ERC1155)
Timeout in milliseconds for fetching token metadata. Set to 0 to only use cached data
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_NF_TS_FOR_OWNERTool to get all NFTs currently owned by a given address. Supports ERC721 and ERC1155 tokens on Ethereum and L2s including Polygon, Arbitrum, Optimism, Base. Use when you need to retrieve NFT holdings for an address with optional metadata.
Input parameters
Address for NFT owner (can be in ENS format for Eth Mainnet)
Ordering scheme for NFTs in the response
Key for pagination. If more results are available, a pageKey will be returned in the response. Pass back the pageKey as a param to fetch the next page of results
Number of NFTs to be returned per page. Defaults to 100. Max is 100
If set to true, returns NFT metadata. Setting this to false will reduce payload size and may result in a faster API call. Defaults to true
Array of filters that will be applied to the query. NFTs that match one or more of these filters will be excluded from the response. May not be used in conjunction with includeFilters. Options: SPAM (NFTs classified as spam), AIRDROPS (NFTs that were airdropped to the user)
Array of filters that will be applied to the query. Only NFTs that match one or more of these filters will be included in the response. May not be used in conjunction with excludeFilters. Options: SPAM (NFTs classified as spam), AIRDROPS (NFTs that were airdropped to the user)
Array of contract addresses to filter the responses with. Max limit 45 contracts
Confidence level for spam filtering
Timeout in milliseconds for the website hosting the metadata to respond when metadata is requested. Set to 0 to only access the cache and not live fetch any metadata for cache misses
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_OWNERS_FOR_COLLECTIONTool to retrieve all owner addresses for a given NFT collection contract. Use when you need to analyze NFT ownership distribution, find all holders of a collection, or build ownership analytics for ERC721 and ERC1155 contracts. Optionally returns token balances per owner.
Input parameters
Key for pagination. If more results are available, a pageKey will be returned in the response. Pass back the pageKey as a param to fetch the next page of results
Contract address for the NFT contract (ERC721 and ERC1155 supported)
If set to true, the query will include the token balances per token id for each owner. False by default
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_OWNERS_FOR_CONTRACTTool to get all owners of NFTs in a contract with optional token balances. Use when you need to analyze NFT holder distribution, prepare airdrops, or identify token owners for specific collections.
Input parameters
Key for pagination. Pass back the pageKey from previous response to fetch the next page of results
Contract address for the NFT contract (supports ERC721 and ERC1155)
If true, includes token balances per token ID for each owner. Defaults to false
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_OWNERS_FOR_NFTV3Tool to retrieve all owners for a specific NFT using Alchemy's v3 API. For ERC-721 tokens returns single owner, for ERC-1155 tokens returns all owners with quantities. Use when you need to identify current ownership of an NFT token.
Input parameters
The ID of the token. Can be in hex or decimal format
Contract address for the NFT contract (ERC721 and ERC1155 supported). Must be a valid Ethereum address
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_PORTFOLIO_NF_TS_BY_ADDRESSTool to fetch NFTs owned by multiple wallet addresses across different blockchain networks. Returns comprehensive NFT metadata including contract details, images, attributes, and ownership information. Use when you need to retrieve NFT portfolio data for wallets across multiple chains.
Input parameters
Order by field.
Pagination key from previous response to fetch next page of results
Number of results per page (default 100, max 100)
Array of address and networks pairs (limit 2 pairs, max 15 networks each)
Sort order for results.
Include NFT metadata in response. Default true
Filter out SPAM or AIRDROPS. Default: SPAM
Include SPAM or AIRDROPS in results
Spam confidence levels.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_PRICES_BY_SYMBOLTool to get current token prices by symbol (e.g., ETH, USDC, BTC) using aggregated CEX and DEX data. Use when you need real-time cryptocurrency prices in USD or other currencies. Supports up to 25 symbols per request. Note: Response succeeds even if some tokens are missing - check the error field in each result item.
Input parameters
Array of token symbols to fetch prices for (e.g., \['ETH', 'BTC', 'USDC'\]). Maximum 25 symbols per request. Symbols are case-insensitive.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_TOKEN_BALANCESThis tool retrieves ERC20 token balances for a specified Ethereum address. It can either return balances for all tokens an address has ever interacted with or for a specific set of token contract addresses. It is useful for checking token balances for wallets, monitoring ERC20 token holdings, portfolio tracking, and DeFi applications.
Input parameters
The Ethereum wallet address (40 hex characters with 0x prefix) to get ERC-20 token balances for
Pagination key from a previous response's pageKey field. Use this to retrieve the next page of results when there are more tokens than max_count.
Maximum number of token balances to return per request. Must be between 1 and 1000. Default is 100 if not specified.
Optional list of specific ERC-20 token contract addresses to check balances for. If not provided, returns balances for all tokens the address has interacted with. Each address must be a 40 hex character string with 0x prefix.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_TOKEN_BALANCES_BY_ADDRESSTool to get token balances for wallet addresses across multiple networks using Alchemy's Portfolio API. Use when you need lightweight balance checks for one or more addresses without full token metadata. Supports up to 3 address/network pairs per request with pagination for large result sets.
Input parameters
Cursor for pagination through results. Use the pageKey returned from a previous request to get the next page of results.
Array of address and network pairs to check balances for. Maximum 3 address pairs, with up to 20 networks per address.
Whether to include ERC-20 tokens. Default is true.
Whether to include chain native tokens (e.g., ETH on Ethereum). Default is true.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_TOKEN_METADATARetrieves metadata for an ERC-20 token on Ethereum mainnet, including its name, symbol, decimals, and logo URL. This information is essential for displaying token details in user interfaces, calculating token amounts (using decimals), and showing token branding. Use this when you need to: - Display token information to users (name, symbol, logo) - Convert token amounts between human-readable and contract formats (requires decimals) - Build token listings or portfolio displays - Validate or enrich token data Note: Returns empty/null values for invalid or non-token contract addresses.
Input parameters
The Ethereum contract address of the ERC-20 token (e.g., '0xdAC17F958D2ee523a2206206994597C13D831ec7' for USDT). Must be a valid 20-byte hexadecimal address starting with '0x'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_TOKEN_PRICES_BY_ADDRESSRetrieves current token prices by contract address and network from decentralized exchanges (DEXes). Use when you need real-time token price data for specific contract addresses across multiple networks. Price data is aggregated from DEXes only (not CEXes) and weighted by total volume. Supports up to 25 addresses per request across maximum 3 different networks. Returns price in USD by default with timestamp. Response succeeds even if some prices are unavailable.
Input parameters
Array of token network and address pairs. Maximum 25 addresses per request, maximum 3 different networks. Each entry specifies a network and contract address to fetch price for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_TOKENS_BY_ADDRESSTool to fetch fungible tokens (native, ERC-20, SPL) for multiple wallet addresses across networks. Returns comprehensive token information including balances, metadata (name, symbol, decimals, logo), and current prices. Use when you need complete token portfolio data for wallets across multiple chains (Ethereum, Polygon, Arbitrum, Base, Optimism, Solana, and 30+ EVM chains). Supports up to 2 addresses with 5 networks each per request, with pagination for large result sets.
Input parameters
Cursor for pagination through results. Use the pageKey returned from a previous request to get the next page of results.
Array of address and network pairs to fetch tokens for. Maximum 2 addresses, with up to 5 networks per address.
Whether to include token prices in USD and other currencies. Default is true. Set to false for faster responses with smaller payloads.
Whether to include token metadata (decimals, logo, name, symbol). Default is true. Set to false for faster responses with smaller payloads.
Whether to include ERC-20 tokens. Default is true. Set to false for faster responses with smaller payloads.
Whether to include chain native tokens (e.g., ETH on Ethereum, MATIC on Polygon). Default is true. Native tokens have a null contract address.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_TRANSACTION_COUNTThis tool retrieves the number of transactions sent from a specific address (also known as the nonce). It uses the eth_getTransactionCount endpoint to return the transaction count for an address at a specified block tag (latest, pending, earliest, or a HEX block number), which is essential for determining the nonce for subsequent transactions.
Input parameters
The Ethereum address to get the transaction count for
The block number or tag to get the transaction count from
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_GET_TRANSACTIONS_HISTORY_BY_ADDRESSTool to get transaction history for wallet addresses across multiple networks using Alchemy's Data API. Use when you need to retrieve historical transactions with detailed metadata including logs and internal transactions. Supports pagination for large result sets with a maximum of 50 transactions per request.
Input parameters
Cursor pointing to the end of the current result set for forward pagination.
Number of items to return per page. Maximum 50, defaults to 25 if not specified.
Cursor pointing to the start of the previous result set for backward pagination.
Pagination key for fetching the next page of results. Use the pageKey returned from a previous request.
Array of address and network pairs to query transaction history for. Maximum 1 address pair, with up to 2 networks per address.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_INVALIDATE_CONTRACT_V3Tool to invalidate the cached metadata for an NFT contract. Use when you need to force a refresh of stale or outdated NFT metadata on the next request. This is useful after contract updates or when metadata changes are expected.
Input parameters
The blockchain network to use. Examples: 'eth-mainnet', 'eth-sepolia', 'polygon-mainnet', 'arb-mainnet', 'opt-mainnet', 'base-mainnet'.
Contract address for the NFT contract (ERC721 and ERC1155 supported). Invalidating the cache forces a refresh of metadata on the next request.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_IS_AIRDROPTool to check if a specific NFT token is marked as an airdrop. Use when you need to determine whether an NFT was distributed via airdrop mechanism. Returns true if the token is identified as an airdrop, false otherwise.
Input parameters
The ID of the token. Can be in hex or decimal format.
Contract address for the NFT contract (ERC721 and ERC1155 supported). Must be a valid Ethereum address.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_IS_AIRDROP_NFTTool to determine whether an NFT was airdropped to the owner address. Use when you need to identify if a specific token was received as an airdrop rather than through a purchase or mint.
Input parameters
The ID of the token. Can be in hex or decimal format
Contract address for the NFT contract (ERC721 and ERC1155 supported)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_IS_HOLDER_OF_COLLECTIONTool to check if a wallet address owns any token from a specific NFT collection. Use this when you need to verify collection ownership without retrieving full NFT details, supporting both ERC721 and ERC1155 standards.
Input parameters
Address for NFT owner (can be in ENS format for Eth Mainnet)
Contract address for the NFT contract (ERC721 and ERC1155 supported)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_IS_HOLDER_OF_CONTRACTTool to check if a wallet address holds any NFTs from a specific contract. Use when you need to verify NFT ownership for access control, membership verification, or token-gating features. Supports both ERC721 and ERC1155 contracts.
Input parameters
Wallet address to check for contract ownership
Contract address for the NFT contract (ERC721 and ERC1155 supported)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_IS_SPAM_CONTRACTTool to check if an NFT contract is marked as spam by Alchemy. Use when you need to verify the legitimacy of an NFT contract before interacting with it or displaying its assets. Returns true if the contract is flagged as spam, false if it's valid or hasn't been evaluated yet.
Input parameters
Contract address for the NFT contract (ERC721 and ERC1155 supported). Must be a valid Ethereum address.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_IS_SPAM_CONTRACT_V3Tool to determine if a specific NFT contract is marked as spam by Alchemy. Use when you need to verify the legitimacy of an NFT contract address before interacting with it. Available on paid Alchemy tiers only.
Input parameters
Contract address for the NFT contract (ERC721 and ERC1155 supported). Must be a valid Ethereum address.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_SEARCH_CONTRACT_METADATA_V3Tool to search for keywords across metadata of all ERC-721 and ERC-1155 smart contracts. Use when you need to find NFT collections by name, symbol, or description keywords. Returns contract addresses, names, symbols, token types, deployer info, and OpenSea metadata for matching collections.
Input parameters
The search string to search for in contract metadata. Searches across contract names, symbols, and descriptions
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ALCHEMY_SUMMARIZE_NFT_ATTRIBUTESRetrieves a comprehensive summary of all attributes and traits for NFTs in a collection, including trait counts and distribution statistics. Use this to analyze rarity, understand collection composition, or build trait filters for NFT marketplaces and analytics dashboards.
Input parameters
The contract address of the NFT collection (supports ERC721 and ERC1155)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 47 agents privately built on Nagent that already use Alchemy.
Build on Nagent
Connect Alchemy to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Alchemy, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Alchemy is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Alchemy is connected, you configure its 36 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Alchemy steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Alchemy event fires, the agent kicks off automatically.
Every Alchemy action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Alchemy ships with 36 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Alchemy together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Alchemy-based workflows tailored to your business.