> ## Documentation Index
> Fetch the complete documentation index at: https://docs.calibri.io/llms.txt
> Use this file to discover all available pages before exploring further.

# List series

> Every series backing at least one active event, busiest first.
Derived from the live event cache — empty shelves never appear.
Use a series slug with `GET /public/events?series=` to expand
collapsed windows.



## OpenAPI

````yaml /api-reference/openapi/calibri.yaml get /api/v2/pythia/public/series
openapi: 3.1.0
info:
  title: Calibri API
  version: 1.0.0
  description: >-
    The Calibri API. Discover markets, read live books, place signed orders, and
    manage positions and account data.

    Routed by path prefix to the service that answers it — which is an
    implementation detail, not something a caller has to reason about.
servers:
  - description: Production
    url: https://calibri.io
security: []
tags:
  - name: Health
    description: Service liveness.
    x-displayName: Health
  - name: Events
    description: Discover events and their metadata.
    x-displayName: Events
  - name: Markets
    description: List markets and load market detail for trading.
    x-displayName: Markets
  - name: Series
    description: Recurring event series.
    x-displayName: Series
  - name: Tags
    description: Editorial shelves used to browse the catalogue.
    x-displayName: Tags
  - name: Market Data
    description: Order book, depth, trade tape, tickers, and candles.
    x-displayName: Market Data
  - name: Assets
    description: Underlying asset price history for price-feed markets.
    x-displayName: Assets
  - name: Community
    description: Leaderboard and platform activity.
    x-displayName: Community
  - name: Currencies
    description: Currency registry.
    x-displayName: Currencies
  - name: Trade
    description: Place, list, and cancel orders.
    x-displayName: Trade
  - name: Positions
    description: Your matched contracts.
    x-displayName: Positions
  - name: Wallet
    description: Self-custody Safe, passkey, session keys, and relay.
    x-displayName: Wallet
  - name: Rewards
    description: Maker rebates and referral earnings.
    x-displayName: Rewards
  - name: Account
    description: Balances, ledger, PnL, limits, preferences, and profile.
    x-displayName: Account
  - name: Categories
    description: Categories
    x-displayName: Categories
  - name: Other
    description: Other
    x-displayName: Other
externalDocs:
  description: ''
  url: ''
paths:
  /api/v2/pythia/public/series:
    get:
      tags:
        - Series
      summary: List series
      description: |-
        Every series backing at least one active event, busiest first.
        Derived from the live event cache — empty shelves never appear.
        Use a series slug with `GET /public/events?series=` to expand
        collapsed windows.
      responses:
        '200':
          content:
            application/json:
              schema:
                items:
                  $ref: '#/components/schemas/SeriesCount'
                type: array
          description: OK
      security: []
components:
  schemas:
    SeriesCount:
      properties:
        event_count:
          example: 12
          type: integer
        frequency:
          description: >-
            How often the feed produces events. Carried because the browse feed
            has

            to tell a rolling series from a one-off: a five-minute feed
            publishes 288

            events a day and must appear ONCE, not 288 times.
          example: daily
          type: string
        generated:
          description: >-
            Generated reports whether atlas's roller mints this series' events
            from a

            template (`series.roll_template` is set), rather than them being
            imported

            or hand-made.


            This is what says the events are the SAME QUESTION per window, and

            frequency cannot substitute for it. `seed-atp` and a daily crypto
            up/down

            feed are both `daily`; one publishes a different fixture each day
            and must

            be listed in full, the other asks "did BTC close up?" every day and
            must

            collapse to one card. Collapsing on frequency alone would bury the

            fixtures; not collapsing would show the same question six times.
          example: true
          type: boolean
        id:
          example: 789
          type: integer
        slug:
          example: daily-btc-close
          type: string
        title:
          example: Daily BTC Close
          type: string
      type: object

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.