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

# Retrieve usage

> Daily submissions, accepted videos and spend, optionally for one mission.



## OpenAPI

````yaml /openapi.yaml get /usage
openapi: 3.1.0
info:
  title: Capibo API
  version: '1.0'
  description: |
    Plan data-collection missions, track quality review, and pull accepted
    egocentric videos into your robot-training pipeline.
  contact:
    name: Capibo support
    email: support@capibo.work
servers:
  - url: https://api.capibo.work/v1
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Missions
    description: Create and manage data-collection missions.
  - name: Planning
    description: Price a mission before you launch it.
  - name: Datasets
    description: Accepted videos, grouped per mission.
  - name: Videos
    description: Individual submissions and their quality-review results.
  - name: Exports
    description: Package a dataset into a training format and deliver it.
  - name: Billing
    description: Prepaid credits, transactions and promo codes.
  - name: Usage
    description: Collection volume and spend over time.
  - name: Webhooks
    description: Get notified when videos are accepted, missions finish and more.
paths:
  /usage:
    get:
      tags:
        - Usage
      summary: Retrieve usage
      description: >-
        Daily submissions, accepted videos and spend, optionally for one
        mission.
      operationId: getUsage
      parameters:
        - name: from
          in: query
          required: true
          schema:
            type: string
            format: date
            example: '2026-10-01'
        - name: to
          in: query
          required: true
          schema:
            type: string
            format: date
            example: '2026-10-24'
        - name: mission_id
          in: query
          schema:
            type: string
            example: MSN-1042
      responses:
        '200':
          description: Usage for the period.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Usage'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
components:
  schemas:
    Usage:
      type: object
      properties:
        from:
          type: string
          format: date
        to:
          type: string
          format: date
        totals:
          type: object
          properties:
            submitted:
              type: integer
              example: 8761
            accepted:
              type: integer
              example: 7450
            cost:
              type: number
              example: 22803.12
        daily:
          type: array
          items:
            type: object
            properties:
              date:
                type: string
                format: date
              submitted:
                type: integer
              accepted:
                type: integer
              cost:
                type: number
    Error:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - type
            - code
            - message
          properties:
            type:
              type: string
              enum:
                - invalid_request
                - authentication_error
                - permission_denied
                - not_found
                - conflict
                - payment_required
                - rate_limited
                - api_error
            code:
              type: string
              description: Machine-readable reason.
            message:
              type: string
              description: Human-readable explanation.
            param:
              type: string
              description: The parameter that caused the error
              if any.: null
  responses:
    BadRequest:
      description: The request is invalid.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              type: invalid_request
              code: parameter_invalid
              message: tasks[0].videos must be at least 1.
              param: tasks[0].videos
    Unauthorized:
      description: The API key is missing, invalid or revoked.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              type: authentication_error
              code: api_key_invalid
              message: Invalid API key.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        An API key from **Settings → API keys**, e.g. `cpb_live_…` or
        `cpb_test_…`.

````

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