GET /v1/calendar/crypto

$0.01hourlytier: utilitycache 3600sEngine A — Probability API

Upcoming crypto market resolutions in date order with current blended probabilities — the forward calendar of crypto events an agent can position around. Same shape as /v1/calendar, pre-filtered to crypto markets.

Parameters

Example

curl "https://x402-factory.com/v1/calendar/crypto?days=30"

Example response

{
  "data": {
    "events": [
      {
        "slug": "bitcoin-etf-inflows-5b-2026-08",
        "question": "Will spot Bitcoin ETF net inflows exceed $5B in July?",
        "resolution_date": "2026-08-05",
        "current_p": 0.528,
        "category": "crypto"
      }
    ]
  },
  "meta": {
    "endpoint": "/v1/calendar/crypto",
    "version": "1.0.0",
    "generated_at": "2026-08-18T22:54:16.760Z",
    "freshness": "hourly",
    "sources": [
      "kalshi",
      "polymarket"
    ],
    "request_id": "req_00000000",
    "docs": "https://x402-factory.com/docs/probability.calendar.crypto",
    "data_mode": "live"
  }
}

Response schema (data payload)

{
  "type": "object",
  "properties": {
    "events": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "slug": {
            "type": "string"
          },
          "question": {
            "type": "string"
          },
          "resolution_date": {
            "type": "string"
          },
          "current_p": {
            "type": "number",
            "minimum": 0,
            "maximum": 1
          },
          "category": {
            "type": "string"
          }
        },
        "required": [
          "slug",
          "question",
          "resolution_date",
          "current_p",
          "category"
        ],
        "additionalProperties": false
      }
    }
  },
  "required": [
    "events"
  ],
  "additionalProperties": false
}

The platform wraps every payload in an envelope: { "data": …, "meta": { endpoint, version, generated_at, freshness, sources, request_id, docs, data_mode } }.

Payment (x402)

Unpaid requests receive 402 with payment requirements (accepts). Pay $0.01 in USDC on Base per call via an X-PAYMENT header — see docs.x402.org. With PAYMENT_MODE=disabled (local dev) the endpoint is open.

Errors