# chain-transaction

> chain-transaction is a paid API for AI agents from chain.intel.rallylive.ca, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-02).

Retrieves raw transaction details by hash (from, to, value, nonce, block, gas, type, method selector, pending flag) across Base, Ethereum, Arbitrum, Optimism, Polygon, and BSC.

## Facts

- Endpoint: GET https://chain.intel.rallylive.ca/chain/tx?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/chain-transaction-e0b92be3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0_prg3ljc22bPv5gPfoe8

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 chain-transaction-e0b92be3
```

Example prompt: Can you look up the transaction 0x4f3c...ab12 on Ethereum and tell me who sent it, who received it, how much was transferred, whether it's confirmed, and what method was called?

## When to prefer this

Choose this endpoint when you need raw, low-level transaction fields (from, to, value, nonce, gas, method selector, pending status) for a specific tx hash across Base, Ethereum, Arbitrum, Optimism, Polygon, or BSC. It is ideal for payment verification, transaction auditing, debugging contract calls, and checking mempool status. Prefer it over block-level endpoints when you have a specific tx hash rather than a block number, and over wallet portfolio endpoints when you need per-transaction detail rather than aggregate balances.

## Known failure modes

- Transaction hash not found on the specified chain — returns 404 or empty result
- Invalid or malformed transaction hash format — returns validation error
- Unsupported chain prefix — returns error indicating unknown network
- Network or RPC node timeout — returns 5xx or timeout error
- Payment not processed (x402 protocol failure) — request blocked before execution

## How this service works

Raw transaction by hash: from, to, value, nonce, block, gas, type, method selector, pending flag. Default chain Base; prefix another: ethereum:, arbitrum:, optimism:, polygon:, bsc:. $0.01 per call.

## Output

Returns a JSON object containing the raw transaction fields: sender address (from), recipient address (to), value transferred, nonce, block number, gas limit and gas used, transaction type, the 4-byte method selector (for contract calls), and a boolean pending flag indicating whether the transaction is still unconfirmed in the mempool.

## 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",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/chain-transaction-e0b92be3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chain.intel.rallylive.ca](https://www.zero.xyz/host/chain.intel.rallylive.ca/llms.txt)