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

# Get current CU usage

> Returns the compute units (CU) your organization has used in the current billing period. Each request is charged at the CU pricing in effect when it was served. The period is your current subscription period in whole UTC days, or the current UTC calendar month if you have no active subscription period. `cuLimit`, `cuRemaining` and `usagePercentage` are null when your organization has no CU allowance.



## OpenAPI

````yaml GET /usage/cu
openapi: 3.0.1
info:
  title: Risk Score API
  description: API definition for Webacy Risk Scores
  version: 1.12.1
servers:
  - url: https://api.webacy.com
    description: Webacy Risk Score API (Production)
  - url: https://api-development.webacy.com
    description: Webacy Risk Score API (Development)
  - url: http://0.0.0.0:3030/api/v1/risk-score
    description: Webacy Risk Score API - Local
security:
  - api_key: []
tags:
  - name: Webhooks
    description: >-
      Subscribe to and manage real-time event notifications (currently
      DEPEG_TIER_CHANGE)
  - name: Threat Risks
    description: Analyze addresses for security threats and malicious activity
  - name: Sanction Checks
    description: Check addresses against OFAC and other sanction lists
  - name: Approval Risks
    description: Analyze token approvals and associated risks
  - name: Transaction Risks
    description: Assess risk details for blockchain transactions
  - name: Exposure Risk
    description: Understand risk profile and exposure of addresses
  - name: Contract Risk
    description: Real-time smart contract security analysis
  - name: URL Risks
    description: Analyze URLs for phishing and security threats
  - name: API Usage
    description: Monitor and manage API consumption
  - name: Holder Analysis
    description: Token holder distribution and sniper detection
  - name: Address Poisoning
    description: Detect address poisoning attack patterns
  - name: Token Analysis
    description: Comprehensive token security and market analysis
  - name: Pool Analysis
    description: Liquidity pool data and analysis
  - name: Transaction Scanning
    description: Scan and simulate transactions for risks
  - name: trading-lite
    description: Lightweight trading risk assessment
  - name: RWA & Pegged Tokens
    description: >-
      Real-world asset and pegged-token analytics (supply flows, mint/burn
      velocity)
  - name: Vault Risk v3
    description: >-
      Webacy-native v3 vault risk surface — composite grade, categories,
      coverage, and the framework taxonomy.
  - name: RWA Risk v3
    description: >-
      Webacy-native v3 RWA / stablecoin risk surface — composite grade,
      structural-health criteria, and batch scoring.
  - name: Stablecoins v3
    description: >-
      Stablecoin-only aliases of the v3 RWA routes: same grades, same shapes,
      `segment` fixed to `stablecoin`.
paths:
  /usage/cu:
    get:
      tags:
        - API Usage
      summary: Get current CU usage
      description: >-
        Returns the compute units (CU) your organization has used in the current
        billing period. Each request is charged at the CU pricing in effect when
        it was served. The period is your current subscription period in whole
        UTC days, or the current UTC calendar month if you have no active
        subscription period. `cuLimit`, `cuRemaining` and `usagePercentage` are
        null when your organization has no CU allowance.
      operationId: getCuUsage
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                required:
                  - periodStart
                  - periodEnd
                  - cuUsed
                  - requests
                  - cuLimit
                  - cuRemaining
                  - usagePercentage
                properties:
                  periodStart:
                    type: string
                    format: date-time
                    description: Start of the current billing period (UTC midnight).
                    example: '2026-10-01T00:00:00.000Z'
                  periodEnd:
                    type: string
                    format: date-time
                    description: >-
                      End of the current billing period (UTC midnight,
                      exclusive).
                    example: '2026-11-01T00:00:00.000Z'
                  cuUsed:
                    type: string
                    description: CU used in the period, as an integer string.
                    example: '125000'
                  requests:
                    type: integer
                    description: CU-metered requests served in the period.
                    example: 40000
                  cuLimit:
                    type: string
                    nullable: true
                    description: >-
                      CU allowance for the period, including top-ups, as an
                      integer string. Null when the organization has no CU
                      allowance.
                    example: '500000'
                  cuRemaining:
                    type: string
                    nullable: true
                    description: >-
                      CU left in the period (never negative), as an integer
                      string. Null when the organization has no CU allowance.
                    example: '375000'
                  usagePercentage:
                    type: number
                    nullable: true
                    description: >-
                      Share of the allowance used, as a percentage with one
                      decimal. Null when the organization has no CU allowance.
                    example: 25
        '404':
          description: >-
            Organization not found. Returned when no usage record exists yet for
            the API key's organization, for example right after the key is
            created.
          content:
            application/json:
              example:
                message: Organization not found
      security:
        - api_key: []
components:
  securitySchemes:
    api_key:
      type: apiKey
      in: header
      name: x-api-key

````

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