# OpenRelay Tx Status

> OpenRelay Tx Status is a paid API for AI agents from openrelay.hggfffdfy687.workers.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Check the confirmation status of a transaction on Base or Solana, returning confirmation state, block/slot, gas used, and any errors.

## Facts

- Endpoint: POST https://openrelay.hggfffdfy687.workers.dev/tools/tx/status
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/openrelay-tx-status-bd6d44b8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zyNyTYB84s5xE6qsyD8ch

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 openrelay-tx-status-bd6d44b8 -d '<json body>'
```

Example prompt: Can you check if my Base transaction 0x4a3b...c91d has been confirmed yet — I need to know the status, which block it landed in, and whether it errored out.

## When to prefer this

Use this endpoint when an AI agent needs to programmatically verify whether a specific Base or Solana transaction has been confirmed, retrieve its block/slot number, or diagnose a transaction failure — especially in payment verification workflows or post-swap confirmation checks where a quick, cheap per-call lookup is needed.

## Known failure modes

- Invalid or malformed transaction hash returns an error
- Unsupported chain value (not 'base' or 'solana') rejected by enum validation
- Transaction not yet indexed returns pending or not-found status
- Network or RPC timeout causes delayed or failed lookup
- Payment failure (insufficient USDC balance) blocks the request

## How this service works

Check transaction status on Base or Solana. Returns confirmed, status, block/slot, gas, err.

## Output

Returns a JSON object containing: confirmation status (e.g. confirmed/pending/failed), block number or slot, gas used, and any error details associated with the transaction.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "enum": [
    "base",
    "solana"
   ],
   "type": "string"
  },
  "tx_hash": {
   "type": "string",
   "description": "Transaction hash / signature"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/openrelay-tx-status-bd6d44b8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from openrelay.hggfffdfy687.workers.dev](https://www.zero.xyz/host/openrelay.hggfffdfy687.workers.dev/llms.txt)
