# EVM Internal Transactions Lookup

> EVM Internal Transactions Lookup is a paid API for AI agents from api.vextorium.com, paid per call via x402, $0.006/call, status unknown (last checked 2026-10-29).

Retrieves internal transactions (native coin transfers triggered by smart contracts, not visible in normal tx history) for an EVM address, including date, type, sender, recipient, value, success status, and parent transaction hash.

## Facts

- Endpoint: POST https://api.vextorium.com/evm-internas-pago?utm_source=zero.xyz
- Price: $0.006/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-internal-transactions-lookup-64848ef2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6X5ZHVqLu1n9WPeAW5dDF

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 evm-internal-transactions-lookup-64848ef2 -d '<json body>'
```

Example prompt: Can you fetch the internal transactions for Ethereum address 0xAbCd...1234 on the Arbitrum network — I need to see all the contract-triggered native coin transfers that don't show up in the normal transaction history?

## When to prefer this

Use this endpoint when you need to surface native coin transfers that are invisible in the standard transaction history because they were triggered by smart contract execution (internal calls). It is essential for DeFi portfolio reconciliation, smart contract auditing, and debugging unexplained balance changes across Ethereum, Base, Arbitrum, Optimism, Polygon, and zkSync.

## Known failure modes

- Invalid or malformed EVM address returns an error
- Unsupported network name causes validation failure
- No internal transactions found returns an empty list
- Rate limiting or payment failure if x402 payment not completed
- Node provider downtime may cause temporary unavailability

## How this service works

Internal transactions of an EVM address (native coin moved by contracts, invisible in the normal history): date, type, from, to, value, success and parent transaction.

## Output

Returns a list of internal transactions for the queried address, each containing: transaction date, type, from/to address objects (with ENS name, contract flag, and scam flag if available), native value transferred, success/failure status, parent transaction hash, and whether more results exist. Also returns the queried address, network name, and data source.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "red": {
   "enum": [
    "ethereum",
    "base",
    "arbitrum",
    "optimism",
    "polygon",
    "zksync"
   ],
   "type": "string"
  },
  "limite": {
   "type": "integer"
  },
  "direccion": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-internal-transactions-lookup-64848ef2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.vextorium.com](https://www.zero.xyz/host/api.vextorium.com/llms.txt)