Ankr

• Name: Ankr
• URL: https://www.ankr.com/
• Category: blockchain infrastructure platform / multichain RPC and indexed API provider / chain-services and staking workflow company
• Tags: ethereum-ecosystem bnb-chain
• Summary: Ankr belongs as an entity note, not a protocol note. The useful cut is that a named company operates a broad chain-access and operations control plane spanning managed RPC, indexed APIs, automation, chain-launch services, and staking under one brand. The practical leverage sits in credential issuance, endpoint policy, indexing semantics, supported-chain exposure, deployment defaults, and how much of a team’s app or staking workflow hardens around Ankr’s managed surface.
• What it does:
  • Provides public, premium, and enterprise RPC / REST / WebSocket access across a large set of blockchains through its Node API product
  • Offers higher-level indexed Advanced API surfaces for NFT, token, and query workflows so developers can request prepared blockchain data instead of building every indexing path themselves
  • Ships contract-automation tooling for time-based or event-based smart-contract execution from dashboard-managed workflows
  • Markets scaling services for sidechain or rollup launches plus adjacent marketplace components for custom chain deployments
  • Runs staking and liquid-staking products alongside developer tooling, making the company both app-facing and asset-operation-facing
• Key claims:
  • The homepage says Ankr delivers 56 ms average response time, 99.99% uptime, support for 70+ blockchains, and a DePIN-backed global node footprint spanning 30+ regions and billions of daily RPC requests
  • The docs home says Ankr’s products are powered by a globally distributed and decentralized network of nodes and groups them into Node API, Advanced API, contract automation, scaling services, staking, and tutorials
  • The Node API docs say developers can interact with 80+ supported blockchains, which is slightly broader than the homepage’s 70+ figure and worth preserving as a surface-level coverage discrepancy rather than smoothing away
  • The Advanced API docs say Ankr optimizes, indexes, caches, and stores blockchain data, supports multi-chain requests in a single call, and exposes NFT, query, and token methods across multiple mainnets and testnets
  • The pricing page shows Ankr selling not just simple HTTPS RPC but also WSS, gRPC, whitelists, statistics, and differentiated rate-limit tiers, which reinforces the control-plane framing
  • The verified GitHub organization exposes JavaScript and Python SDKs plus ecosystem tooling, which confirms a broader developer-platform posture beyond a single API gateway
• Whitepaper: No canonical standalone Ankr whitepaper or litepaper surfaced in this pass. The clearest current source of truth remains the official site, docs suite, pricing pages, and verified GitHub organization; see ../whitepapers/ankr-primary-sources-2026-04-27.md.
• Sources:
  • https://www.ankr.com/
  • https://www.ankr.com/docs/
  • https://www.ankr.com/docs/rpc-service/chains/chains-list/
  • https://www.ankr.com/docs/advanced-api/overview/
  • https://www.ankr.com/advanced-api/
  • https://www.ankr.com/rpc/pricing/
  • https://github.com/Ankr-network

Internal linkages

• Legacy project-layer alias kept for old links: ankr.
• Keep this note on the strongest operator-platform contrasts: alchemy, quicknode, and blockdaemon.
• Reusable lens: once the same vendor handles RPC, indexed data, automation, chain-launch services, and staking, the dependency is on the company-run workflow shell rather than on a neutral endpoint utility.

Protocol / company boundary

• Keep ankr only as an alias so legacy links keep resolving without pretending Ankr is a distinct protocol layer.
• This company note is the real control-surface note: API admission, indexed-data semantics, automation policy, chain-launch packaging, and staking workflow all live inside one named operating company.
• That split matters because the useful question is not what is the Ankr protocol? but which company controls the managed multichain access, indexing, automation, and staking shell developers and operators are actually depending on?

Control surface

• Practical authority sits in API keys, rate limits, supported-chain admission, caching and indexing semantics, automation triggers, deployment defaults, and the way staking or other higher-level services are bundled into the same operator surface.

• Read Ankr as managed developer and operations middleware, not as a protocol in its own right.

• Last reviewed: 2026-08-10 UTC