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

# List daily bills

> Daily bills (one row per calendar day; project_id/key are filter dimensions; see nested model_details for model × token-type × key breakdown) with cursor pagination (`has_more`/`next`). Amounts are in milli-cent; billing data for day T becomes available at 07:00 (UTC+8) on day T+1; earlier returns `400 data_not_ready`.

> [!NOTE]
>
> This endpoint requires an Admin Key with the `billing:read` scope.

> [!NOTE]
>
> **Readiness and amount semantics**: billing data for day T becomes available at 07:00 (UTC+8) on day T+1; earlier returns `400 data_not_ready`. Amounts are split into cash (`recharge_fee`) and voucher (`voucher_fee`) parts summing to `total_fee` (actual amount charged). The time window is left-closed, right-open, aligned to CST day boundaries.


## OpenAPI

````yaml GET /v1/admin/organizations/billings/daily_bills
openapi: 3.0.3
info:
  title: Kimi Admin API
  version: 2026-10-20-beta
  description: >-
    ## Overview


    The Kimi Admin API lets organization administrators manage members,
    invitations, projects, and inference API keys programmatically, and query
    billing, usage, and audit logs — without signing in to the console. It is a
    control-plane API: Admin API credentials cannot call any inference endpoint,
    and inference API keys cannot call this API.


    The base URL is `https://api.moonshot.ai/v1`.


    <Note>

    The Admin API is in **beta** and opens to organizations that have completed
    organization verification. After completing organization verification under
    **Console → Organization → Organization Verification**, organization admins
    can create Admin API keys under **Organization → Admin API Keys**.

    </Note>


    ## Authentication


    Send the Admin API secret (`sk-admin-*`) as a Bearer token:


    ```sh

    curl https://api.moonshot.ai/v1/admin/organizations \
      --header "Authorization: Bearer $MOONSHOT_ADMIN_KEY"
    ```


    A key is bound to exactly one organization; the organization is always
    derived from the key — cross-organization access is impossible by
    construction. If the key owner leaves the organization or is deactivated,
    the key stops working within 30 seconds. Secrets are shown only once, at
    creation or rotation; store them safely.


    ## Scopes


    Every key carries scopes chosen at creation:


    | Scope | Type | Covers |

    | --- | --- | --- |

    | `billing:read` | read | Daily/product bills, request details, interrupted
    requests, account balance, usage aggregation |

    | `org:read` | read | Members, invitations, projects, project members,
    inference API key metadata, spend limits, organization rate limits |

    | `org:write` | write | Member/invitation/project/key writes (implies
    `org:read` — no separate grant needed) |

    | `audit:read` | read | Audit log events |

    | `all` | read+write | Everything above; new scopes are covered
    automatically |


    Write endpoints additionally require the key owner to be an organization
    admin at call time and are rate-limited more strictly (see below).


    ## Rate limits


    | Class | Limit |

    | --- | --- |

    | Read endpoints | 60 requests/minute per organization |

    | Write endpoints | 20 requests/minute per organization |

    | Request details, interrupted requests, usage aggregation | 5 concurrent
    requests per organization |


    Rate limits are counted per organization and endpoint: all Admin Keys in the
    same organization share the quota — more keys do not raise it. Exceeding a
    limit returns `429 rate_limit_exceeded` / `concurrency_limit_exceeded`.


    ## Pagination


    Paginated endpoints (daily/product bills, request details, interrupted
    requests, usage aggregation, audit logs) use cursor pagination: responses
    carry `has_more` and `next`; pass `next` back as the `cursor` query
    parameter. Page size by endpoint: daily/product bills and usage default 100,
    max 1000; request details and interrupted requests default 100, max 10000;
    audit logs default 20, max 100. The cursor carries only the page position —
    restate all filters on every page.


    Organization collection endpoints (members, invitations, projects, project
    members, API keys) return the full list in one response, with no pagination
    parameters. Query parameters outside the protocol (such as `page_size`) are
    silently ignored — double-check parameter names.


    ## Errors


    Errors follow a unified envelope:


    ```json

    {
      "error": {
        "type": "invalid_request_error",
        "code": "invalid_date_range",
        "message": "end must be greater than start.",
        "param": "end",
        "request_id": "..."
      }
    }

    ```


    `data_not_ready` gates the bill endpoints' readiness: current-day data
    becomes ready on T-1 and is queryable from 07:00 CST the next day.


    ## Data conventions


    - Monetary amounts are in **milli-cent** (1 USD = 100,000 milli-cent).

    - Timestamps in query parameters are epoch **milliseconds**; timestamps in
    response bodies are RFC 3339 unless stated otherwise.

    - Time windows are left-closed, right-open, aligned to CST day boundaries;
    timestamps in query parameters are epoch milliseconds, and RFC 3339 in
    responses unless stated otherwise. Passing seconds returns empty data rather
    than an error — check your units.

    - Billing data becomes ready on T-1: the current day is queryable from 07:00
    CST the next day and returns `400 data_not_ready` earlier; interrupted
    request details are exempt (near real time).

    - Retention and window caps: daily/product bills 365 days; request details
    and interrupted requests 90 days with a 31-day per-call cap; audit logs 31
    days per call; usage aggregation windows by granularity (`1m` ≤24 hours,
    `1h` ≤31 days, `1d` ≤93 days, cut on Asia/Shanghai natural days).

    - Each organization holds at most 10 active Admin API keys.
