icy.tools NFT Analytics API
70
AI ReadinessAI-Aware (A-)70/100
Agent-ready OpenAPI document · curated by JenticAnalyticsBusiness IntelligenceapiKey1 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Query NFT collection analytics, trending sets, wallet activity, and token-level data across EVM chains via a single GraphQL endpoint.
Use for: Get the trending NFT collections in the last 24 hours, Retrieve a wallet's NFT holdings and recent sales, Find the floor price history for a specific NFT collection, List all sales for a given token ID in a contract
Not supported: Does not handle on-chain transactions, wallet signing, or NFT minting - use for read-only NFT analytics queries only.
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.
Install Jentic One Beta
Connect the icy.tools NFT Analytics API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the icy.tools NFT Analytics 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ficy.tools%2Ficy-tools" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ficy.tools%2Ficy-tools" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 icy.tools NFT Analytics API.
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
Patterns agents use icy.tools NFT Analytics API for, with concrete tasks.
★ 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.
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.
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.
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.
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
1 endpoints — jentic publishes the only available openapi specification for icy.
METHOD
PATH
DESCRIPTION
POST
/graphql
Run any GraphQL query or mutation against the icy.tools NFT analytics schema
POST
/graphql
Run any GraphQL query or mutation against the icy.tools NFT analytics schema
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
I
icy.tools NFT Analytics API
- AI-Aware (A-)70/100
100
Foundational Compliance64
Developer Experience & Jentic Compatibility56
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
64
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
6%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
56
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
43%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
80%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using icy.tools NFT Analytics API through Jentic.
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.
GET STARTED