Blocknative provides real-time mempool monitoring and transaction management tools for public blockchains.
Blocknative provides real-time mempool monitoring and transaction management tools for public blockchains. On Nagent, Blocknative is exposed as a fully-configurable developer tools integration that any agent can call — 10 actions, and API key authentication. No code is required to wire Blocknative into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Blocknative to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Blocknative into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Blocknative, with input parameters and output schema. Drop these into any step of an agent built in Helix.
BLOCKNATIVE_CONFIGURE_FILTERSTool to configure filters and ABI decoding for Ethereum mempool transactions. Use after establishing a Blocknative WebSocket connection to set up event filters and decoding.
Input parameters
Nested object defining scope, filters, ABI decode and watch settings.
Must be the literal string 'put'.
Must be the literal string 'configs'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BLOCKNATIVE_GET_GAS_DISTRIBUTIONTool to retrieve the current mempool gas price distribution breakdown. Use when analyzing gas price trends or preparing fee strategies.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BLOCKNATIVE_GET_GAS_ORACLESTool to retrieve metadata on supported gas oracles per chain. Use when you need to dynamically discover all available on-chain gas estimation oracles across networks.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BLOCKNATIVE_GET_GAS_PRICESTool to fetch gas price estimates for specific inclusion probabilities. Use when you need gas price ranges for the next block or next ~10 seconds.
Input parameters
The chain ecosystem (e.g., 'ethereum', 'story', 'polygon').
The network chain ID. Default is 1 (Ethereum Mainnet).
The specific network within the system (e.g., 'mainnet', 'sepolia').
Up to 5 custom confidence levels to override defaults (99,95,90,80,70). For Ethereum Mainnet, values 1-99; for other chains, select from (99,95,90,80,70,50).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BLOCKNATIVE_GET_SUPPORTED_CHAINSTool to retrieve supported chains metadata. Use when discovering available networks for Blocknative gas services.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BLOCKNATIVE_PREDICTION_API_BASEFEE_ESTIMATESGet real-time gas fee predictions for Ethereum mainnet's next 5 blocks. Returns base fee, blob base fee, and priority fee estimates at multiple confidence levels (99% and 50%). Essential for optimizing transaction costs and timing. Predictions include current block context (block number, time since last block) and estimated fees in gwei.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BLOCKNATIVE_SUBSCRIBE_MULTICHAINGenerate WebSocket connection details to subscribe to real-time blockchain events (transactions or account activity) across multiple chains via Blocknative's Multichain API. Returns the WebSocket URL and subscription message payload needed to establish the connection and start receiving event notifications for a specific transaction hash or account address on any supported blockchain.
Input parameters
Transaction hash or account address to subscribe to (hex string starting with '0x').
(Account only) Optional JSON ABI array to decode contract input data on account events.
Type of subscription: 'transaction' for transaction events, 'account' for address events.
Hex-encoded chain ID, e.g. '0x1' for Ethereum Mainnet.
(Account only) Optional array of JSQL filter expressions to apply to account events.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BLOCKNATIVE_SUBSCRIBE_TRANSACTION_HASHTool to subscribe to transaction state change events of an Ethereum transaction hash. Use after establishing a Blocknative WebSocket connection to prepare the subscription message.
Input parameters
Ethereum transaction hash to monitor (must be in format: 0x followed by 64 hexadecimal characters).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BLOCKNATIVE_UNSUBSCRIBE_MULTICHAINTool to unsubscribe from events across multiple chains using the Multichain SDK. Use after stopping monitoring of an address or transaction to clean up resources, e.g., call: blocknative.unsubscribe({ id: '0x..', chainId: '0x1' }).
Input parameters
Transaction hash or account address to stop monitoring across chains.
Hex-encoded chain ID where the subscription exists, e.g. '0x1'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BLOCKNATIVE_UNSUBSCRIBE_TRANSACTION_HASHTool to unsubscribe from transaction state change events for an Ethereum transaction hash. Use after establishing a Blocknative WebSocket connection to prepare the unsubscription message.
Input parameters
Ethereum transaction hash to unsubscribe from. Must be a valid 66-character hex string starting with '0x' (e.g., '0x0b4c94c414f71ddd5e7a625fcaa83ff1f93e9a7ca37e0f577b488ac8fd786655').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 84 agents privately built on Nagent that already use Blocknative.
Build on Nagent
Connect Blocknative to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Blocknative, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Blocknative is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Blocknative is connected, you configure its 10 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Blocknative steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Blocknative event fires, the agent kicks off automatically.
Every Blocknative action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Blocknative ships with 10 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Blocknative together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Blocknative-based workflows tailored to your business.