/v1/evm/raw/logs
POST /v1/evm/raw/logs is an endpoint of the BlockDB EVM Logs API, listed on Proxygate by Blockchain Database LTD. Complete event log records for every log emitted by smart contracts across EVM chains. One row per log entry, with raw topic and data payloads directly verified by RLP, and deterministic row-level tracing back to the originating block. 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 | - |
| tx_hashes | array | No | - |
| from_block | integer | No | - |
| topic_zeros | array | No | - |
| to_timestamp | string | No | - |
| block_numbers | array | No | - |
| from_timestamp | string | No | - |
| contract_addresses | array | No | - |
Call /v1/evm/raw/logs with an AI agent
# Call this endpoint with the Proxygate CLI
proxygate proxy blockdb-evm-logs /v1/evm/raw/logs -X POST// Call it from an AI agent over the Proxygate MCP server
call_api({
listing_id: "a6eef09c-6a60-4667-af03-e6d27763311a",
method: "POST",
path: "/v1/evm/raw/logs"
})BlockDB EVM Logs /v1/evm/raw/logs: frequently asked questions
Complete event log records for every log emitted by smart contracts across EVM chains. One row per log entry, with raw topic and data payloads directly verified by RLP, and deterministic row-level tracing back to the originating block.
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/logs 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.