# Bitcoin UTXO Snapshot

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

Returns current status (value, script, confirmations, coinbase flag) for up to 25 Bitcoin UTXOs by txid:vout outpoints, based on this node's chainstate and mempool observations.

## Facts

- Endpoint: GET https://diamond.btc-intel.workers.dev/api/x402/utxos?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bitcoin-utxo-snapshot-2fd2c641
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zupEVfW6Fm5jNiloi4D3M

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-utxo-snapshot-2fd2c641
```

Example prompt: Can you check the current status of these Bitcoin outputs for me — their values, confirmation counts, and whether they're coinbase outputs: a3f1b2c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2:0 and 9b8a7f6e5d4c3b2a1f0e9d8c7b6a5f4e3d2c1b0a9f8e7d6c5b4a3f2e1d0c9b8:1?

## When to prefer this

Use this endpoint when you need fast, cheap batch UTXO status lookups across up to 25 Bitcoin outpoints in a single call, and you need value, script, confirmations, and coinbase status together. Prefer this over single-outpoint lookups when checking multiple UTXOs to minimize API calls and cost. Note that this provides a node observation snapshot — not a cryptographic proof of unspentness — so it is best for informational checks, pre-signing audits, and wallet reconciliation rather than security-critical unspentness proofs.

## Known failure modes

- Invalid txid format (non-hex or wrong length) results in an error
- vout index out of range (>65535) causes rejection
- More than 25 outpoints submitted exceeds the batch limit
- Outpoint present in neither chainstate nor mempool returns absent/missing entry — does not prove it is spent
- Mempool state may change between sequential queries in a batch, causing inconsistency
- Payment not completed or insufficient funds results in HTTP 402 response

## How this service works

Batch output status for one to 25 unique Bitcoin outpoints (txid:vout pairs). Reports this node's chainstate and sequential mempool observations, value, script, confirmations and coinbase flag. Missing does not prove spent. No cryptographic unspentness proof or spendability guarantee; all-absent bat

## Output

A JSON object containing: a UTC timestamp of the snapshot (as_of), a terms disclaimer, the product identifier (utxo_batch_snapshot), a flag indicating mempool queries are not atomic, and an outputs array with per-outpoint details including value in satoshis, locking script, confirmation count, and coinbase flag. Missing outpoints are not returned and their absence does not confirm they are spent.

## 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": [
      "outpoints"
     ],
     "properties": {
      "outpoints": {
       "type": "string",
       "maxLength": 1774,
       "description": "One to 25 unique comma-separated txid:vout pairs. txid is 64 hex characters; vout 0..65535. URLs disclose these public outpoints to Diamond."
      }
     },
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "as_of": "<UTC timestamp>",
  "terms": "One node's observations, not a cryptographic proof of unspentness or a guarantee of spendability. Chainstate and mempool queries are sequential; the mempool can change during a batch. A missing output may be spent, nonexistent, or absent from this node's view. Coinbase, script locks, ownership and other spending conditions need separate checks. Public outpoints supplied in the URL are disclosed to Diamond. Paid replay preserves this snapshot, not current status.",
  "outputs": [],
  "product": "utxo_batch_snapshot",
  "mempool_queries_atomic": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bitcoin-utxo-snapshot-2fd2c641/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)
