Summary
Token API continues to be Pinax’s number one priority and this month we hit a few major milestones, with the launch of new paid tiers, support for batched queries, new API versioning and route structures, and more.
Looking back (what was delivered)
Token API BD
- Launched new paid tiers for Token API
- Denis conducted a demo with Marcus on X to showcase how easy it is to build AI agents using Token API data.
New Token API Features
- New batched query support
- Added batching capability for multiple values in a single request
- API Versioning & Route Structure
- Introduced /v1 API prefix for all endpoints, enabling better version control for future breaking changes
- Reorganized routes under /v1/evm/* and /v1/svm/* for clearer separation
- Consolidated token and NFT endpoints under unified namespaces
- Updated route structure was a pre-requisite for enabling batched queries
- New Query Parameters
- start_block and end_block - Filter results by block range
- include_null_balances - Optionally include zero/null balances in balance queries
- input_token and output_token - More explicit token filtering for pool queries (replaces generic tokenparameter)
- Enhanced Authentication
- Added API key authentication method via X-Api-Key header, enabling paid tiers in The Graph Market
- Added plan-based API limits
Token API fixes and improvements
- Improved performance of swaps, transfers and holders endpoints for EVM and SVM
- Fix SVM Native Balances SQL
- Fix SVM Pools SQL
- Fix SQL ORDER BY for consistent pagination of results
- Improvements to transfers endpoint to force filtering timestamp & block_num first
- A bunch of bug fixes and refactoring
Looking ahead (upcoming priorities)
A few key priorities for Token API to look forward to over the coming weeks:
- Support for Tron launching on November 6
- Updated spam scoring with added support for Polygon, Arbitrum One and Avalanche launching on November 6
- New Rest-MCP
- Continuing to work on optimizing Token API performance