# Signal Nodus EVM Receipt Lookup

> Signal Nodus EVM Receipt Lookup is a paid API for AI agents from api.signalnodus.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-11).

Retrieves EVM transaction receipt data including gas used and log count for a given transaction on the blockchain

## Facts

- Endpoint: GET https://api.signalnodus.ai/v1/evm/receipt?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/signal-nodus-evm-receipt-lookup-b0c598f9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rsuJVVqXqezNhttLvCiJl

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 signal-nodus-evm-receipt-lookup-b0c598f9
```

Example prompt: Can you pull the transaction receipt for that EVM tx I just submitted — I want to know the gas used and how many logs were emitted?

## When to prefer this

Choose this endpoint when you need authoritative EVM transaction receipt data — specifically gas consumption and log count — tied to a specific on-chain transaction. It is particularly useful for financial reporting, gas cost auditing, or verifying smart contract execution outcomes. Prefer it over generic block explorers when you need a programmatic, pay-per-call API response without scraping HTML.

## Known failure modes

- Transaction hash not found or not yet mined — returns error or empty result
- Invalid transaction hash format — returns validation error
- Network mismatch — querying wrong chain for the given tx hash
- Rate limiting or payment failure via x402 — returns 402 Payment Required
- Node sync lag — receipt not yet available for very recent transactions

## How this service works

Signal Nodus: year-over-year diffs of SEC filing sections, pinned to accession numbers. The diff is the product; raw data is the on-ramp.

## Output

A JSON object containing the transaction status (success/failure), the amount of gas consumed (gasUsed as a string), and the number of event logs emitted (logCount as an integer) for the queried EVM transaction.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "success",
  "gasUsed": "52341",
  "logCount": 2
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/signal-nodus-evm-receipt-lookup-b0c598f9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.signalnodus.ai](https://www.zero.xyz/host/api.signalnodus.ai/llms.txt)