servers:
  - url: https://api.moonshot.ai
    description: Production
security:
  - AdminBearerAuth: []
paths:
  /v1/admin/organizations/billings/daily_bills:
    get:
      tags:
        - Billing
      summary: List daily bills
      description: >-
        Daily bills (one row per calendar day; project_id/key are filter
        dimensions; see nested model_details for model × token-type × key
        breakdown) with cursor pagination (`has_more`/`next`). Amounts are in
        milli-cent; billing data for day T becomes available at 07:00 (UTC+8) on
        day T+1; earlier returns `400 data_not_ready`.
      operationId: listDailyBillsV2
      parameters:
        - $ref: '#/components/parameters/Start'
        - $ref: '#/components/parameters/End'
        - $ref: '#/components/parameters/ProjectID'
        - $ref: '#/components/parameters/APIKey'
        - name: limit
          in: query
          required: false
          schema:
            type: integer
            minimum: 1
            maximum: 1000
            default: 100
          description: >-
            Page size. Defaults to 100, maximum 1000. Rows are bounded by the
            requested window (one row per natural day), so one page usually
            covers the whole window.
        - name: cursor
          in: query
          required: false
          schema:
            type: string
          description: >-
            Cursor from the previous response `next` field. The cursor carries
            only the page position; all query parameters must be restated on
            every page. Keep them unchanged while paginating (except limit) —
            the server does not check them for consistency.
      responses:
        '200':
          description: Daily bills.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DailyBillsResponseV2'
        '400':
          description: >-
            Invalid request parameters (illegal/out-of-retention time window,
            invalid enum value, or illegal limit/cursor).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BillingErrorResponse'
        '401':
          description: >-
            Authentication failed (the Admin API key is invalid,
            deleted/expired, or its owner is no longer active).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BillingErrorResponse'
        '403':
          description: Insufficient scope (the Admin Key lacks the billing:read scope).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BillingErrorResponse'
        '404':
          description: Resource not found (no data for this organization).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BillingErrorResponse'
        '429':
          description: >-
            Rate limit exceeded (requests-per-minute cap or concurrency cap
            hit).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BillingErrorResponse'
        '500':
          description: Internal server error (contact support with the request_id).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BillingErrorResponse'
      security:
        - AdminBearerAuth: []
