/vendor/infura/AgentRouting.json or
/vendor/infura/AgentContext.json directly.
infura.io
Overview
Does infura.io support MCP?
No confirmed MCP support was found for infura.io as of 2026-06-29.
What agentic protocols does infura.io support?
As of 2026-06-29, infura.io has confirmed support for proprietary and self_declared_discovery.
Is infura.io's API publicly accessible or partner-gated?
Open.
Does infura.io explicitly prohibit automated access?
Yes. infura.io's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is infura.io agent-ready?
Partial. infura.io supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
Infura is a Web3/blockchain infrastructure provider (Ethereum, IPFS, multichain node APIs) with no evidence of involvement in the Agent2Agent protocol. The A2A launch partner list includes vendors such as Atlassian, Box, Cohere, Intuit, LangChain, MongoDB, PayPal, Salesforce, SAP, ServiceNow, and Workday — Infura does not appear among them. No A2A references appear on infura.io or blog.infura.io. Infura's domain focus is entirely distinct from the AI agent interoperability space this protocol addresses.
Infura (infura.io) is a Web3/blockchain infrastructure provider offering Ethereum and IPFS API access — structurally unrelated to ACP's retail commerce and checkout scope. Known ACP launch and early partners include URBN brands, Coach, Kate Spade, Revolve, Ashley Furniture, Salesforce/Agentforce, PayPal, and Meta; Infura appears in none of these lists. No evidence found connecting Infura to the Agentic Commerce Protocol in any capacity.
AP2 launched with 60+ named partners (Adyen, American Express, Coinbase, Mastercard, PayPal, Salesforce, Worldpay, Mysten Labs, etc.); Infura.io does not appear in any partner list or AP2-related announcement. Infura is an Ethereum/Web3 RPC infrastructure provider with no confirmed involvement in AP2's cryptographic payment-mandate stack. No vendor-specific evidence found.
No official Infura-published MCP server was found. The MCP servers that appear in search results (github.com/Qbandev/infura-mcp-server and github.com/deflang/infura-mcp) are community-built, third-party wrappers around Infura's public JSON-RPC API — not officially published or maintained by Infura/ConsenSys. Infura's own documentation at infura.io and docs.metamask.io contains no mention of an MCP server offering. Choosing not_found rather than confirmed_absent because Infura has made no specific public statement deprecating or refusing MCP; it simply has not published one.
No evidence found linking Infura to the Stripe/Tempo Machine Payment Protocol (MPP) launch or any associated partner list. Named MPP launch partners identified in public announcements include MultiversX and Lightspark; Infura does not appear among them. Infura's public footprint concerns Ethereum/IPFS node infrastructure and its own Decentralized Infrastructure Network (DIN), which is unrelated to MPP.
No evidence found that Infura (infura.io), a blockchain node and Web3 API provider, is among NLWeb's known launch or early adopter partners. Named NLWeb early participants include Chicago Public Media, Allrecipes, Eventbrite, Hearst/Delish, O'Reilly Media, Tripadvisor, and Shopify — none of which overlap with Infura's domain. No NLWeb-related endpoints or documentation were found at infura.io.
Infura.io is a Web3/blockchain infrastructure provider (Ethereum RPC, IPFS, MetaMask backend) with no connection to the Universal Commerce Protocol, which is a Google/Shopify-led retail checkout standard. No evidence of UCP adoption, implementation, or partnership was found in any Infura documentation, announcements, or third-party coverage.
No evidence found that Infura (infura.io), a Web3 blockchain node and API provider, has implemented or announced support for the WebMCP browser-layer protocol. The WebMCP launch-partner ecosystem visible in search results centers on Cloudflare Browser Run and W3C/WebML working group contributors — none referencing Infura. The Infura partnership results found (Microsoft, Chainstack, Consensys DIN) are unrelated to WebMCP or browser-native agent tooling.
No evidence that Infura (infura.io) is a launch partner, listed adopter, or documented implementer of the x402 protocol. Known x402 ecosystem participants include Coinbase, Cloudflare, and Solana; Infura appears nowhere in any x402 partner or launch context. Infura's own site and blog coverage focuses on its Decentralized Infrastructure Network (DIN), multichain RPC services, and Ethereum/IPFS node access — none of which reference x402. Sketchiness and stability ratings left at insufficient_data as no Infura-specific x402 documentation surface was available to evaluate.
No evidence found that Infura (infura.io) has built or published an app for OpenAI's ChatGPT Apps platform using the Apps SDK. Searches surfaced Infura blog posts about using ChatGPT as a development tool, but no Infura-specific listing in the ChatGPT app directory or Apps SDK integration. The confirmed_absent designation is not warranted because Infura has made no public statement deprecating or refusing this platform; the absence is simply undocumented.
Blockchain node RPC access: proxied JSON-RPC endpoints for Ethereum and other EVM-compatible networks (e.g., Polygon, Arbitrum, Optimism), plus a Gas API (REST) providing real-time EIP-1559 gas fee estimates for EVM chains, and an NFT REST API (nft.api.infura.io) for querying NFT metadata, collections, ownership, and transfers across multiple chains. All three are distinct proprietary surfaces under the same API key scheme.
Infura exposes three documented proprietary API surfaces: (1) JSON-RPC node endpoints per network (e.g., mainnet.infura.io/v3/{API_KEY}), (2) a Gas API used internally by MetaMask wallet, and (3) a REST NFT API at https://nft.api.infura.io. All require an Infura API key obtained via self-serve dashboard signup. Primary docs at https://docs.infura.io.
AI agent documentation index for Infura API services (blockchain node endpoints, supported networks, and API methods), published at the root of the official Infura developer documentation domain
Multiple Infura documentation pages hosted at docs.metamask.io (the current home of Infura's developer docs, formerly docs.infura.io) explicitly advertise a machine-readable documentation index for AI agents at the path /llms.txt on that domain. The specific text observed: "For AI agents: a documentation index is available at /llms.txt" appears inline on pages such as https://docs.metamask.io/services/get-started/infura/. No equivalent self-declaration file was found on the infura.io root domain itself, and no AGENTS.md or /.well-known/agent files were identified.
Summary
Has agent interface: partial
Verify whether Infura's docs.metamask.io/llms.txt index is machine-readable and complete enough for agent discovery purposes; then assess whether Infura's proprietary JSON-RPC and REST APIs (Gas API, NFT API) are sufficient for the intended agent use case, and obtain an API key via self-serve signup at infura.io to begin integration.
AgentContext
Verified discrepancies
Vendor claim: Infura presents itself as offering broad Ethereum JSON-RPC API access including debug and trace methods, archive data querying, and expanded method support across its plans. Its documentation lists these capabilities as part of its feature set without prominently flagging that they are restricted to higher-tier plans via a separate infrastructure layer (DIN).
What actually happens: Debug and trace methods, archive data access, and failover support are not natively available through Infura on free or developer-tier plans. These capabilities are only accessible via Infura's Decentralized Infrastructure Network (DIN), which is explicitly limited to Growth or Custom plan subscribers. Additionally, when a project exhausts its daily credit quota, Infura halts all API access for the remainder of that UTC day — including severing active WebSocket connections — with no mid-transaction graceful degradation. An agent operating on a standard plan that attempts eth_debug, eth_trace, or archive-state queries will receive errors mid-execution without prior in-flow warning.
Agent guidance: Before using Infura in any agentic workflow: (1) Verify the active plan tier — if it is not Growth or Custom, do not attempt debug_, trace_, or archive-block calls, as they will fail mid-execution; (2) Pre-check remaining daily credits via the Infura dashboard before initiating multi-step transactions, and build in a fallback provider if credits may be exhausted; (3) For WebSocket-dependent workflows, implement reconnection logic since Infura will sever connections without notice upon quota exhaustion.
- Infura's own developer documentation states that debug/trace methods and archive data querying are provided via DIN, and that DIN failover is 'currently available on select networks for customers on Growth or Custom plans.'
- Infura's rate-limiting guidance confirms that once the daily credit limit is reached, 'your service will be halted for the rest of the day' and 'the WebSocket service will sever connections,' with no partial or graceful degradation for in-flight operations.
Human handoff required for
Escalate to a human when an agentic workflow receives unexpected RPC errors on debug_, trace_, or archive-block calls mid-execution, because these methods are silently unavailable on Free or Developer-tier Infura plans and will fail without an in-flow warning — a human must confirm whether a plan upgrade or alternative provider is required to complete the transaction.
Escalate to a human when all Infura API calls (including WebSocket connections) are suddenly severed or returning quota errors mid-execution, because Infura performs an immediate hard cutoff of all access upon daily credit exhaustion with no graceful degradation — a human must decide whether to wait until UTC midnight reset, top up credits, or reroute to a fallback provider to avoid incomplete or corrupted transaction state.
Five discrepancy categories were checked for infura.io. Pricing (discrepancy_pricing): searches found only Infura's published plan tiers and credit-based pricing model documentation — no hidden fees, deceptive pricing complaints, or regulatory actions were found. Availability (discrepancy_availability): searches found historical infrastructure outages handled via standard incident reporting, but no evidence of advertised API plans or features being unavailable or misrepresented at the point of access. Identity (discrepancy_identity): no evidence of merchant-of-record ambiguity, liability deflection, or counterparty identity issues was found; Infura operates as a straightforward subscription-based developer API service. Policy (discrepancy_policy): no regulatory findings, court filings, or credible reports of enforcement discrepancies were found; one third-party source noted the absence of a publicly documented refund policy, but this reflects a policy gap rather than a contradiction between stated and enforced terms. Undisclosed constraints (discrepancy_undisclosed_constraint): a confirmed finding was identified — debug/trace/archive RPC methods are silently restricted to Growth or Custom plan subscribers via a separate DIN infrastructure layer, and daily credit exhaustion triggers an immediate hard cutoff of all API access including live WebSocket connections, with no graceful degradation or in-flow warning; both constraints can cause agentic workflows to fail mid-execution.