BitcoinsAPI Bitcoin + x402

Protocol contract

One resource, one exact payment boundary.

The paid handler produces a fee decision draft. No success body is returned until the official x402 v2 adapter confirms settlement.

PausedPayments are paused. No payment proof is processed. The free fee preview is available without a wallet.

Published tuple

Wrong resource, amount, asset, network, recipient, timeout, host, method, or query is rejected.

Route
GET /api/v1/fees/now
Resource
https://bitcoinsapi.com/api/v1/fees/now
Price
0.001 USDC
Amount atomic
1000
Protocol
x402 v2 · exact
Network
Base mainnet · eip155:8453
Asset
0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Recipient
0x8454A49215A78040c69525D57D05fb5d9B21F663
Timeout
60 seconds
MIME
application/json
Facilitator
xpay
Compatibility
2026-09-08T16:05:04.856Z

The decision method

send-wait-v1 · a heuristic for a flexible transfer

The result is wait if either condition holds:

  • The hour rate exceeds the economy rate by at least 2 sat/vB and at least 25% of the hour rate.
  • The mempool contains at least 4,000,000 vbytes and the hour rate is at least 5 sat/vB.

Otherwise the result is send. This does not forecast a fee drop, promise confirmation, or account for your transaction deadline. The savings example compares present rate tiers for 140 vbytes; it is not an observed saving.

Compare costs for your own size · Integrate the API

Response order

  1. Check payment state. When enabled, fetch the private, no-store 402 challenge.
  2. Sign the exact advertised x402 v2 requirement.
  3. The facilitator verifies; the deterministic handler computes.
  4. Settlement confirms before any useful response is released.
  5. The receipt—not the handler—supplies the public transaction hash.