Base URL
MCP
The Indexy MCP Server allows AI agents (Claude, GPT, etc.) to interact with the Indexy API using the Model Context Protocol. For setup instructions, configuration details, and source code, visit the Indexy MCP Repository.Available MCP Tools
Feedback
Indexy uses Writeback to collect telemetry. Please report your experience so we can improve. Outcomes to report:
Submit a report:
x402 Payments
Some endpoints require a small USDC payment on Base via the x402 protocol. Agents using the MCP with a Web3 wallet don’t need to do anything — payments are handled automatically. This only matters if you are calling the API directly from an external client. See the x402 guide for details.Auth (if you are not using MCP)
The Indexy API supports two authentication methods. Every request to a protected endpoint must use one of these methods.Method 1: API Key
The simplest way to authenticate. Include your API key as a Bearer token in theAuthorization header:
Method 2: ERC-8004 Web3 Authentication
Authenticate using an EIP-191 signature from a wallet that holds an ERC-8004 Agent Identity NFT. This method is designed for on-chain AI agents and does not require an API key. When Web3 credentials are present in a request, they take priority over API Key authentication. Required Headers Include these headers on every authenticated request:base, ethereum
How It Works
- Generate a signing message (see endpoint below)
- Sign the message with your wallet
- The API verifies the signature and checks that your address holds an ERC-8004 Agent Identity NFT on the specified chain
- If valid, you are authenticated and a user account is created automatically if needed
Rate Limits
The API enforces per-key rate limits. Default: 15 calls/minute. Rate limit info is returned in response headers:X-RateLimit-Limit- Maximum calls per windowX-RateLimit-Remaining- Remaining calls in current windowX-RateLimit-Reset- Timestamp when the window resets
Endpoints
Get Index by ID
Retrieve detailed information about a specific index.
Response Example:
List All Public Indexes
Retrieve a paginated list of all public indexes, with optional filters. Returns indexes with their coin composition. This endpoint requires an x402 payment of 0.01 USDC per index returned (total cost =0.01 × results returned). See the x402 guide for details.
Response Example:
Agent Index Management
These endpoints allow authenticated agents to create and manage their own indices. All indices created via these endpoints are marked asindex_category = 'agentic'.
Supported Networks
Token networks use CoinGecko naming conventions. Use these identifiers in thenetwork field when specifying assets:
For a full list, refer to the CoinGecko Networks API.
Create Index
Create a new cryptocurrency index.
Response Example (201):
Update Index
Update an existing index you own. Supports two modes: metadata-only updates or complete rebalancing.
Mode 1: Metadata Only
Update name, description, or methodology fields without changing assets:
List My Indexes
List all indices created by the authenticated agent.
Response Example:
Get My Index Details
Get detailed information about a specific index you own, including its asset composition.
Response Example:
List KPIs
Retrieve all available KPIs that can be used to filter index data.Get KPI Data for Indexes
Retrieve KPI values for indexes with time range filtering.
Grouped Response Example (default):
group_by_index=false):
Get Index Highlights
Retrieve highlighted/featured indexes by category.
Response Example:
Get Index Mindshare
Mindshare represents “market attention” or popularity of coins and indexes. It compares a 7-day mindshare KPI against the previous period and calculates the percentage change.
Response Example: