Changelog

The Conduit Nodes documentation now includes an interactive JSON-RPC API reference and method playground, generated from Conduit’s OpenRPC specification with Fern’s OpenRPC support.

• Explore supported methods — Browse the Conduit Nodes JSON-RPC API by method, with descriptions, parameters, response schemas, and examples in one place.
• Try requests in the playground — Build JSON-RPC requests from the documented schemas and test them against your Conduit endpoint.
• See method pricing — Each method displays its Compute Unit cost so you can understand request cost while integrating.
• Use a machine-readable specification — The same OpenRPC source powers the reference, keeping the public API specification and rendered documentation aligned.

On August 3, 2026, Conduit transitions managed Blockscout deployments to Conduit Explorer. Every Conduit chain includes Conduit Explorer at no additional cost, with support for inspecting blocks and transactions, viewing transaction traces, verifying contracts, and interacting with contracts.

Conduit imports verified contracts from existing Blockscout deployments into its hosted contract verification server, so they remain available in Conduit Explorer. If a contract is missing after the migration, you can verify it again or contact Conduit support for help with bulk imports.

Starting August 4, 2026 at 12:00 PM PST, Conduit is updating RPC access rules to improve platform stability and security. Keyed traffic on Pro and Enterprise plans is unaffected.

• debug_* and trace_* methods require an API key — Unauthenticated calls to these methods are rejected.
• WebSocket connections require an API key — Anonymous WSS connections are rejected. Append your key to the WSS URL to keep subscriptions running.
• Lower rate limits for Public and Free traffic — Public drops to 25 req/s; Free drops to 250 req/s. Pro and Enterprise limits are unchanged. Retry gracefully on HTTP 429 responses.

You can now build and send an RPC request straight from your API key page, without copying anything into a terminal first. Pick a method and network inline in the example request, then send it and see the response rendered inline.

• Inline method and network selectors — Switch the JSON-RPC method and the target network directly in the curl example; the request URL fills in with your API key appended.
• Send from the dashboard — Use the send button to run the request against the selected endpoint and view a syntax-highlighted, expandable JSON response.
• Copy the full command — The copy button still copies the complete curl command so you can run it anywhere.

Added a Request Count by Method chart to the Nodes Metrics page and a toggle to switch the usage breakdown charts between stacked and line views.

Added a new CU Usage by API Key breakdown chart to the Nodes Metrics page.

Added CSV export for RPC metrics and a new CU Usage by Network breakdown chart to the Nodes Metrics page.

Renamed Rollups to Chains and updated navigation URLs. Added a dedicated Bundler page and new installation flow for Conduit Account Abstraction.

To improve the reliability and throughput of the RPC product, rate-limiting now works differently.

Rate limits are now enforced in Compute Units per second (CU/s). The documentation has been updated to reflect these changes. Read more here

Launched a new chain for RPC Nodes and quality of life and performance improvements to the app.

We’re kicking off changelogs and release notes along with our brand new documentation site!