EVM Block by Height or Hash
Retrieve a live EVM block header and a bounded list of real transaction hashes by height, tag, or block hash.
Preview request
The preview path is rate-limited and does not charge. Production requests use the same parameters and return a standard x402 challenge when no payment signature is present.
curl --request GET \ "https://ai-data-marketplace-1042299154756.us-central1.run.app/api/v1/evm_block?preview=true&chain=base&block=latest&transaction_limit=250"
Input contract
| Parameter | Type | Required | Description |
|---|---|---|---|
chain | string | No | base, ethereum, or arbitrum; defaults to base. |
block | string | No | Block tag, decimal height, or canonical hex quantity. Defaults to latest. |
block_hash | string | No | Optional 32-byte block hash. Takes precedence over block. |
transaction_limit | integer | No | Maximum transaction hashes returned, from 0 to 500; defaults to 250. |
Example deliverable
This is the documented response shape, not a promise that live values will match the example. The paid request returns current or declared-source results using the same contract.
{
"success": true,
"network": "base",
"block": {
"number": "33752215",
"hash": "0x...",
"transaction_count": 184,
"transactions_truncated": false
}
}Purchase decision
Buy when: the active task needs this product's structured result, its declared source and freshness are sufficient, and 0.002 USDC is within the buyer's authorized per-request limit.
Skip when: a cached result is sufficient, the source or fields do not satisfy the task, or the buyer has not authorized payment. Do not bypass wallet, budget, or user-approval policy.
Guaranteed response metadata
Every successful product response identifies how the result was produced. Product-specific output fields are documented in the paid OpenAPI contract and can be inspected through the preview request where available.
{
"marketplace_metadata": {
"data_mode": "live_source",
"billable": true,
"availability": "operational",
"source": "public EVM JSON-RPC"
}
}Agent payment flow
Fast path: install the public MCP package, configure a dedicated low-balance Base buyer wallet and a maximum per-request spend, then call this tool with auto_pay: true. The client handles the challenge, local signature, settlement, and retry in one tool call.
npx -y dopaminedesk-ai-data-marketplace-mcp
X402_AUTO_PAY=true
X402_EVM_PRIVATE_KEY=<dedicated buyer wallet key>
X402_MAX_PAYMENT_USDC=0.25
tool input: { "auto_pay": true }Manual path: request the product, read the base64 PAYMENT-REQUIRED challenge, sign with any compatible x402 v2 client, and retry with PAYMENT-SIGNATURE. A successful response includes PAYMENT-RESPONSE.