> ## Documentation Index > Fetch the complete documentation index at: https://docs.kairos.trade/llms.txt > Use this file to discover all available pages before exploring further. # Top live/upcoming sports markets matched across Polymarket and Kalshi > Finds games that have BOTH a Polymarket and a Kalshi entry in the cross-venue sports match cache, drops any entry whose embedded date is older than yesterday (UTC), enriches each surviving Kalshi side with a live volume figure (`volume_1h` falling back to `volume_total`), sorts descending by that volume, and truncates to `limit`. Title and `tokenId` come from the cached match record itself, not from a live provider call. Responses are cacheable at the edge. ## OpenAPI ````yaml /openapi/data-api.yaml get /sports/trending-matched openapi: 3.1.0 info: title: Kairos Data API version: 1.0.0 summary: >- The full Kairos data plane — markets, candles, trades, search, discover, sports, trader analytics, and PnL. description: | The Kairos Data API at `data.kairos.trade` is the platform's primary data plane: market metadata and prices, OHLCV candles, live venue trade proxies, normalized trade history, full-text search, discovery feeds, the sports catalog, public trader analytics, and account PnL. ## Authentication Most endpoints accept a Kairos **API key** (`X-Client-Id` + `X-Api-Key` + `X-Api-Secret`, all three) or a first-party session JWT. Endpoints tagged `public` (trader analytics, provider configs, several sports feeds) need no credentials at all. Some endpoints additionally require an API-key **scope** (`trade:read`, `position:read`) — stated per operation. For high-volume market-data consumption (candles/trades/metadata at scale), prefer the dedicated **Market Data API** at `md.kairos.trade` — it has higher budgets, ETag caching, and a binary candle format. ## Rate limits Rate limits use a sliding window keyed on the authenticated user (JWT `sub`) or, for anonymous callers, the trusted client IP. Routes belong to a named **bucket** (`x-kairos-bucket`) whose per-minute budget is shared by every route in it; routes with no bucket run under the service default of 100/minute. `x-kairos-rate-limit` states the bucket's compile-time default — operators can raise or lower a bucket at runtime, so treat the documented number as the baseline, not a contract. 429 responses carry `Retry-After` and `X-RateLimit-*`. ## Conventions - Prices are on the **0–100 cents scale** unless a field says otherwise (trader-analytics position/trade prices use the 0–1 scale; each field's description states its scale). - Errors: `{"detail": ""}` for handler errors; FastAPI's standard validation envelope for 422s. Errors surfaced from a venue adapter instead use `{"error", "provider", "operation", "message"}` — see `DataProviderError`. Unhandled failures always return the generic 500 body; internal details are logged, never returned. - Every request body is capped at 8 MiB service-wide (413). contact: name: Kairos url: https://app.kairos.trade/docs/api-reference termsOfService: https://kairos.trade/terms servers: - url: https://data.kairos.trade description: Production - url: https://staging-data.kairos.trade description: Staging security: - apiKeyClientId: [] apiKeyKey: [] apiKeySecret: [] paths: /sports/trending-matched: get: tags: - Sports summary: Top live/upcoming sports markets matched across Polymarket and Kalshi description: >- Finds games that have BOTH a Polymarket and a Kalshi entry in the cross-venue sports match cache, drops any entry whose embedded date is older than yesterday (UTC), enriches each surviving Kalshi side with a live volume figure (`volume_1h` falling back to `volume_total`), sorts descending by that volume, and truncates to `limit`. Title and `tokenId` come from the cached match record itself, not from a live provider call. Responses are cacheable at the edge. operationId: getSportsTrendingMatched parameters: - name: limit in: query required: false description: >- Maximum number of matched markets to return, sorted by Kalshi volume descending. schema: type: integer minimum: 1 maximum: 20 default: 5 example: 5 responses: '200': description: >- Trending cross-provider matched markets. Returns `{"matches": [], "count": 0}` immediately if the matching cache is empty. headers: Cache-Control: schema: type: string example: public, max-age=30, s-maxage=60 content: application/json: schema: $ref: '#/components/schemas/SportsTrendingMatchedResponse' '422': $ref: '#/components/responses/DataValidationError' '429': $ref: '#/components/responses/DataRateLimited' security: [] components: schemas: SportsTrendingMatchedResponse: type: object description: Top matched sports markets ranked by live Kalshi volume. required: - matches - count properties: matches: type: array items: $ref: '#/components/schemas/SportsTrendingMatch' count: type: integer description: Number of items in matches (after truncation to limit). example: 5 SportsTrendingMatch: type: object required: - slug - title - image - icon - volume1h - polymarket - kalshi properties: slug: type: string description: Game slug, used as the matching-cache key. example: nba-lal-bos-2026-01-15 title: type: string description: Human-readable game title, from the matching cache. example: Lakers vs Celtics image: type: - string - 'null' description: Always null — not populated by this endpoint. icon: type: - string - 'null' description: Always null — not populated by this endpoint. volume1h: type: number format: double description: >- Kalshi 1h (or total, as fallback) volume used for ranking, from the discover cache. example: 48213.5 polymarket: $ref: '#/components/schemas/SportsTrendingMatchPolymarketSide' kalshi: $ref: '#/components/schemas/SportsTrendingMatchKalshiSide' SportsTrendingMatchPolymarketSide: type: object required: - marketId - tokenId - price properties: marketId: type: string description: >- Equal to the game slug (Polymarket has no separate market id in this cache entry). example: nba-lal-bos-2026-01-15 tokenId: type: - string - 'null' description: Polymarket CLOB token id, from the matching cache. example: 10897234... price: type: - number - 'null' format: double example: 0.62 SportsTrendingMatchKalshiSide: type: object required: - marketId - eventTicker - price properties: marketId: type: - string - 'null' example: KXNBAGAME-26JAN15LALBOS-LAL eventTicker: type: - string - 'null' example: KXNBAGAME-26JAN15LALBOS price: type: - number - 'null' format: double example: 0.6 responses: DataValidationError: description: Request failed FastAPI parameter validation. content: application/json: schema: type: object required: - detail properties: detail: type: array description: >- One entry per failed field, with location, message, and error type. items: type: object additionalProperties: true DataRateLimited: description: > Rate limit exceeded for this route's sliding window, keyed on the session `sub` when authenticated and on the trusted client IP otherwise. Honor `Retry-After`. A per-API-key data ceiling (set per credential) rejects with `{"detail": "API key data rate limit exceeded"}` instead of the `error` envelope below. headers: Retry-After: schema: type: integer X-RateLimit-Limit: schema: type: integer X-RateLimit-Remaining: schema: type: integer X-RateLimit-Reset: schema: type: integer content: application/json: schema: type: object properties: error: type: string example: 'Rate limit exceeded: 100 per 1 minute' securitySchemes: apiKeyClientId: type: apiKey in: header name: X-Client-Id description: >- Credential client id (`kairos_ck_...`). Must be sent together with X-Api-Key and X-Api-Secret. apiKeyKey: type: apiKey in: header name: X-Api-Key description: 64-char hex API key. apiKeySecret: type: apiKey in: header name: X-Api-Secret description: 64-char hex API secret. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.