# DopamineDesk EVM Transaction Lookup

> DopamineDesk EVM Transaction Lookup is a paid API for AI agents from ai-data-marketplace-1042299154756.us-central1.run.app, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-13).

Fetches on-chain transaction details (block, sender, receiver, value) for a given transaction hash on Base, Ethereum, or Arbitrum.

## Facts

- Endpoint: GET https://ai-data-marketplace-1042299154756.us-central1.run.app/api/v1/evm_transaction
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dopaminedesk-evm-transaction-lookup-93c58427
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KsgcSFvK9GxAfQ_XgQWNR

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability dopaminedesk-evm-transaction-lookup-93c58427
```

Example prompt: Can you look up the details of transaction 0x91698c8339b23372096c31fe065bfa0a73988d1b5969447986b3b1b3a7960d06 on Base — I want to know the sender, receiver, block number, and value?

## When to prefer this

Choose this endpoint when you need a pay-per-use, no-subscription lookup of EVM transaction metadata across Base, Ethereum, or Arbitrum. It is well-suited for agents performing due-diligence, audit trails, or payment verification in agentic workflows that settle via x402/USDC, avoiding the need to manage your own blockchain RPC infrastructure.

## Known failure modes

- Invalid or malformed transaction hash returns an error
- Transaction hash not found on specified chain returns failure or empty result
- Unsupported chain identifier causes a bad request
- Network connectivity issues with the RPC node may cause timeouts
- Missing required transaction_hash query parameter returns a validation error

## How this service works

Retrieve a real EVM transaction and normalized block, sender, recipient, nonce, value, gas, fee, type, and input fields by hash.

## Output

A JSON object with a success boolean, the network name (e.g. 'base'), and a transaction object containing the hash, block_number, from address, to address, and value_wei. Additional fields may be present.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "transaction_hash"
     ],
     "properties": {
      "chain": {
       "type": "string",
       "description": "base, ethereum, or arbitrum; defaults to base."
      },
      "transaction_hash": {
       "type": "string",
       "description": "32-byte 0x-prefixed transaction hash."
      }
     },
     "additionalProperties": true
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "required": [
      "success",
      "network",
      "transaction"
     ],
     "properties": {
      "network": {
       "type": "string"
      },
      "success": {
       "type": "boolean"
      },
      "transaction": {
       "type": "object",
       "required": [
        "hash",
        "block_number",
        "from",
        "to",
        "value_wei"
       ],
       "properties": {
        "to": {
         "type": "string"
        },
        "from": {
         "type": "string"
        },
        "hash": {
         "type": "string"
        },
        "value_wei": {
         "type": "string"
        },
        "block_number": {
         "type": "string"
        }
       },
       "additionalProperties": true
      }
     },
     "additionalProperties": true
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "network": "base",
  "success": true,
  "transaction": {
   "to": "0x4200000000000000000000000000000000000015",
   "from": "0xdeaddeaddeaddeaddeaddeaddeaddeaddead0001",
   "hash": "0x91698c8339b23372096c31fe065bfa0a73988d1b5969447986b3b1b3a7960d06",
   "value_wei": "0",
   "block_number": "49533146"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dopaminedesk-evm-transaction-lookup-93c58427/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ai-data-marketplace-1042299154756.us-central1.run.app](https://www.zero.xyz/host/ai-data-marketplace-1042299154756.us-central1.run.app/llms.txt)
