canonical: https://jentic.com/apis/icy.tools/icy-tools

# icy.tools NFT Analytics API

Jentic publishes the only available OpenAPI specification for icy.tools NFT Analytics API, keeping it validated and agent-ready. icy.tools exposes a GraphQL endpoint for NFT collection analytics, trending data, wallet activity, and token-level metadata across Ethereum and other EVM chains. The single /graphql endpoint accepts arbitrary queries against schemas covering collections, sales, transfers, and wallet portfolios. Note: icy.tools was acquired by QuickNode and the original developer portal now redirects to QuickNode, so new integrations should plan migration accordingly.

## For AI agents

Query NFT collection analytics, trending sets, wallet activity, and token-level data across EVM chains via a single GraphQL endpoint.

## Scope

Does not handle on-chain transactions, wallet signing, or NFT minting - use for read-only NFT analytics queries only.

## Capabilities

- Query trending NFT collections by volume, floor price, and sales count over rolling windows
- Retrieve wallet-level analytics including held tokens, realized profit, and transfer history
- Fetch collection metadata such as supply, owners, traits, and contract address
- Pull token-level sale and transfer events for a given contract and tokenId
- Run ad hoc GraphQL queries combining filters across collections, wallets, and time ranges
- Surface floor price and sale price changes for a collection across configurable time windows

## Use cases

### NFT Portfolio Tracker

Build a portfolio dashboard that surfaces a wallet's current NFT holdings, realized profit, and recent sales. The /graphql endpoint accepts a wallet query that returns held tokens with current floor price and last sale. Most teams ship a basic tracker in a day because GraphQL collapses the request count compared to chain RPC calls.

Example prompt: Send a GraphQL query to /graphql for wallet 0x... that returns tokens with collection name, floor price, and last sale price

### Trending Collection Discovery

Surface trending NFT collections to feed a market-watch bot or newsletter. Send a GraphQL query against the trendingCollections field with a time window argument and a sort key to receive ranked collections with volume and floor price deltas. Refresh hourly to keep the feed current.

Example prompt: Query /graphql for trendingCollections sorted by 1h volume, returning the top 10 with name, floor price, and 1h volume change

### Collection Floor Monitoring

Monitor floor price for a specific collection and trigger an alert when it moves beyond a threshold. The GraphQL query returns floor price snapshots that can be polled at a configurable interval, then compared against a stored baseline before notifying users via a downstream channel.

Example prompt: Poll /graphql every 5 minutes for collection floor price and send a webhook when the price drops more than 10% from the prior reading

### AI Agent Market Research

An NFT research agent uses Jentic to find icy.tools operations matching 'analyze nft collection performance', loads the GraphQL schema, and runs a query that combines floor price, volume, and unique buyers. The agent returns a written summary to the user without the developer needing to learn the GraphQL schema in advance.

Example prompt: Use Jentic search 'analyze nft collection performance' to load the icy.tools schema, then execute a GraphQL query for collection volume and floor price over 7 days

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/graphql` | Run any GraphQL query or mutation against the icy.tools NFT analytics schema |

## Key resources

- **GraphQL** — Single /graphql endpoint that accepts queries across all icy.tools NFT analytics schemas

## Why Jentic

- **Setup:** Wiring the icy.tools NFT Analytics API by hand means passing your key in the X-API-Key header and shaping GraphQL queries against its single endpoint yourself. Through Jentic you install once, import the icy.tools NFT Analytics API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** icy.tools exposes one GraphQL endpoint and takes the query in the request body, so limit the agent to that read-only analytics operation. Because the API is read-only, the agent can query NFT analytics and nothing more.
- **Credential handling:** Your icy.tools API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get trending NFT collections' or 'query NFT sales analytics', and Jentic returns the matching icy.tools operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Alchemy API** — Alternative provider of NFT and EVM data with a JSON-RPC and REST surface
- **Covalent GoldRush API** — Multi-chain blockchain data API including NFT holdings and transfer history
- **QuickNode API** — Parent platform after icy.tools acquisition - provides RPC and broader chain infrastructure

## FAQ

### Why is there no official OpenAPI spec for icy.tools NFT Analytics API?

icy.tools does not publish an OpenAPI specification - the API is GraphQL-native. Jentic generates and maintains this spec so that AI agents and developers can call icy.tools NFT Analytics API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the icy.tools NFT Analytics API use?

The API uses an API key passed in the X-API-Key header on requests to /graphql. Through Jentic, the key is stored encrypted in your Jentic One instance and injected at execution time, so the raw key never enters the agent's prompt context.

### Can I query historical NFT sales with the icy.tools API?

Yes. Send a GraphQL query to POST /graphql that selects sale events for a given collection or wallet over a time window. The schema exposes price, buyer, seller, and timestamp fields, so an agent can build a full sales timeline for a contract.

### What are the rate limits for the icy.tools NFT Analytics API?

Rate limits are tied to your icy.tools (now QuickNode) plan and are not encoded in the OpenAPI spec. Plan-level request budgets apply per minute; design agents to handle 429 responses with backoff and to batch related fields into a single GraphQL query rather than firing many small ones.

### How do I run an icy.tools query through Jentic?

Run pip install jentic and import the SDK, then await client.search('analyze nft collection performance') to find the icy.tools /graphql operation. Load the schema and execute with a GraphQL query string. Run Jentic One, the self-hosted execution layer, for an API key.

### Does the icy.tools API still work after the QuickNode acquisition?

icy.tools was acquired by QuickNode and the developer portal now redirects to QuickNode. Existing API keys continue to work against the GraphQL endpoint, but new credentials and any future schema updates will come from QuickNode. Plan migrations accordingly when building long-lived integrations.

### Can I limit what my agent is allowed to do with the icy.tools NFT Analytics API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. This API exposes a single read-only GraphQL endpoint at POST /graphql, so you can scope the agent to just that one analytics operation and no other. That confines it to querying NFT collections, wallets, sales, and trending data, and blocks any attempt to reach beyond read-only analytics.