# Financial Data x402 – Transaction Status Lookup

> Financial Data x402 – Transaction Status Lookup is a paid API for AI agents from x402financialdata.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).

Looks up the confirmation status and success/failure of an Ethereum transaction by its hash

## Facts

- Endpoint: GET https://x402financialdata.com/transaction-status/%7Btx_hash%7D
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/financial-data-x402-transaction-status-lookup-5629a191
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zkGayIiSDyJ4_Ja3mVMSm

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 financial-data-x402-transaction-status-lookup-5629a191
```

Example prompt: Can you check whether this Ethereum transaction succeeded or failed: 0x4dfa7b1be6578326be24ad2d330e7baf23230e18c2d2c67d8f41798e0e764b0b?

## When to prefer this

Use this endpoint when you need a quick, no-subscription, pay-per-call check on whether a specific Ethereum transaction succeeded or was reverted, especially in agentic workflows that need to verify on-chain settlement before proceeding. Prefer this over building your own Etherscan integration when you want micro-payment access without API key management.

## Known failure modes

- Transaction hash not recognized by Etherscan — succeeded returns null
- Pre-Byzantium transaction (block < 4,370,000) — succeeded returns null because receipt status field did not exist
- Invalid or malformed tx hash — may return an error or null response
- Network or upstream Etherscan API outage causing lookup failure
- Payment failure via x402 protocol if USDC balance is insufficient

## How this service works

Pay-per-call stock, macro, on-chain, and crypto data over the x402 protocol. USDC on Base or Solana, no API keys, no subscriptions.

## Output

Returns a JSON object with the chain name (e.g. 'eth'), the transaction hash, a boolean 'succeeded' field (null for pre-Byzantium blocks before 4,370,000 or unrecognized hashes), an 'error_description' string if applicable, and an 'is_contract_error' boolean indicating whether a failure was at the contract execution level.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "note": "succeeded is null for pre-Byzantium transactions (before block 4,370,000) or a tx hash Etherscan doesn't recognize -- the receipt status field didn't exist yet.",
  "chain": "eth",
  "tx_hash": "0x4dfa7b1be6578326be24ad2d330e7baf23230e18c2d2c67d8f41798e0e764b0b",
  "succeeded": true,
  "error_description": null,
  "is_contract_error": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/financial-data-x402-transaction-status-lookup-5629a191/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402financialdata.com](https://www.zero.xyz/host/x402financialdata.com/llms.txt)