Ankr Advanced API

Name: Ankr Advanced API API
Brand: Ankr Advanced API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey18 EndpointsREST

For Agents

Query account balances, NFT holdings, transactions, and on-chain logs across 30+ blockchains through Ankr's multichain JSON-RPC. Returns normalised data so agents can answer wallet questions without per-chain RPC code.

Quickstart

Get started with Ankr Advanced API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get NFTs owned by a wallet"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Ankr Advanced API API.

Look up an account's token and native-coin balances across multiple blockchains in a single call

List all NFTs owned by a wallet with metadata and collection info

Retrieve NFT transfer history and current holders for a given collection

Fetch token holder distributions and supply metrics for ERC-20 contracts

GET STARTED

Start building with Ankr Advanced API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Ankr Advanced API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Ankr Advanced API, keeping it validated and agent-ready. Ankr Advanced API is a multichain JSON-RPC service that exposes account balances, blockchain stats, transaction history, NFT ownership and metadata, token holders, and on-chain logs across more than thirty supported networks behind a single endpoint. Each operation is invoked via the ankr_* method namespace (for example ankr_getAccountBalance, ankr_getNFTsByOwner) and returns normalised JSON across chains so agents do not have to learn each network's native RPC. Authentication is via an API key embedded in the multichain URL path.

Use Cases

Patterns agents use Ankr Advanced API API for, with concrete tasks.

★ Multichain Wallet Dashboard

Build a portfolio dashboard that shows native and token balances, NFT holdings, and recent activity for a user's wallets across Ethereum, BSC, Polygon, and other Ankr-supported chains. A single Ankr Advanced API key covers all networks via the multichain URL, so the agent issues one ankr_getAccountBalance call instead of spinning up an RPC connection per chain. Setup is short because each operation returns the same normalised JSON structure regardless of source network.

Call ankr_getAccountBalance via POST /?ankr_getAccountBalance with the user's wallet and a list of chains, then format the returned token balances into a dashboard view

NFT Collection Analytics

Monitor an NFT collection by combining ankr_getNFTHolders, ankr_getNFTsByOwner, and ankr_getNftTransfers to surface ownership concentration, recent flips, and per-wallet holdings. Agents use this for floor-watch alerts, whale tracking, or due-diligence workflows where the underlying chain (Ethereum, Polygon, BSC) should not change the calling code. Ankr's normalised metadata also reduces the post-processing required compared to raw chain RPCs.

Call ankr_getNFTHolders with the collection contract address, then ankr_getNftTransfers for the last 24 hours and surface the top 10 buying wallets

On-Chain Activity Monitoring

Watch a smart contract's events by polling ankr_getLogs with a topic filter and block range, then use ankr_getInternalTransactionsByBlockNumber to expand into internal-call detail when an event triggers further on-chain activity. This avoids running a self-hosted indexer for low-to-medium volume monitoring use cases such as alerting on governance votes, liquidations, or DAO treasury movements.

Call ankr_getLogs with the contract address and the Transfer topic for the last 1000 blocks, then drill into ankr_getInternalTransactionsByParentHash for any transaction over a threshold value

AI Agent Wallet Inspector via Jentic

An AI agent answering 'what's in this wallet?' style questions uses Ankr Advanced API through Jentic to fetch balances, NFTs, and recent transfers without managing the multichain key directly. Jentic's intent search routes the agent to the correct ankr_* method with its parameter schema, and the API key is loaded from the vault at execution time so it never enters the agent's tool context.

Search Jentic for 'get NFTs owned by a wallet', load ankr_getNFTsByOwner, and execute with the user-supplied address and chain list to return a normalised NFT list

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/?ankr_getAccountBalance

Retrieve native and token balances for a wallet across chains

POST

/?ankr_getNFTsByOwner

List all NFTs owned by a given wallet

POST

/?ankr_getNFTHolders

List holders of a given NFT collection

POST

/?ankr_getNftTransfers

