# DESK LEAD x402 - Transaction Status Lookup

> DESK LEAD x402 - Transaction Status Lookup is a paid API for AI agents from desk-x402.desk-x402-gh.workers.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Looks up the confirmation status of a blockchain transaction by hash on BSC or Base networks

## Facts

- Endpoint: GET https://desk-x402.desk-x402-gh.workers.dev/v1/tx-status
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/desk-lead-x402-transaction-status-lookup-9e7d20f8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nQ7a1gSaKlRcMnTxNK9UC

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 desk-lead-x402-transaction-status-lookup-9e7d20f8
```

Example prompt: Can you check whether the Base transaction 0xabc123...def456 has been confirmed yet?

## When to prefer this

Use this endpoint when you need to programmatically verify whether a specific blockchain transaction has been confirmed on the BSC or Base networks, especially in x402 micropayment workflows where proof of payment is required before granting access to a resource. Prefer this over block explorer UIs when you need machine-readable status checks inside an automated agent pipeline.

## Known failure modes

- Invalid or malformed transaction hash returns an error
- Unsupported network value (not 'bsc' or 'base') returns a validation error
- Transaction not yet mined may return status 0 or pending indicator
- Missing required query parameters (tx or network) returns 400
- Payment header missing or invalid USDC payment causes 402 rejection
- Network congestion may cause delayed status resolution

## How this service works

Micropay research APIs (x402 v2 + bazaar). Free catalog at /.well-known/x402.json. Primary v2 accepts: Base eip155:8453 only. Legacy X-PAYMENT-TX still supports bsc|base via acceptsV1. Headers: X-PAYMENT-TX, X-PAYMENT-NETWORK, PAYMENT-SIGNATURE. No financial advice.

## Output

Returns a JSON object with an 'ok' boolean indicating success, a 'status' integer representing the transaction confirmation state, and a 'product' field set to 'tx_status'. Allows the caller to determine whether a given transaction hash has been confirmed on the specified network.

## 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",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "tx",
      "network"
     ],
     "properties": {
      "tx": {
       "type": "string",
       "description": "Transaction hash"
      },
      "network": {
       "enum": [
        "bsc",
        "base"
       ],
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "status": 1,
  "product": "tx_status"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/desk-lead-x402-transaction-status-lookup-9e7d20f8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from desk-x402.desk-x402-gh.workers.dev](https://www.zero.xyz/host/desk-x402.desk-x402-gh.workers.dev/llms.txt)