> ## Documentation Index > Fetch the complete documentation index at: https://docs.ornn.com/llms.txt > Use this file to discover all available pages before exploring further. # Get GPU usage cost > Returns GPU-hours and usage cost per reservation for the part of each reservation inside the date range, using the reserved GPU count and agreed price. This is informational, not an invoice. ## OpenAPI ````yaml openapi.yaml GET /commerce/billing/showback openapi: 3.1.0 info: title: Ornn compute API version: 1.0.0 description: >- Customer HTTP API for Ornn GPU capacity. It covers reserved capacity and nodes, VM and Bare Metal access, Kubernetes and Slurm clusters, SSH keys, storage volumes and GitHub repositories, private networks, monitoring, buying and selling capacity (Reserve, Market, Spot, and Relist), and billing. API keys are scoped to one organization and act with their creator's access there; account, team, and API-key management stay in the console. Most operations require an approved organization. See https://docs.ornn.com/api-keys to create a key and https://docs.ornn.com/guides/kubernetes-api for an end-to-end Kubernetes integration. Examples use fictional IDs and credentials. The info.version field identifies the contract revision, not a shared API path version. contact: email: support@ornn.com servers: - url: https://api.ornn.com description: Production security: - OrnnApiKey: [] tags: - name: Authentication - name: Reservations - name: GPU nodes - name: Clusters - name: Workers - name: Virtual machines description: >- Choose a VM disk, launch VM access on a reservation, and read each VM's status, launch progress, and SSH connection details. - name: Bare Metal description: >- Launch Bare Metal access on a reservation, read a host's readiness and SSH connection details, and reboot or hard reset it. - name: SSH keys description: >- Register public keys for your organization, choose which keys a VM or Bare Metal reservation uses, and queue key delivery to machines. Slurm clusters take organization key IDs at launch. Kubernetes API access does not use SSH keys. - name: Reserve description: >- Browse reserved-capacity listings and their terms, and post, cancel, or accept offers. Reserve listings are visible to approved organizations. - name: Market description: >- Browse relisted capacity and buy windows at the asking price, paid up front. Open to every member of your organization. - name: Spot description: >- Hourly order books for VMs with 1, 2, 4, or 8 GPUs on one node: read books, trades, and quotes, place and cancel bids, and follow fills. - name: Relist description: >- Sell whole nodes from a reservation you hold at your asking price, and manage those listings. - name: Storage description: >- Managed volumes, their files, and GitHub repository pulls. Volumes belong to the API key's creator in the key's organization. - name: Networks description: >- Organization private networks and the WireGuard configs you use to reach private machines and clusters. - name: Monitoring description: >- Machine telemetry and console logs for capacity your organization holds. Reads are limited to your reservation window. - name: Billing description: >- Invoices, billing summary, usage cost, Ornn credits, and account statements. Saving a card and paying invoices stay in the console. externalDocs: description: REST integration walkthrough url: >- https://docs.ornn.com/guides/kubernetes-access#provision-and-manage-through-rest paths: /commerce/billing/showback: get: tags: - Billing summary: Get GPU usage cost description: >- Returns GPU-hours and usage cost per reservation for the part of each reservation inside the date range, using the reserved GPU count and agreed price. This is informational, not an invoice. operationId: platformGetUsageReport parameters: - name: start in: query required: true description: First day of the range, YYYY-MM-DD. schema: type: string format: date example: '2026-10-01' - name: end in: query required: true description: Last day of the range, YYYY-MM-DD, on or after start. schema: type: string format: date example: '2026-10-14' responses: '200': description: Usage by reservation. content: application/json: schema: $ref: '#/components/schemas/PlatformUsageReport' example: windowStart: '2026-10-01' windowEnd: '2026-10-14' rows: - reservationId: 11111111-1111-4111-8111-111111111111 status: active gpuCount: 8 windowStart: '2026-10-07' windowEnd: '2026-10-14' gpuHours: 1344 costCents: 336000 sharePct: '100.00' totalGpuHours: 1344 totalCostCents: 336000 '400': description: start or end is missing, malformed, or out of order. content: application/json: schema: $ref: '#/components/schemas/PlatformPlainError' example: error: start must be YYYY-MM-DD '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' default: $ref: '#/components/responses/Error' components: schemas: PlatformUsageReport: type: object properties: windowStart: type: string format: date windowEnd: type: string format: date rows: type: array items: type: object properties: reservationId: type: string format: uuid status: type: string gpuCount: type: integer windowStart: type: string format: date windowEnd: type: string format: date gpuHours: type: number costCents: type: integer format: int64 sharePct: type: string description: This reservation's share of total cost, as a decimal string. totalGpuHours: type: number totalCostCents: type: integer format: int64 PlatformPlainError: type: object description: Error body with a machine-readable string. Check the HTTP status first. required: - error properties: error: type: string Error: type: object properties: code: type: string detail: oneOf: - type: string - type: object required: - code - message properties: code: type: string message: type: string responses: Unauthorized: description: >- The credential is missing, invalid, revoked, or no longer belongs to a current organization member. Check the HTTP status before parsing the body. content: application/json: schema: $ref: '#/components/schemas/Error' Forbidden: description: >- The credential lacks access to this operation, or the organization requires approval. An API key does not bypass these checks. content: application/json: schema: $ref: '#/components/schemas/Error' Error: description: >- Unsuccessful request. Check HTTP status first. Errors may have detail.code/detail.message, a string detail and optional top-level code, or an empty/non-JSON body. 401: invalid credential; 403: access or approval required; 404: not visible or credentials not ready; 409: lifecycle conflict; 429: back off; 5xx: service failure. Inspect current state before retrying mutations. content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: OrnnApiKey: type: http scheme: bearer bearerFormat: ornn_sk_... description: >- Create an organization API key in Account Settings > Developer. Do not send this key to the Kubernetes API server. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.