ceven

Blocknative

Monitors the blockchain mempool in real time to track pending transactions and optimizes gas fees for immediate inclusion.

Try Blocknative in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Blocknative integration

    • Describe the outcome and Ceven picks the right Blocknative calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Blocknative data, across all 10 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Blocknative access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Blocknative, when, and on whose behalf.
    • The agent pauses and asks when Blocknative is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Blocknative.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Blocknative action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Blocknative, and when to use it.

Configure Mempool Filters
Use this to set up event filters and abi decoding for ethereum mempool transactions after a websocket connection is active.
Get Gas Price Distribution
Pull the current mempool gas price distribution breakdown to analyze trends or set fee strategies.
Get Gas Oracles
Retrieve metadata on supported gas oracles per chain to discover available on chain estimation tools.
Get Gas Prices
Fetch gas price estimates for specific inclusion probabilities for the next block or ten second window.
Get Supported Chains
Pull metadata on all supported chains available for Blocknative gas services.
Get Base Fee Estimates
Get real time predictions for base fee and blob base fee for the next five blocks with confidence intervals.
Subscribe Multichain
Generate websocket subscription details to track a transaction hash or account across multiple chains.
Subscribe Transaction Hash
Subscribe to state change events for a specific ethereum transaction hash via websocket.
Unsubscribe Multichain
Stop monitoring an address or transaction across chains to clean up SDK resources.
Unsubscribe Transaction Hash
Stop receiving state change events for a specific ethereum transaction hash.

10 actions · scroll to see them all

Frequently asked questions

Ceven manages the lifecycle of the websocket connection on your behalf. When you trigger a subscription action for a transaction hash or multichain event, the agent establishes the connection to the Blocknative gateway and maintains the heartbeat. It listens for the specific JSON RPC responses and maps those events directly into your workflow context. You do not need to manage the socket open or close events manually. Once the transaction reaches a final state like mined or dropped, the agent can automatically trigger the unsubscribe action to ensure you are not wasting connection slots or hitting concurrency limits set by your Blocknative plan.
Yes, provided the network is listed in the supported chains metadata. Ceven calls the supported chains endpoint first to verify the network ID. If the network is supported, the agent can pull gas price estimates and base fee predictions. It is important to note that gas dynamics on Layer 2 networks often differ from Ethereum mainnet, especially regarding blob fees and sequencer batching. Ceven accounts for these differences by using the specific oracle metadata provided by Blocknative to ensure the fee estimates are relevant to the target chain and not just a generic Ethereum estimate.
Because Ceven uses the Blocknative subscription model, it receives a real time notification the moment a transaction is no longer seen in the mempool. The agent can then trigger a fallback workflow. For example, if a high priority trade is dropped, Ceven can immediately pull the latest gas price distribution to determine why it was dropped and then suggest a new gas price for a replacement transaction. This prevents the silent failure common in standard RPC calls where you only realize a transaction failed after several blocks have passed without inclusion.
Yes, Blocknative enforces strict rate limits and concurrency caps based on your specific API tier. For example, free or lower tier accounts have a limited number of simultaneous websocket subscriptions and a cap on the number of requests per second for gas price endpoints. If Ceven hits a 429 Too Many Requests error, the agent will implement an exponential backoff strategy. However, if you are running a high frequency monitoring workflow, you may need to upgrade your Blocknative plan to increase your concurrency limit to avoid delays in transaction tracking.
Blocknative uses historical data and current mempool pressure to provide these estimates, offering both 50 percent and 99 percent confidence intervals. Ceven presents these as a range rather than a single number. For critical transactions, the agent is configured to use the 99 percent confidence estimate to ensure the transaction is not underpriced during a volatility spike. For non urgent tasks, it can target the 50 percent estimate to save on costs. These predictions are updated every few seconds, so the agent always uses the freshest data before suggesting a fee.
Yes, by using the configure mempool filters action, Ceven can pass the necessary ABI decoding information to Blocknative. This allows the agent to see not just that a transaction is pending, but exactly which function is being called and with what arguments. For instance, if you are monitoring a specific DeFi vault, Ceven can detect a pending deposit of a specific amount and trigger a response. The ABI must be provided or available in the workflow configuration for the agent to map the raw hex data into human readable fields.
Ceven fully supports the multichain SDK capabilities of Blocknative. You can instruct the agent to watch a single wallet address across all supported chains simultaneously. When a transaction is detected on any of those chains, the agent identifies the chain ID and pulls the relevant chain specific metadata. This is particularly useful for users managing assets across multiple EVM compatible networks who want a single stream of alerts for all their movements without setting up individual monitors for every single network they use.
Ceven uses the get gas oracles tool to dynamically find which on chain oracles are currently available and supported for a given network. Instead of relying on a hard coded list, the agent queries Blocknative for the most current metadata. This ensures that if Blocknative adds a new oracle or if an existing one becomes deprecated, the agent automatically switches to the available source. This provides a layer of resilience for automated fee strategies that cannot afford downtime due to a broken oracle connection.

Alternatives to Blocknative

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Alchemy logoAlchemyInfura logoInfuraTenderly logoTenderly

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Blocknative and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free