Alchemy API

Name: Alchemy API
Brand: Alchemy API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey8 EndpointsREST

For Agents

Look up NFTs, ERC-20 token balances, and historical asset transfers for any Ethereum address through Alchemy's enhanced blockchain APIs.

Install Jentic One Beta

Connect the Alchemy API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Alchemy API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Alchemy API.

Fetch every NFT held by a wallet address with /getNFTsForOwner

Retrieve metadata for a specific NFT contract and token id

List all NFTs minted by a given NFT contract on Ethereum

Look up the current owners of a specific NFT

GET STARTED

Start building with Alchemy API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Alchemy API, keeping it validated and agent-ready. Alchemy is a blockchain infrastructure provider whose REST endpoints expose enhanced data on top of Ethereum and other EVM chains. This spec covers the NFT API, Token API, and Transfers API — letting agents look up NFTs and metadata for an owner or contract, fetch ERC-20 token balances and metadata for an address, and pull historical asset transfers. Authentication uses the API key embedded as a path parameter in the base URL.

Use Cases

Patterns agents use Alchemy API for, with concrete tasks.

★ NFT portfolio dashboard for a wallet

A wallet UX team builds a portfolio view that shows every NFT a user owns, with images and collection metadata. The integration calls /getNFTsForOwner with the user's address, then enriches each item with /getNFTMetadata for missing media. Alchemy returns a normalised payload across collections, so the team avoids parsing on-chain calldata.

GET /getNFTsForOwner with the wallet address, then for each NFT GET /getNFTMetadata when media or attributes are missing

Treasury token balance reporting

A DAO operations agent reports daily on a treasury multisig by calling /getTokenBalances with the multisig address, then expanding each result with /getTokenMetadata to attach symbols and decimals. The agent posts the formatted balance sheet to a Slack channel, removing the need to query nodes directly.

GET /getTokenBalances for the treasury address, then GET /getTokenMetadata for every contract in the response and assemble the report

Historical transfer audit for compliance

A compliance team audits inflows and outflows of a wallet by calling /getAssetTransfers with from/to filters, category filters such as external and erc20, and a block range. The single endpoint replaces multiple ad-hoc node queries and returns paginated transfer events in chronological order.

POST /getAssetTransfers with the wallet address, category filters, and a fromBlock/toBlock range, then page through the result set

Agent-led NFT ownership verification

A Jentic agent checks whether a user qualifies for a token-gated experience by looking up NFTs for the user's address and verifying that the contract address matches the gating collection. The agent only needs the wallet address and the gating contract — Jentic handles the Alchemy request and returns a yes/no result.

Search Jentic for 'check NFTs owned by an Ethereum address', execute /getNFTsForOwner, and filter the response for the gating contract address

Key Endpoints

8 endpoints — jentic publishes the only available openapi specification for alchemy api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/getNFTsForOwner

List NFTs held by a wallet address

GET

/getNFTMetadata

Retrieve metadata for a specific NFT

GET

/getNFTsForContract

List NFTs minted by a contract

GET

/getOwnersForNFT

Get current owners of a specific NFT

GET

/getTokenBalances

Get ERC-20 token balances for an address

GET

/getTokenMetadata

Get metadata for a token contract

POST

/getAssetTransfers

Query historical asset transfers

GET

/getNFTsForOwner

List NFTs held by a wallet address

GET

/getNFTMetadata

Retrieve metadata for a specific NFT

GET

/getNFTsForContract

List NFTs minted by a contract

GET

/getOwnersForNFT

Get current owners of a specific NFT

GET

/getTokenBalances

Get ERC-20 token balances for an address

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Alchemy API key sits in the URL path. Jentic keeps the key encrypted in its vault and substitutes it into the path at execution time so it never enters agent context or logs.

Intent-based discovery

Agents search Jentic by intent (e.g. 'list NFTs for a wallet', 'get ERC-20 balances'), and Jentic returns the matching Alchemy enhanced API operation with its input schema so the agent can call it without reading the docs.

Time to first call

Direct Alchemy integration: half a day to a day for auth wiring, response normalisation, and pagination. Through Jentic: under 30 minutes with search, load, and execute.

FAQs

Specific to using Alchemy API through Jentic.

Why is there no official OpenAPI spec for Alchemy API?

Alchemy does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Alchemy API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Alchemy API use?

The Alchemy API key is embedded directly in the URL path (https://eth-mainnet.g.alchemy.com/v2/{apiKey}). Jentic stores the key encrypted in its credential vault and substitutes it into the path at execution time, so the raw key never appears in the agent's prompt or response.

Can I list every NFT held by a wallet address with the Alchemy API?

Yes. Call GET /getNFTsForOwner with the wallet address as a query parameter. The endpoint returns NFTs across collections, with metadata, media URLs, and pagination tokens for large wallets.

What are the rate limits for the Alchemy API?

The OpenAPI spec does not declare per-endpoint rate limits. Alchemy enforces compute-unit-based limits per plan (free, growth, scale), so monitor compute units in the Alchemy dashboard for high-volume NFT or transfer queries.

How do I get ERC-20 token balances for an address through Jentic?

Search Jentic for 'get token balances for an Ethereum address', load the schema for GET /getTokenBalances, and execute it with the wallet address. Chain GET /getTokenMetadata for any contract addresses you need to display with symbols and decimals.

Does the Alchemy API cover non-Ethereum chains?

The base URL in this spec points at Ethereum mainnet (eth-mainnet.g.alchemy.com). Alchemy supports other EVM networks (Polygon, Arbitrum, Optimism, Base) via different base URLs that follow the same path structure documented here.