> ## 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 daily CU usage > Returns the compute units (CU) and CU-metered requests your organization used per UTC day in [from, to]. The range spans at most 92 days, inclusive. Only days with usage are listed, so a missing day means no usage was recorded for it. Daily history starts in October 2026; earlier days have no data. Daily figures are recorded separately from the period total returned by GET /usage/cu and can differ slightly from it. ## OpenAPI ````yaml GET /usage/cu/daily 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/daily: get: tags: - API Usage summary: Get daily CU usage description: >- Returns the compute units (CU) and CU-metered requests your organization used per UTC day in [from, to]. The range spans at most 92 days, inclusive. Only days with usage are listed, so a missing day means no usage was recorded for it. Daily history starts in October 2026; earlier days have no data. Daily figures are recorded separately from the period total returned by GET /usage/cu and can differ slightly from it. operationId: getDailyCuUsage parameters: - name: from in: query required: true description: First UTC day to include (YYYY-MM-DD). schema: type: string format: date example: '2026-10-01' - name: to in: query required: true description: >- Last UTC day to include (YYYY-MM-DD). Must be on or after from, and at most 91 days after it. schema: type: string format: date example: '2026-10-12' responses: '200': description: Success content: application/json: schema: type: object required: - from - to - days properties: from: type: string format: date example: '2026-10-01' to: type: string format: date example: '2026-10-12' days: type: array description: Days with usage, in date order. items: type: object required: - date - cuUsed - requests properties: date: type: string format: date example: '2026-10-08' cuUsed: type: string description: CU used that day, as an integer string. example: '630' requests: type: integer description: CU-metered requests served that day. example: 210 '400': description: Invalid or too-wide date range content: application/json: examples: malformedDate: summary: Date not in YYYY-MM-DD format value: statusCode: 400 timestamp: '2026-10-12T15:00:00.000Z' path: /api/v2/usage/cu/daily message: from must be a YYYY-MM-DD date impossibleDate: summary: Date that does not exist value: statusCode: 400 timestamp: '2026-10-12T15:00:00.000Z' path: /api/v2/usage/cu/daily message: from is not a valid date rangeTooWide: summary: Range reversed or longer than 92 days value: statusCode: 400 timestamp: '2026-10-12T15:00:00.000Z' path: /api/v2/usage/cu/daily message: to must be on or after from, and the range at most 92 days '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.