# Bitcoin Transaction Status

> Bitcoin Transaction Status is a paid API for AI agents from bess-x402.onrender.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-30).

Looks up the status of a Bitcoin transaction by txid, returning confirmation count, block info, fee, fee rate, RBF flag, and inputs/outputs.

## Facts

- Endpoint: GET https://bess-x402.onrender.com/v1/crypto/btc-tx?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bitcoin-transaction-status-6adb1a6a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bKP7APJccsMstytQvYm2K

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-6adb1a6a
```

Example prompt: Can you check whether my Bitcoin transaction is confirmed yet? The txid is 4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b — also tell me how many confirmations it has and what the fee rate was.

## When to prefer this

Use this endpoint when you need authoritative Bitcoin transaction details — confirmation status, fee analysis, or RBF eligibility — for a specific txid. Prefer this over generic block explorers when you need structured JSON data suitable for agent decision-making (e.g. auto fee-bumping logic or payment verification workflows). For EVM chains, use the sibling EVM Transaction Status endpoint instead.

## Known failure modes

- Invalid or malformed txid (not 64 hex characters) returns a validation error
- Transaction not found on the Bitcoin network returns a not-found error
- Network or node connectivity issues may result in timeout or service unavailable
- Very recently broadcast transactions may not yet be visible if mempool propagation is incomplete

## How this service works

Status of a Bitcoin transaction: confirmed or pending, confirmations, block, time, fee and fee rate, RBF flag, inputs and outputs. Use to confirm a BTC payment or decide whether to bump a fee.

## Output

Returns whether the transaction is confirmed or pending, the number of confirmations, the block it was included in, the timestamp, the total fee in satoshis, the fee rate (sat/vbyte), whether RBF (replace-by-fee) is flagged, and a breakdown of inputs and outputs.

## 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": [
      "txid"
     ],
     "properties": {
      "txid": {
       "type": "string",
       "description": "Transaction id (64 hex)"
      }
     }
    }
   },
   "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/bitcoin-transaction-status-6adb1a6a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bess-x402.onrender.com](https://www.zero.xyz/host/bess-x402.onrender.com/llms.txt)