components:
  parameters:
    Start:
      name: start
      in: query
      required: true
      schema:
        type: integer
        format: int64
        minimum: 0
      description: >-
        Start time in milliseconds, inclusive, e.g. `1790784000000` (2026-10-01
        00:00 CST).
      example: 1790784000000
    End:
      name: end
      in: query
      required: true
      schema:
        type: integer
        format: int64
        minimum: 0
      description: >-
        End time in milliseconds, exclusive, e.g. `1792598400000` (2026-10-22
        00:00 CST).
      example: 1792598400000
    ProjectID:
      name: project_id
      in: query
      required: false
      schema:
        type: array
        items:
          type: string
      style: form
      explode: true
      description: >-
        Project IDs. Every project must belong to the authenticated
        organization.
    APIKey:
      name: key
      in: query
      required: false
      schema:
        type: array
        items:
          type: string
      style: form
      explode: true
      description: >-
        Business API key IDs. Every key must belong to the authenticated
        organization.
  schemas:
    DailyBillsResponseV2:
      type: object
      required:
        - data
        - has_more
        - next
      additionalProperties: false
      properties:
        data:
          type: array
          description: >-
            Daily bill rows (one per natural day; see model_details for the
            breakdown).
          items:
            $ref: '#/components/schemas/DailyBillV2'
        has_more:
          type: boolean
          description: Whether there is a next page.
        next:
          type: string
          nullable: true
          description: >-
            Cursor for the next page. Pass it back verbatim as the `cursor`
            query parameter.
    BillingErrorResponse:
      type: object
      required:
        - error
      additionalProperties: false
      properties:
        error:
          $ref: '#/components/schemas/BillingErrorBody'
    DailyBillV2:
      type: object
      required:
        - date
        - total_fee
        - recharge_fee
        - voucher_fee
        - model_details
      additionalProperties: false
      properties:
        date:
          type: string
          example: '2026-06-30'
          description: Billing date (calendar day).
        total_fee:
          type: integer
          format: int64
          minimum: 0
          description: Total fee (milli-cent).
        recharge_fee:
          type: integer
          format: int64
          minimum: 0
          description: Recharge account deduction (milli-cent).
        voucher_fee:
          type: integer
          format: int64
          minimum: 0
          description: Voucher account deduction (milli-cent).
        model_details:
          type: array
          description: >-
            Model inference breakdown of the day, one row per model x token type
            x API key, sorted by model_id, token_type, then key. Only
            token-metered inference items are included; non-token items
            (cache-call, tool_call, cache storage) and business-type charges
            (e.g. BatchAPI) stay in the outer fees only, so outer total_fee
            minus the sum of model_details fees equals those other charges.
            Empty array for days without model inference consumption.
          items:
            $ref: '#/components/schemas/DailyBillModelDetailV2'
    BillingErrorBody:
      type: object
      required:
        - type
        - code
        - message
        - request_id
      additionalProperties: false
      properties:
        type:
          type: string
          example: invalid_request_error
        code:
          type: string
          description: Billing-domain error codes (subset).
          enum:
            - invalid_request
            - invalid_date_range
            - date_range_too_large
            - date_range_out_of_retention
            - data_not_ready
            - invalid_cursor
            - invalid_api_key
            - api_key_inactive
            - insufficient_scope
            - resource_not_found
            - rate_limit_exceeded
            - concurrency_limit_exceeded
            - internal_server_error
        message:
          type: string
        param:
          type: string
          nullable: true
        request_id:
          type: string
    DailyBillModelDetailV2:
      type: object
      required:
        - model_id
        - token_type
        - tokens
        - key
        - total_fee
        - recharge_fee
        - voucher_fee
      additionalProperties: false
      properties:
        model_id:
          type: string
          example: kimi-k2.6
          description: Model ID.
        token_type:
          type: string
          enum:
            - prompt
            - completion
            - auto-caching
            - cache-write-5m
            - cache-write-1h
          description: >-
            Token billing item, same naming as the underlying product. New token
            billing types extend this enum in the future.
        tokens:
          type: integer
          format: int64
          description: >-
            Billed tokens of this item. prompt excludes cache-hit tokens;
            auto-caching reports the cache-hit tokens.
        key:
          type: string
          description: Business API key ID.
        total_fee:
          type: integer
          format: int64
          minimum: 0
          description: Total fee of this row (milli-cent; = recharge_fee + voucher_fee).
        recharge_fee:
          type: integer
          format: int64
          minimum: 0
          description: Recharge account deduction (milli-cent).
        voucher_fee:
          type: integer
          format: int64
          minimum: 0
          description: Voucher account deduction (milli-cent).
  securitySchemes:
    AdminBearerAuth:
      type: http
      scheme: bearer
      bearerFormat: Admin API Secret (sk-admin-*)
      description: >-
        Send the Admin API secret as a Bearer token in the Authorization header
        (`Bearer sk-admin-***`). Create Admin Keys under Console → Organization
        → Admin API Keys.

````