# Bitcoin Batch Fee Planner

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

Returns fee estimates for 1–25 Bitcoin transaction sizes against a single per-transaction sats budget, flagging the fastest confirmable option within that cap.

## Facts

- Endpoint: GET https://diamond.btc-intel.workers.dev/api/x402/feeplan?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bitcoin-batch-fee-planner-cca720dd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CXQRQK5kWNonlC4wRjnfj

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-batch-fee-planner-cca720dd
```

Example prompt: Can you check if a 1000 sat fee budget is enough for Bitcoin transactions of 140, 220, and 350 vbytes, and tell me which size gets the fastest confirmation within that budget?

## When to prefer this

Use this endpoint when you need to evaluate Bitcoin transaction fee feasibility across multiple transaction sizes in a single call, particularly when working with a fixed sat budget and wanting to know the fastest confirmable option within that constraint. Prefer it over single-transaction fee estimators when batching payment planning or comparing output sizes. It is not a broadcast or signing service — purely advisory.

## Known failure modes

- plan parameter missing or malformed — returns error if format deviates from budget_sats:vbytes
- fee cap out of range (must be 1–100,000,000 sats) — validation error
- vbyte value out of range (must be 60–100,000 per size) — validation error
- more than 25 transaction sizes submitted — rejected
- network or node connectivity issues may return stale or unavailable data
- fastest_estimate_within_budget returns null when no estimate fits within the cap

## How this service works

Batch fee-budget analysis for one to 25 transaction sizes. plan=budget_sats:vbytes[,vbytes...]. The budget is a per-transaction cap in sats. Returns rounded-up fee estimates and the fastest observed estimate fitting each cap. Uses fresh independent-node observations; no confirmation guarantee.

## Output

A JSON object containing a UTC timestamp, the observing node name, one plan entry per submitted vbyte size (each showing the fee cap, available options, and the label of the fastest estimate fitting within budget or null if none fit), plus a disclaimer about network conditions and confirmation times.

## 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": [
      "plan"
     ],
     "properties": {
      "plan": {
       "type": "string",
       "maxLength": 185,
       "description": "Per-transaction fee cap in sats, colon, and one to 25 comma-separated transaction sizes in vbytes. Example 1000:140,220,350. Fee cap 1..100000000; each size 60..100000."
      }
     },
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "as_of": "<UTC timestamp>",
  "plans": [
   {
    "vbytes": 140,
    "options": [],
    "fee_cap_sats": 1000,
    "fastest_estimate_within_budget": "<estimate label or null>"
   }
  ],
  "terms": "Independent-node estimates, not guaranteed confirmation times. The budget is a per-transaction fee cap in sats, and each vsize entry is evaluated against that cap. Transaction sizes are supplied by the buyer. Node relay policies and network conditions can change. No transaction is signed or sent.",
  "product": "fee_plan_batch",
  "plan_count": 3,
  "observing_node": "Diamond"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bitcoin-batch-fee-planner-cca720dd/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)
