# TraceFast Transaction Event Logs

> TraceFast Transaction Event Logs is a paid API for AI agents from mpp.tracefast.xyz, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-12).

Retrieves the ordered list of event logs emitted by an Ethereum transaction, with emitting contract, topics, raw data, and decoded event name/arguments when the signature is recognized

## Facts

- Endpoint: GET https://mpp.tracefast.xyz/api/v1/chains/1/transactions/:hash/events?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tracefast-transaction-event-logs-91081481
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_C_Us3L00mc5HTFW8zrZS5

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 tracefast-transaction-event-logs-91081481
```

Example prompt: Can you pull all the event logs emitted by Ethereum transaction 0x5c504ed432cb51138bcf09aa5e8a410dd4a1e204d9e9f892f3f7b2f6b9a1c0a1 — I want to see each contract that fired an event, the topics, and any decoded event names with their arguments?

## When to prefer this

Choose this endpoint when you need the complete ordered event log sequence for a specific Ethereum transaction, especially when you want both raw log data and human-readable decoded event names and arguments. It is the right choice for debugging smart contract interactions, auditing DeFi swaps, verifying NFT transfers, or any workflow that requires inspecting exactly what happened inside a transaction at the event level. Prefer it over generic block explorers when you need structured, machine-readable decoded output with confidence scores suitable for programmatic processing.

## Known failure modes

- Transaction hash not found or invalid format returns an error
- Transaction exists but emitted no events returns an empty array
- Unrecognized event signatures return raw topics/data without decoded fields
- Pagination cursor mismatch or expiry causes an error
- Rate limiting or payment failure (x402) blocks the request
- Network or RPC issues may cause transient failures

## How this service works

TraceFast live Ethereum data: the event logs a transaction emitted, in emission order, each with the emitting contract, topics and data, and — when the event signature is known — the decoded event name and arguments with a stated confidence. Path hash: Transaction hash, `0x`-prefixed, 64 hex characters, any case. Query limit: 1..=100, default 25; cursor: `nextCursor` of the previous page. Docs: https://docs.tracefast.xyz/api/transaction-events.md

## Output

An ordered array of event log entries, each containing the emitting contract address, array of topics (hex-encoded), raw data field, log index, and — where the event signature is recognized — the decoded event name and typed arguments along with a stated confidence score. The response also includes a nextCursor token for paginating through additional logs beyond the requested limit.

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "required": [
    "method"
   ],
   "properties": {
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tracefast-transaction-event-logs-91081481/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mpp.tracefast.xyz](https://www.zero.xyz/host/mpp.tracefast.xyz/llms.txt)