POST

/v1/evm/raw/internal-transactions

POST /v1/evm/raw/internal-transactions is an endpoint of the BlockDB EVM Internal Transactions API, listed on Proxygate by Blockchain Database LTD. Full call-trace decomposition of every EVM transaction via debug_traceTransaction. One row per internal call, with the complete call tree position, call type, value transferred, gas used, and input/output data — providing complete internal execution visibility beyond top-level transactions. AI agents call it per request through a transparent proxy and pay $0.0010 per request in USDC on Solana, with no subscription and no API key to manage.

Price

$0.0010 / request

Method

POST

Settlement

USDC on Solana

Parameters

ParameterTypeRequiredDescription
limitintegerNo-
cursorstringNo-
chain_idintegerYes-
to_blockintegerNo-
tx_hashesarrayNo-
call_typesarrayNo-
from_blockintegerNo-
to_addressstringNo-
tx_successbooleanNo-
from_addressstringNo-
to_timestampstringNo-
block_numbersarrayNo-
from_timestampstringNo-

Call /v1/evm/raw/internal-transactions with an AI agent

Proxygate CLI
# Call this endpoint with the Proxygate CLI
proxygate proxy blockdb-evm-internal-transactions /v1/evm/raw/internal-transactions -X POST
MCP / agent
// Call it from an AI agent over the Proxygate MCP server
call_api({
  listing_id: "ffe8dc76-e35d-487a-9063-619babc38ce7",
  method: "POST",
  path: "/v1/evm/raw/internal-transactions"
})

BlockDB EVM Internal Transactions /v1/evm/raw/internal-transactions: frequently asked questions

Full call-trace decomposition of every EVM transaction via debug_traceTransaction. One row per internal call, with the complete call tree position, call type, value transferred, gas used, and input/output data — providing complete internal execution visibility beyond top-level transactions.

It costs $0.0010 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/internal-transactions 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.