Monitoring · x402 · early usage

Complete latest daily Keelbase Signal records and full synthesis

Complete latest daily Keelbase Signal records and full synthesis.

by signal.keelbase.io · discovered, not yet claimed by its owner · updated 2026-09-17

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

Complete latest daily Keelbase Signal records and full synthesis.

Tags: bazaar

Call contract

Method: GET
Input: query parameters
Output: json
Last paid call: 2026-09-17

Input example from Bazaar metadata

{}

Output example

{
  "completeness": {
    "bounded": true,
    "complete": true,
    "maximum_record_count": 25,
    "returned_record_count": 3
  },
  "data_status": "publication",
  "publication": {
    "body_markdown": "# Disclosure Without Consensus",
    "report_date": "2026-07-14",
    "title": "Disclosure Without Consensus"
  },
  "records": [
    {
      "factual_reporting": {
        "summary": "Original source-grounded factual summary."
      },
      "keelbase_analysis": {
        "relevance": "Operational relevance to Keelbase."
      },
      "record_id": "KB-SIGNAL-20260714-001",
      "source": {
        "status": "proposal"
      }
    },
    {
      "factual_reporting": {
        "summary": "Original source-grounded factual summary."
      },
      "keelbase_analysis": {
        "relevance": "Operational relevance to Keelbase."
      },
      "record_id": "KB-SIGNAL-20260714-002",
      "source": {
        "status": "unresolved"
      }
    },
    {
      "factual_reporting": {
        "summary": "Original source-grounded factual summary."
      },
      "keelbase_analysis": {
        "relevance": "Operational relevance to Keelbase."
      },
      "record_id": "KB-SIGNAL-20260714-003",
      "source": {
        "status": "confirmed"
      }
    }
  ],
  "warnings": [
    "Current publication status is explicitly identified in the response."
  ]
}

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/53639.json for the price and payment options.
Pay. Call GET https://signal.keelbase.io/api/v1/daily/latest. 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.03 / 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.03	0x7B177B724d6B02f69D9f25d9b91c63338c554DBF	60s

accepts[] (raw JSON)

[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0x7B177B724d6B02f69D9f25d9b91c63338c554DBF",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "30000",
    "amountUsd": 0.03,
    "maxTimeoutSeconds": 60
  }
]

Schemas

Output schema (JSON Schema)

{
  "properties": {
    "example": {
      "additionalProperties": true,
      "properties": {
        "completeness": {
          "additionalProperties": true,
          "description": "Bounded-response and record-count metadata.",
          "type": "object"
        },
        "data_status": {
          "description": "Whether the returned publication is fixture or production data.",
          "type": "string"
        },
        "publication": {
          "additionalProperties": true,
          "description": "The complete latest daily publication and Markdown synthesis.",
          "type": "object"
        },
        "records": {
          "items": {
            "additionalProperties": true,
            "description": "A normalized public Keelbase Signal event record with factual reporting, Keelbase analysis, assessment, source attribution, and correction lineage.",
            "type": "object"
          },
          "type": "array"
        },
        "warnings": {
          "items": {
            "type": "string"
          },
          "type": "array"
        }
      },
      "required": [
        "data_status",
        "publication",
        "completeness",
        "records",
        "warnings"
      ],
      "type": "object"
    },
    "type": {
      "type": "string"
    }
  },
  "required": [
    "type"
  ],
  "type": "object"
}

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

{
  "example": {
    "completeness": {},
    "data_status": "string",
    "publication": {},
    "records": [
      {}
    ],
    "warnings": [
      "string"
    ]
  },
  "type": "string"
}

Examples

curl

curl -X GET 'https://signal.keelbase.io/api/v1/daily/latest'
# -> 402 Payment Required; read PAYMENT-REQUIRED
# retry the identical request with PAYMENT-SIGNATURE

JavaScript

const res = await fetch("https://signal.keelbase.io/api/v1/daily/latest", {
  "method": "GET"
});
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.request("GET", "https://signal.keelbase.io/api/v1/daily/latest")
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: signal.keelbase.io
Endpoint: https://signal.keelbase.io/api/v1/daily/latest
Machine-readable: /resources/53639.json