Blocknative MCP integration for AI agents.
Connect AI agents to Blocknative through 4 structured actions, including get gas price distribution, get gas prices, and list gas oracles. Review authenticat…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Blocknative integration exposes
The Blocknative Agent App exposes 4 provider-backed actions for developer tools and data work. Its current contract lets an authorized agent get the current blocknative gas-price distribution for ethereum mainnet, get blocknative gas-price estimates for the default chain or a selected network, and list the gas-oracle metadata exposed by blocknative across supported chains. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Blocknative account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Blocknative capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_gas_price_distributionREADGet the current Blocknative gas-price distribution for Ethereum mainnet.
INPUTS: chainId
get_gas_pricesREADGet Blocknative gas-price estimates for the default chain or a selected network.
INPUTS: chainId / system / network / confidenceLevels
list_gas_oraclesREADList the gas-oracle metadata exposed by Blocknative across supported chains.
list_supported_chainsREADList the chains currently supported by the Blocknative Gas Platform.
INPUT CONTRACTS
Know what the action needs before it runs.
get_gas_price_distribution
chainIdOPTIONAL- The supported chain ID for gas distribution. Only Ethereum mainnet (`1`) works.
get_gas_prices
chainIdOPTIONAL- The chain ID to query. Use `0` for Bitcoin when querying the Gas Price API.
systemOPTIONAL- The chain ecosystem used by Blocknative, for example `ethereum` or `story`.
networkOPTIONAL- The network name used by Blocknative, for example `main` or `mainnet`.
confidenceLevelsOPTIONAL- Up to five confidence levels used to override the default prediction buckets.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Gas Price Distribution
Get the current Blocknative gas-price distribution for Ethereum mainnet. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_gas_price_distributionVerify with Get Gas Prices
Get Blocknative gas-price estimates for the default chain or a selected network. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_gas_pricesSAFETY BOUNDARY
Operate Blocknative with explicit limits
- Authorize Blocknative with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Blocknative data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Blocknative rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Blocknative task completed successfully.
CONNECTION MODEL
API key
Blocknative API key sent with the Authorization header. Request or manage it from the official Blocknative API key page: https://www.blocknative.com/request-api-key
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Blocknative.