Ankr primary-source snapshot

Last reviewed: 2026-04-27 UTC

Project status snapshot

What the official materials say

1) Ankr presents as a multi-product infrastructure platform, not a single API

  • URLs:
  • Key takeaways:
    • The homepage frames Ankr around Web3 API, scaling services, staking solutions, and a DePIN of globally distributed nodes rather than around only one endpoint product
    • The docs home groups the product surface into Node API, Advanced API, contract automation, scaling services, staking, and tutorials
    • That combination makes Ankr look like a broader infrastructure platform and control plane rather than just a hosted RPC brand

2) The Node API surface is broad and chain-by-chain documented

  • URLs:
  • Key takeaways:
    • The docs home says the Node API exposes HTTPS and WebSocket RPC/REST endpoints and supports 80+ blockchains
    • The chains-list page is a giant first-party inventory of supported networks and methods, spanning EVM and non-EVM ecosystems with per-chain request examples and unsupported-method notes
    • This chain-by-chain documentation is a strong signal that Ankr’s real product surface is operational infrastructure, not just generic marketing copy

3) Advanced API adds indexed and multi-chain query surfaces above raw RPC

  • URLs:
  • Key takeaways:
    • The product page says Advanced APIs help developers make fewer requests, spend less per request, and query multiple chains at once
    • The docs say Advanced API optimizes, indexes, caches, and stores blockchain data for access-ready use and supports multi-chain requests in a single call
    • The documented API families — NFT, Query, and Token — make Ankr look partly like an indexed data platform in addition to an RPC provider

4) Scaling and automation products widen the operating surface

  • URLs:
  • Key takeaways:
    • The docs describe contract automation for time-based and event-based execution managed from a dashboard
    • The scaling-services section positions Ankr as a provider of sidechains or rollups plus extra marketplace components
    • These materials are important because they show Ankr operating higher in the stack than raw node hosting

5) Pricing and packaging reveal control-plane features

  • URLs:
  • Key takeaways:
    • The pricing page differentiates Node API and Advanced API rate limits and exposes WSS, gRPC, whitelists, statistics, and multi-project features
    • Enterprise packaging includes preferred chains, region orchestration, engineering support, and custom SLAs
    • This reinforces the idea that Ankr is selling managed operational control, not merely commodity endpoint access

6) The GitHub org confirms a broader developer-platform footprint

  • URLs:
  • Key takeaways:
    • The verified GitHub org is tied to ankr.com and exposes ankr.js, ankr-python-sdk, and game-focused SDKs
    • The repo mix supports the official claim that Ankr targets multiple developer workflows beyond simple RPC usage
    • GitHub is especially useful here because it confirms the platform still ships SDKs and ecosystem tooling, not just hosted APIs

Whitepaper / technical-doc status

  • No canonical standalone Ankr whitepaper or litepaper surfaced in this pass.
  • The strongest current primary sources are the official homepage, docs suite, Advanced API docs, pricing page, and verified GitHub org.
  • For future refreshes, the chain-list docs and GitHub org are likely the fastest places to detect expansion into new chains, SDKs, or product categories.

Research notes

  • Best current category for the library: blockchain infrastructure platform / multichain RPC and indexed API provider / rollup-sidechain and staking control plane.
  • Most important categorization clues:
    • 80+ chain Node API surface with chain-specific docs
    • indexed NFT / token / query APIs layered above raw RPC
    • contract automation and rollup/sidechain launch services
    • differentiated pricing for WSS, gRPC, whitelists, and orchestration features
    • verified GitHub org with SDKs and game tooling
  • Important caveat: coverage numbers vary by surface (for example 70+ chains on the homepage vs. 80+ in docs), so future refreshes should record the exact source of each claim instead of normalizing them.