Retrieve NFT transfer history for a wallet or collection

POST

/?ankr_getLogs

Fetch on-chain event logs filtered by topic and block range

POST

/?ankr_getBlockchainStats

Return per-chain block height, block time, and gas stats

POST

/?ankr_getNFTMetadata

Retrieve metadata for a single NFT token

POST

/?ankr_getInternalTransactionsByParentHash

List internal transactions for a given parent transaction

POST

/?ankr_getAccountBalance

Retrieve native and token balances for a wallet across chains

POST

/?ankr_getNFTsByOwner

List all NFTs owned by a given wallet

POST

/?ankr_getNFTHolders

List holders of a given NFT collection

POST

/?ankr_getNftTransfers

Retrieve NFT transfer history for a wallet or collection

POST

/?ankr_getLogs

Fetch on-chain event logs filtered by topic and block range

Why though Jentic?

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

Credential isolation

Ankr's URL-embedded API key is stored encrypted in the Jentic vault. Agents receive scoped execution access only — the multichain URL with the key never enters the agent's prompt or tool context, which matters because the key controls billable RPC quota.

Intent-based discovery

Agents search by intent (e.g., 'get NFTs owned by a wallet') and Jentic returns the matching ankr_* method with its parameter schema, so the agent does not need to memorise method names like ankr_getNFTsByOwner from the docs.

Time to first call

Direct Ankr integration: 1-2 days to handle the multichain URL pattern, per-method parameter shapes, and 429 backoff. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Alchemy API

Alchemy is a competing multichain RPC provider with its own enhanced NFT and token APIs.

Choose Alchemy when the agent already uses Alchemy SDKs or needs Alchemy-specific webhooks and notify features.

Alternative

Covalent GoldRush API

Covalent GoldRush provides multichain wallet, token, and NFT data through a unified REST surface.

Choose Covalent when the agent prefers a REST-style interface and pre-aggregated portfolio endpoints over Ankr's ankr_* JSON-RPC methods.

Complementary

QuickNode API

QuickNode provides standard JSON-RPC nodes for transaction broadcasting that pair with Ankr's enhanced reads.

Choose QuickNode when the agent needs to broadcast transactions or call raw eth_* methods that Ankr's enhanced surface does not cover.

FAQs

Specific to using Ankr Advanced API API through Jentic.

Why is there no official OpenAPI spec for Ankr Advanced API?

Ankr does not publish an OpenAPI specification — the Advanced API is documented as JSON-RPC methods. Jentic generates and maintains this spec so that AI agents and developers can call Ankr 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 Ankr Advanced API use?

Ankr uses an API key embedded directly in the multichain RPC URL path (https://rpc.ankr.com/multichain/{API_KEY}). There is no separate Authorization header. Through Jentic the API key is stored in the encrypted vault and the URL is reconstructed at execution time so the key never enters the agent's prompt context.

Can I query NFTs across multiple chains with the Ankr Advanced API?

Yes. ankr_getNFTsByOwner, ankr_getNFTHolders, and ankr_getNftTransfers accept a blockchain list parameter, so a single call can span Ethereum, Polygon, BSC, and other supported networks and return normalised metadata.

What are the rate limits for the Ankr Advanced API?

The OpenAPI spec does not declare explicit rate limits. Ankr enforces per-plan throughput on the live service, so check your Ankr dashboard for the exact RPS for your tier and back off on 429 responses.

How do I look up a wallet's NFTs with the Ankr Advanced API through Jentic?

Run pip install jentic, then search Jentic for 'get NFTs owned by a wallet'. Jentic returns ankr_getNFTsByOwner with its parameter schema. Execute the call with the wallet address and the list of chains you want covered.

Does the Ankr Advanced API support sending transactions?

No. The Advanced API surface in this spec is read-only — balances, transfers, logs, and NFT data. Transaction broadcasting is handled by Ankr's standard JSON-RPC node endpoints, not by the ankr_* method namespace covered here.