Blockchain Data · x402 · early usage

Bitcoin protocol and software changes as JSON: Bitcoin Core merges and releases, BIP up…

Bitcoin protocol and software changes as JSON: Bitcoin Core merges and releases, BIP updates, Lightning spec and implementation changes. Each item has status (proposal, merged, released, activated), layer (consensus, policy, p2p, wallet), why it matters, what…

by btc-radar.vercel.app · discovered, not yet claimed by its owner · updated 2026-10-08

30d calls3

30d payers3

MethodGET

Outputjson

Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.

What it does

Tags: bitcoin · bitcoin-core · bip · protocol · lightning · bazaar

Call contract

Method: GET
Input: query parameters
Output: json
Last paid call: 2026-10-08

Input example from Bazaar metadata

{}

Output example

{
  "digest_date": "2026-10-07",
  "items": [
    {
      "affects": [
        "node operators on low-bandwidth connections",
        "initial block download"
      ],
      "id": "core-36080",
      "layer": "p2p",
      "not_yet": "In master only; not in a release. No consensus or policy change.",
      "project": "bitcoin-core",
      "sources": [
        {
          "date": "2026-10-05",
          "publisher": "GitHub bitcoin/bitcoin",
          "type": "merged pull request",
          "url": "https://github.com/bitcoin/bitcoin/pull/36080"
        }
      ],
      "status": "merged",
      "title": "Peers are no longer disconnected for a missed ping while they are sending us blocks",
      "uncertainty": "none noted",
      "verification": "primary",
      "what_happened": "Bitcoin Core stops enforcing the 20-minute ping timeout against a peer while blocks are being downloaded from that peer.",
      "why_it_matters": "During initial block download on a slow link, a peer busy serving our block requests could miss the ping deadline and be dropped although it was not at fault. This avoids needless disconnects for low-bandwidth nodes."
    }
  ]
}

Use with an agent

Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
Inspect. Fetch /resources/38710.json for the price and payment options.
Pay. Call GET https://btc-radar.vercel.app/bitcoin/technical-updates. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, Base Sepolia, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price: $0.01 / request
Protocol: x402 v2
Auth: No account or API key. Pay per request.
Networks: Base, Base Sepolia
Demand: 3 calls · 3 unique payers in 30d (public x402 Bazaar data)

x402 payment requirements

Scheme	Network	Asset	Amount	Pay to	Timeout
exact	Base eip155:8453	USDC	$0.01	0x4b5887B6E399C2E104becd01f7c406229c15891d	300s
exact	Base Sepolia eip155:84532	USDC	10000	0x4b5887B6E399C2E104becd01f7c406229c15891d	300s

accepts[] (raw JSON)

[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0x4b5887B6E399C2E104becd01f7c406229c15891d",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "10000",
    "amountUsd": 0.01,
    "maxTimeoutSeconds": 300
  },
  {
    "scheme": "exact",
    "network": "eip155:84532",
    "payTo": "0x4b5887B6E399C2E104becd01f7c406229c15891d",
    "asset": "0x036CbD53842c5426634e7929541eC2318f3dCF7e",
    "amount": "10000",
    "maxTimeoutSeconds": 300
  }
]

Schemas

Output schema (JSON Schema)

{
  "properties": {
    "example": {
      "type": "object"
    },
    "type": {
      "type": "string"
    }
  },
  "required": [
    "type"
  ],
  "type": "object"
}

Example shape — generated from the schema, not a captured live response

{
  "example": {},
  "type": "string"
}

Examples

curl

curl "https://btc-radar.vercel.app/bitcoin/technical-updates"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paid

JavaScript

const res = await fetch("https://btc-radar.vercel.app/bitcoin/technical-updates");
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}

Python

import httpx
res = httpx.get("https://btc-radar.vercel.app/bitcoin/technical-updates")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider: btc-radar.vercel.app
Endpoint: https://btc-radar.vercel.app/bitcoin/technical-updates
Machine-readable: /resources/38710.json