GetBlock RPC competitor monitor — 2026-07-20
GetBlock RPC competitor monitor — 2026-07-20
Criterion of the day: AI/agent tooling and MCP/CLI/dev workflow support (ai-agent-tooling; query hint: "AI agents MCP CLI developer workflow").
Summary
What really changed / new baseline
This is the first full monitored run after bootstrap, so every tracked page is marked baseline rather than a true diff vs yesterday. The useful signal today is competitive positioning around AI-native developer workflows:
- QuickNode is the most explicit in agent packaging. It has a dedicated [Quicknode for AI Agents](https://www.quicknode.com/agents) page, top-nav "Agents", x402/MPP payment flows, Agent Subscription API, Blockchain Skills and a hosted MCP server.
- Alchemy is turning AI workflow into content + product narrative. Blog and homepage/pricing banners promote [usage data in Alchemy CLI](https://www.alchemy.com/blog/usage-data-alchemy-cli); the blog lists [Alchemy MCP Server](https://www.alchemy.com/blog/alchemy-mcp-server) and [Claude Code setup](https://www.alchemy.com/blog/setup-claude-code-with-alchemy) posts.
- Chainstack is also AI-forward. Main nav mentions "AI-ready infrastructure" and "Chainstack MCP"; docs advertise
/llms.txt,llms-full.txt, markdown pages and a search MCP server. - Moralis positions around AI-native data, not only RPC. Homepage/pricing/menu mention "Cortex API — AI-native, fully LLM-ready crypto data layer"; docs include
Ask Assistant,Open in ChatGPT,/llms.txt, and a Cortex OpenAPI file. - Infura and Ankr have LLM-ready docs, but weaker agent product packaging in monitored pages. Infura docs expose
/llms.txtand "Search or Ask AI". Ankr docs expose LLM-friendly markdown and/llms.txt; AI keyword hits are mostly Kite AI chain support and docs format.
Unchanged / no true deltas
changed_vs_last=baselinefor all fetched pages because this is the first daily snapshot instate.json.- No reliable pricing change can be asserted vs prior day. Pricing observations below are current baseline only.
Blocked / limited
- QuickNode
/changelogreturned 404. - Alchemy
docs_chainsand/customer-storiesreturned 404 in the pre-run fetch, although the 404 page itself still exposed nav/customer-story links. - No web-search tool was available; supplemental validation used direct HTTP fetches of known pages (
/agents,/llms.txt, blog pages). Claims below are grounded in pre-run samples or direct URL fetches.
Competitor notes
QuickNode
Sources: [home](https://www.quicknode.com/), [pricing](https://www.quicknode.com/pricing), [enterprise](https://www.quicknode.com/enterprise), [blog](https://www.quicknode.com/blog), [chains](https://www.quicknode.com/chains), [agents](https://www.quicknode.com/agents).
- Positioning: "The Blockchain Development Platform" with top-nav "Agents". Also promoting Quicknode Earn across pages.
- AI/agent tooling: Dedicated [Quicknode for AI Agents](https://www.quicknode.com/agents) page says: "Multi-chain blockchain infrastructure for AI agents" across 80+ chains and 130+ networks. It describes x402, MPP stablecoin pay-per-request, Agent Subscription API, Admin API, Blockchain Skills and MCP.
- MCP/CLI/dev workflow: QuickNode page lists hosted MCP endpoint
https://mcp.quicknode.com/mcp,claude mcp add quicknode --transport http ..., localnpx -y @quicknode/mcp, and support for Claude Code/Desktop, Cursor, VS Code, Windsurf, Zed. It says MCP can create endpoints, configure security, set rate limits, review billing and monitor usage; blockchain data access remains via x402/RPC endpoints. - Pricing/packaging baseline: Enterprise page claims contractual 99.99% uptime SLAs, volume discounts, early chain/network access, compliance reports, named solutions architect and 24/7 on-call engineering.
- Content/release delta: No true delta yet. AI page is already productized enough to treat as a core competitive pillar.
Alchemy
Sources: [home](https://www.alchemy.com/), [pricing](https://www.alchemy.com/pricing), [enterprise](https://www.alchemy.com/enterprise), [blog](https://www.alchemy.com/blog), [Usage data CLI](https://www.alchemy.com/blog/usage-data-alchemy-cli), [MCP Server](https://www.alchemy.com/blog/alchemy-mcp-server), [Claude Code setup](https://www.alchemy.com/blog/setup-claude-code-with-alchemy).
- Positioning: "The complete blockchain developer platform" and "Infrastructure that moves billions at scale"; homepage claims 150,000+ teams, 100+ blockchains, 99.99% uptime and 71% of top crypto apps using Alchemy.
- AI/agent tooling: Blog page prominently lists
MCP for blockchain data: every Alchemy API in your AI assistantdated July 1, 2026. Extracted metadata says the MCP server gives AI assistants 168 tools across 100+ chains with OAuth sign-in and no local install. - CLI/dev workflow: Homepage/pricing banner says: "NEW: Usage data now live in the Alchemy CLI. Pull compute, costs, and usage trends over time, straight from your terminal." Blog metadata for
usage-data-alchemy-clisays the same usage data is available to AI agents through the Alchemy MCP Server. - Claude/Codex workflow: Blog lists
Set up Claude Code with Alchemy in 60 secondsdated July 15, 2026; metadata says one command connects Claude Code and gives a coding agent live data across 100+ chains: prices, balances, NFTs, transfers and simulation. - Pricing baseline: Free: 25 RPS, 5 apps/5 webhooks, 30M CU/month; PAYG starts at 300 RPS and as low as $0.40/1M CUs; Enterprise starts at 1000 RPS.
- Blocked: Fetched
docs_chainsand/customer-storiesURLs returned 404, so chain/customer proof should be verified through alternative URLs in a future run.
Infura
Sources: [home](https://www.infura.io/), [pricing](https://www.infura.io/pricing), [networks](https://www.infura.io/networks), [blog](https://www.infura.io/blog), [docs](https://docs.infura.io/), [llms.txt](https://docs.infura.io/llms.txt).
- Positioning: "Build, Scale, Disrupt"; now part of Consensys. Highlights high availability APIs, Consensys distribution, MetaMask SDK/Snaps/Linea synergy, and decentralization via DIN.
- AI/agent tooling: Docs page explicitly says: "For AI agents: a documentation index is available at
/llms.txt" and offers markdown pages by.md/Accept header. Docs UI includes "Search or Ask AI". - MCP/CLI: No dedicated MCP or CLI product surfaced in monitored pages today. Current AI-readiness is documentation accessibility rather than an agent control plane.
- Pricing baseline: Core free with 3M daily credits and 500 credits/sec; Developer $50/month with 15M daily credits and 4K credits/sec; Team $225/month with 75M daily credits and 40K credits/sec; Enterprise custom.
- Other notable baseline: IPFS access notice says Infura is limiting IPFS service access to pre-qualified customers.
Chainstack
Sources: [home](https://chainstack.com/), [pricing](https://chainstack.com/pricing/), [protocols](https://chainstack.com/protocols/), [enterprise](https://chainstack.com/enterprise/), [blog](https://chainstack.com/blog/), [docs](https://docs.chainstack.com/docs/platform-introduction), [llms.txt](https://docs.chainstack.com/llms.txt).
- Positioning: "Fast and Reliable Blockchain Infrastructure Provider"; strong emphasis on Global Nodes, Managed Dedicated Nodes, and new Self-Hosted Nodes.
- AI/agent tooling: Main navigation explicitly includes "AI-ready infrastructure" and Resource link "Chainstack MCP". Docs navigation includes
MCP,llms-full.txt; docs overview says the complete documentation index is at/llms.txt. - LLM docs: Direct
/llms.txtfetch says every page is available as Markdown by appending.md, "via the search MCP server," and in sitemap. This is a strong dev workflow signal even if the MCP doc URL guessed during supplemental checks returned 404. - Pricing/features baseline: Self-Hosted Nodes are promoted across home/pricing/protocols/blog as a new product: user-managed nodes on any infrastructure with automated deployment, self-healing and lifecycle management.
- Content baseline: Site nav includes comparison pages "Chainstack vs QuickNode vs Alchemy" and "Migration Guide" — likely SEO/conquesting to monitor.
Ankr
Sources: [home](https://www.ankr.com/), [RPC](https://www.ankr.com/rpc/), [enterprise](https://www.ankr.com/enterprise/), [blog](https://www.ankr.com/blog/), [docs](https://www.ankr.com/docs/), [llms.txt](https://www.ankr.com/docs/llms.txt).
- Positioning: "The Fastest Web3 Infrastructure" and "Build any Web3 project with leading performance". Home claims 56 ms average response time, 99.99% uptime and 70+ blockchains.
- AI/agent tooling: Docs page says: "For AI agents: an LLM-friendly Markdown version of every page is available by appending
.md... The full documentation index is at https://www.ankr.com/docs/llms.txt". - MCP/CLI: No dedicated MCP/CLI control plane surfaced in monitored pages today.
/llms.txtkeyword hits include Kite AI chain docs, but that is chain coverage rather than agent tooling. - Enterprise baseline: Enterprise page claims 30+ blockchains for tailored RPC/API, geo-distribution across 24 metros, custom throughput over 25,000 RPS, dedicated Slack/Telegram support and fixed monthly payment options.
- News baseline: Latest blog sample includes
Trust Wallet Needed More Supported Chains From Its Provider. Ankr Delivered.dated July 16, 2026, and an Ankr community letter dated July 15, 2026.
Moralis
Sources: [home](https://moralis.com/), [pricing](https://moralis.com/pricing/), [chains](https://moralis.com/chains/), [enterprise](https://moralis.com/enterprise/), [blog](https://moralis.com/blog/), [docs](https://docs.moralis.com/), [llms.txt](https://docs.moralis.com/llms.txt).
- Positioning: "Enterprise-Grade Web3 APIs" and broad data platform: Data APIs, Streams, Datashare, Data Feeds, RPC Nodes.
- AI/agent tooling: Main nav/product menu includes "Cortex API — New AI-native, fully LLM-ready crypto data layer". Docs include
Ask Assistant,Open in ChatGPT,/llms.txt, and direct/llms.txtreferences to a Cortex OpenAPI file. - MCP/CLI: No explicit MCP or CLI product was found in monitored pages today; AI positioning is data-layer/API-first.
- Enterprise baseline: Enterprise page emphasizes audit-grade data, unified schemas, real-time and historical coverage, SOC 2 Type II and enterprise SLAs.
- Chain coverage baseline: Docs overview says Moralis supports 30+ chains; menu says high-performing RPC nodes for all major chains.
GetBlock implications
Sales
- Prepare an objection-handling card for: "Do you have MCP / Claude Code / Cursor integration like Alchemy or QuickNode?" QuickNode and Alchemy now have concrete assets buyers can name.
- For enterprise prospects, contrast GetBlock reliability/support with competitors that now bundle AI workflows into enterprise infrastructure narratives.
- Track QuickNode agent payments (x402/MPP) as a procurement wedge for autonomous agents; this could change how small AI teams try RPC vendors.
Product marketing
- Add a visible "AI agents / LLM-ready RPC" angle to GetBlock developer pages if product support exists; if not, mark as roadmap gap.
- Publish a simple GetBlock
llms.txt/markdown docs inventory and an "Open in ChatGPT/Claude/Cursor" workflow. This is low-cost and narrows the perceived gap vs Infura/Ankr/Moralis docs. - Consider a branded MCP server or MCP recipe that lets developers create/read endpoints, inspect usage, and retrieve chain docs.
Content
- Content cluster to build:
GetBlock MCP server,Use GetBlock RPC with Claude Code,Cursor + GetBlock,x402 payments for blockchain RPC,LLM-ready RPC docs. - Competitive SEO: Chainstack is openly targeting "vs QuickNode vs Alchemy" and migration pages; GetBlock should refresh comparison/migration pages with AI-workflow sections.
- Developer tutorial: "Ask an AI agent to query balances/transfers over GetBlock RPC" with reproducible code and supported chains.
Opportunities
- High priority: Build or publish GetBlock AI-agent workflow assets:
llms.txt, markdown docs, MCP recipe/server, and Claude/Cursor/Codex setup pages. - Medium priority: Evaluate x402/agent payment flow feasibility for RPC credits/API keys.
- Medium priority: Produce comparison content against QuickNode/Alchemy/Chainstack specifically on AI-agent developer workflow.
Tomorrow seed
state.json only shows one used criterion (ai-agent-tooling) and no visible upcoming criterion queue. Next criterion is not inferable from current state; tomorrow's pre-run JSON should supply it.