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

# List the caller's netted usage entries grouped by chat

> One row per chat across every tool and bare-LLM usage combined — backs the /usage Detailed View tab's 'VyomFlow' aggregate group, whose total spans every category rather than one bucket. Optional `?period=` (7d/30d/90d/all, default all) scopes it to a rolling window.



## OpenAPI

````yaml /openapi.json get /api/v1/me/credits/usage-entries-by-chat
openapi: 3.1.0
info:
  title: VyomFlow API
  version: 1.0.0
  description: >-
    The versioned public REST surface (`/api/public/v1/*`, bearer API-key auth)
    plus the app's own internal `/api/v1/*` surface (Clerk session-token auth),
    generated directly from the same Zod contracts the Route Handlers validate
    against — never a hand-maintained duplicate. The MCP endpoint (`/api/mcp`)
    is a separate streamable-HTTP JSON-RPC transport, not expressible here — see
    the MCP guide.
servers:
  - url: https://api.vyomflow.co.in
    description: Production
  - url: http://localhost:3000
    description: Local development
security: []
paths:
  /api/v1/me/credits/usage-entries-by-chat:
    get:
      tags:
        - Credits
      summary: List the caller's netted usage entries grouped by chat
      description: >-
        One row per chat across every tool and bare-LLM usage combined — backs
        the /usage Detailed View tab's 'VyomFlow' aggregate group, whose total
        spans every category rather than one bucket. Optional `?period=`
        (7d/30d/90d/all, default all) scopes it to a rolling window.
      parameters:
        - schema:
            type: string
            enum:
              - 7d
              - 30d
              - 90d
              - all
            default: all
          required: false
          name: period
          in: query
      responses:
        '200':
          description: Netted usage entries grouped by chat.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListCreditUsageChatEntriesResponse'
        '401':
          description: Missing or invalid credentials.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiError'
      security:
        - ClerkBearer: []
components:
  schemas:
    ListCreditUsageChatEntriesResponse:
      type: object
      properties:
        entries:
          type: array
          items:
            type: object
            properties:
              chatId:
                type: string
              chatTitle:
                type: string
              amount:
                type: string
              timestamp:
                type: string
            required:
              - chatId
              - chatTitle
              - amount
              - timestamp
      required:
        - entries
    ApiError:
      type: object
      properties:
        error:
          type: object
          properties:
            code:
              type: string
            message:
              type: string
            details: {}
          required:
            - code
            - message
      required:
        - error
  securitySchemes:
    ClerkBearer:
      type: http
      scheme: bearer
      description: >-
        Clerk session token, `Authorization: Bearer <token>` — the first-party
        browser app's own auth. Used only by this internal `/api/v1/*` surface,
        never by `/api/public/v1/*`.

````