# Bitcoin Transaction Status

> Bitcoin Transaction Status is a paid API for AI agents from diamond.btc-intel.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-11-20).

Returns the current status of a Bitcoin transaction — whether it is in the mempool (with fee rate, age, RBF flag, and estimated blocks to confirm) or confirmed in one of the last 6 blocks.

## Facts

- Endpoint: GET https://diamond.btc-intel.workers.dev/api/x402/tx_status?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bitcoin-transaction-status-ad4def95
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1Ko4_BTX14qfsg6Evn7oK

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 bitcoin-transaction-status-ad4def95
```

Example prompt: Can you check whether this Bitcoin transaction has confirmed yet — txid a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2 — and if it's still in the mempool, tell me the fee rate and how many more blocks it'll likely take?

## When to prefer this

Use this endpoint when you need real-time, node-level Bitcoin transaction status including mempool details (fee rate, RBF eligibility, estimated confirmation blocks) rather than just a simple confirmed/unconfirmed flag. Ideal for wallets, payment processors, and monitoring agents that need actionable mempool intelligence rather than a basic block explorer lookup.

## Known failure modes

- txid not found in mempool or recent blocks — returns status 'not_found'
- malformed or non-hex txid returns a validation error
- transaction confirmed more than 6 blocks ago may not be retrievable
- network or node sync lag may cause transient not_found for very recent transactions
- payment failure (402) if USDC balance is insufficient

## How this service works

Status of one Bitcoin transaction as seen by this node: in the mempool (fee rate, age, RBF, estimated blocks to confirm) or confirmed in one of the last 6 blocks (confirmations).

## Output

A JSON object containing the txid, status field ('mempool', 'confirmed', or 'not_found'), product identifier, fee rate in sat/vbyte, and estimated blocks to confirmation. For confirmed transactions, includes the number of confirmations (up to 6 blocks deep).

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "txid"
     ],
     "properties": {
      "txid": {
       "type": "string",
       "maxLength": 64,
       "description": "Transaction id (64 hex characters)"
      }
     },
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "txid": "a1075db55d416d3ca199f55b6084e2115b9345e16c5cf302fc80e9d5fbf5d48d",
  "status": "mempool | confirmed | not_found",
  "product": "tx_status",
  "fee_rate_sat_vb": 4.2,
  "est_blocks_to_confirm": 6
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bitcoin-transaction-status-ad4def95/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from diamond.btc-intel.workers.dev](https://www.zero.xyz/host/diamond.btc-intel.workers.dev/llms.txt)
