Blocknative
for LuumenAI
Read mempool gas conditions, then set transaction filters as an approved step
Connect Blocknative and your agent can answer gas questions from the terminal: current price distribution, estimates at a given inclusion probability, base fee predictions for the next few blocks, and which chains and oracles are available. When you want the mempool watched differently, the agent writes the filter and ABI decoding config for you, showing the change first. Luumen authenticates with an API key.
The Blocknative toolbox
10 tools: 9 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Gas Price DistributionRetrieve the current mempool gas price distribution breakdown.
- ReadGet Gas OraclesRetrieve metadata on supported gas oracles per chain.
- ReadGet Gas PricesFetch gas price estimates for specific inclusion probabilities.
- ReadGet Supported ChainsRetrieve supported chains metadata.
- ReadGet Base Fee EstimatesGet real-time gas fee predictions for Ethereum mainnet's next 5 blocks.
- ReadSubscribe MultichainGenerate WebSocket connection details to subscribe to real-time blockchain events (transactions or account activity) across multiple chains via Blocknative's Multichain API.
- ReadSubscribe Transaction HashSubscribe to transaction state change events of an Ethereum transaction hash.
- ReadUnsubscribe MultichainUnsubscribe from events across multiple chains using the Multichain SDK.
- ReadUnsubscribe Transaction HashUnsubscribe from transaction state change events for an Ethereum transaction hash.
- WriteConfigure Mempool FiltersConfigure filters and ABI decoding for Ethereum mempool transactions. Approval by default
One prompt, start to finish
What a governed Blocknative run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — configure mempool filters — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Blocknative — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Blocknative to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.