{"coverage_note":"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 \u2014 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 \u2014 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.","human_handoff_required_for":[{"action":"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 \u2014 a human must confirm whether a plan upgrade or alternative provider is required to complete the transaction.","evidence":[{"description":"Infura's debug and trace RPC methods and archive data access are restricted to the Decentralized Infrastructure Network (DIN), which is only available on Growth or Custom plans \u2014 this limitation is not prominently surfaced during API onboarding or at the point of method invocation.","reference":"https://docs.infura.io/infura/networks/ethereum/json-rpc-methods"}],"last_checked_date":"2026-06-28"},{"action":"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 \u2014 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.","evidence":[{"description":"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 or advance in-flow warning to the calling application.","reference":"https://docs.infura.io/infura/learn/rate-limits"}],"last_checked_date":"2026-06-28"}],"record_verification":{"last_checked_agentic_scan":"2026-06-29","last_checked_human_verified":null},"vendor_id":"infura","verified_discrepancies":[{"actuals":"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 \u2014 including severing active WebSocket connections \u2014 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.","discrepancy_start_date_est":"Unconfirmed; DIN-gating of debug/trace methods has been present in documentation at least as of 2024","evidence":[{"description":"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.'","reference":"https://infura.io/docs/ethereum/json-rpc/ratelimits"},{"description":"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.","reference":"https://docs.metamask.io/services/how-to/avoid-rate-limiting/"}],"interim_guidance":"Before using Infura in any agentic workflow: (1) Verify the active plan tier \u2014 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.","last_checked_date":"2026-06-29","status":"active","type":"undisclosed_constraint_discrepancy","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)."}]}