# Vextorium EVM Transaction History

> Vextorium EVM Transaction History is a paid API for AI agents from api.vextorium.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-16).

Returns the full transaction history of an EVM address across Ethereum, Base, Arbitrum, Optimism, Polygon, and zkSync, including method called, parties, value, fees, status, and revert reasons.

## Facts

- Endpoint: POST https://api.vextorium.com/evm-historial-pago?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vextorium-evm-transaction-history-7ec7ead6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9pWTAeBxUV8QOp5lFDCpk

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 vextorium-evm-transaction-history-7ec7ead6 -d '<json body>'
```

Example prompt: Pull up the full transaction history for wallet 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on Ethereum — I want to see dates, methods called, who sent and received, values, fees, statuses, and any revert reasons, plus total fees paid.

## When to prefer this

Choose this endpoint when you need structured, multi-chain EVM transaction history with named counterparties (ENS, labeled contracts), method-level detail, revert reasons, and aggregated fee totals — especially for wallets on Base, Arbitrum, Optimism, Polygon, or zkSync where many indexers lack coverage. Prefer this over raw blockchain RPC calls when you need human-readable labels and fee summaries without additional parsing.

## Known failure modes

- Invalid or malformed EVM address returns an error
- Unsupported network enum value causes a validation error
- Address with no transactions returns an empty transaction array
- Network congestion or data source downtime may cause timeouts
- Exceeding the limit parameter may be capped silently or return an error

## How this service works

Transaction history of an EVM address (Ethereum, Base, Arbitrum, Optimism, Polygon, zkSync): date, method called, from, to (named when known), value, fee, status and revert reason, plus total fees paid.

## Output

Returns a structured object containing the queried address, the network, the data source, a flag indicating if more results exist, total native fees paid, and an array of transactions each with: hash, date, transaction type tags, from address (with ENS/name/contract flags), to address (with ENS/name/contract flags), native value transferred, native fee paid, status (success/fail), and revert reason if applicable.

## 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/vextorium-evm-transaction-history-7ec7ead6/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)