/v1/evm/raw/blocks
POST /v1/evm/raw/blocks is an endpoint of the BlockDB EVM Block Headers API, listed on Proxygate by Blockchain Database LTD. Returns canonical EVM block headers. Provide exactly one of: a block range (`from_block`/`to_block`), a timestamp range (`from_timestamp`/`to_timestamp`), `block_numbers`, or `block_hashes`. `block_numbers` and `block_hashes` are mutually exclusive. AI agents call it per request through a transparent proxy and pay $0.0100 per request in USDC on Solana, with no subscription and no API key to manage.
$0.0100 / request
POST
USDC on Solana
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| limit | integer | No | - |
| cursor | string | No | - |
| chain_id | integer | Yes | - |
| to_block | integer | No | - |
| from_block | integer | No | - |
| block_hashes | array | No | - |
| to_timestamp | string | No | - |
| block_numbers | array | No | - |
| from_timestamp | string | No | - |
Call /v1/evm/raw/blocks with an AI agent
# Call this endpoint with the Proxygate CLI
proxygate proxy blockdb-evm-block-headers /v1/evm/raw/blocks -X POST// Call it from an AI agent over the Proxygate MCP server
call_api({
listing_id: "4793e88a-23d0-4831-808e-60adca52b318",
method: "POST",
path: "/v1/evm/raw/blocks"
})BlockDB EVM Block Headers /v1/evm/raw/blocks: frequently asked questions
Returns canonical EVM block headers. Provide exactly one of: a block range (`from_block`/`to_block`), a timestamp range (`from_timestamp`/`to_timestamp`), `block_numbers`, or `block_hashes`. `block_numbers` and `block_hashes` are mutually exclusive.
It costs $0.0100 per request, settled in USDC on Solana. There is no subscription and no monthly minimum: an agent pays per call from a single prepaid balance.
The agent calls POST /v1/evm/raw/blocks through the Proxygate gateway with the Proxygate CLI, SDK, or MCP server. Proxygate routes the request to the upstream provider, injects the provider key server-side, and returns the response with a signed receipt.
No. The upstream provider key never leaves the Proxygate gateway. Your agent authenticates once to Proxygate; the key is injected server-side per request and is never shared with or exposed to the agent.