Monitoring · x402 · early usage

Bitcoin and digital-asset adoption scores for the world's 100 largest banks, as CSV

by gibai.app · discovered, not yet claimed by its owner · updated 2026-09-24

30d calls1

30d payers1

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

Bitcoin and digital-asset adoption scores for the world's 100 largest banks, as CSV. Answers: does a bank offer Bitcoin custody or trading, how has its position changed, which banks lead. One row per scoring change since the index began, each with the bank, the activity (custody, trading, stablecoins, tokenization and 12 more), old and new values, a reason, a source URL, the event date, and the resulting score and rank out of 100. Includes the scoring schema. Free /latest shows coverage.

Tags: bitcoin · banking · custody · institutional · stablecoin · bazaar

Call contract

Method: GET
Input: HTTP request
Output: json
Last paid call: 2026-09-24

No input exampleProvider did not publish one in Bazaar metadata.

Output example

{
  "history_csv": "change_date,ts,bank,country,sub_dimension,old_score,new_score,origin,reason,source_url,published_total,published_rank,event_date\n2026-09-03,2026-09-03T07:34:58Z,Citigroup,United States,btc_custody,75,50,auto,Citi announced Bitcoin custody under Custody+ launching later in 2026; not yet live.,https://coinpaprika.com/news/citi-brings-bitcoin-into-bank-grade-custody/,31.8,15,2026-08-18\n",
  "report_date": "2026-09-03",
  "rows": 1547,
  "schema_json": {
    "score_ladder": {
      "0": "No Bitcoin adoption",
      "25": "Announced, piloted, or offered only through a third party",
      "50": "Launched, but limited in scope or availability",
      "75": "Live at scale",
      "100": "Market-leading"
    }
  }
}

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/37883.json for the price and payment options.
Pay. Call GET https://gibai.app/history. 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, 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.1 / request
Protocol: x402 v2
Auth: No account or API key. Pay per request.
Networks: Base
Demand: 1 calls · 1 unique payers in 30d (public x402 Bazaar data)

x402 payment requirements

Scheme	Network	Asset	Amount	Pay to	Timeout
exact	Base eip155:8453	USDC	$0.1	0xEa09587Ed59DC18EC3A307E35E96b315d3a9614f	60s

accepts[] (raw JSON)

[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0xEa09587Ed59DC18EC3A307E35E96b315d3a9614f",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "100000",
    "amountUsd": 0.1,
    "maxTimeoutSeconds": 60
  }
]

Schemas

Output schema (JSON Schema)

{
  "properties": {
    "example": {
      "properties": {
        "history_csv": {
          "description": "The full change log as CSV text. Columns: change_date, ts, bank, country, sub_dimension, old_score, new_score, origin, reason, source_url, published_total, published_rank, event_date",
          "type": "string"
        },
        "report_date": {
          "description": "Date of the most recent report, YYYY-MM-DD",
          "type": "string"
        },
        "rows": {
          "description": "Number of change rows in the CSV",
          "type": "integer"
        },
        "schema_json": {
          "description": "Score ladder, sub-dimension definitions, category weights, coverage counts",
          "type": "object"
        }
      },
      "required": [
        "report_date",
        "rows",
        "history_csv",
        "schema_json"
      ],
      "type": "object"
    },
    "type": {
      "type": "string"
    }
  },
  "required": [
    "type"
  ],
  "type": "object"
}

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

{
  "example": {
    "history_csv": "string",
    "report_date": "string",
    "rows": 0,
    "schema_json": {}
  },
  "type": "string"
}

Examples

curl

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

JavaScript

const res = await fetch("https://gibai.app/history");
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://gibai.app/history")
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: gibai.app
Endpoint: https://gibai.app/history
Machine-readable: /resources/37883.json