specification: FinOps Framework specificationVersion: '1.0' schema: https://www.finops.org/framework/ provider: Uniblock providerId: uniblock created: '2026-05-04' # Provenance stamped 2026-08-11: this artifact was written by the API Evangelist # bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35. method: generated modified: '2026-05-05' reconciled: true tags: - Blockchain - Web3 - FinOps - FOCUS description: FOCUS-aligned FinOps for Uniblock - monthly subscription tier plus a compute-unit (CU) envelope that meters JSON-RPC and unified-API consumption across providers and chains. sources: - https://uniblock.dev/pricing - https://docs.uniblock.dev/guides/uniblock/rate-limits alignedWith: framework: FinOps Foundation Framework frameworkUrl: https://www.finops.org/framework/ dataSpec: FOCUS dataSpecVersion: '1.3' dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/ publisherName: Uniblock serviceCategory: Web3 Infrastructure billingModel: pricingCategory: Tiered Subscription with CU Envelope billingFrequency: Monthly billingCurrency: USD chargeCategories: - Purchase - Usage - Adjustment - Credit focusColumns: ServiceName: Uniblock ServiceCategory: Web3 Infrastructure ProviderName: Uniblock PublisherName: Uniblock InvoiceIssuerName: Uniblock BillingCurrency: USD ChargeCategory: Purchase PricingCategory: Subscription meters: - name: plan_subscription description: Monthly Uniblock plan subscription (Growth, Pro, Business). unit: month aggregation: sum dimensions: - plan - billing_term - name: compute_units description: Compute units consumed across JSON-RPC, Unified, and Direct APIs. CU cost per call varies by method. unit: compute_unit aggregation: sum dimensions: - api - method - chain - project - name: projects description: Number of active projects used in the month, capped per plan tier. unit: project aggregation: max dimensions: - plan principles: - name: Visibility description: Track CU consumption per project in the Uniblock dashboard; correlate request volume to method-level CU costs to identify cost-driver endpoints. - name: Allocation description: Use separate Uniblock projects per consuming team, environment, or product line so CU spend can be attributed without invoice splitting. - name: Optimization description: Reduce CU usage with response caching, batching, lower poll frequencies, and selecting cheaper unified methods over high-cost direct provider calls. Switch to annual billing for the built-in discount. - name: Accountability description: Set CU consumption alerts ahead of plan envelope exhaustion to avoid 429s; assign a project owner for each Uniblock project to handle plan upgrades and traffic anomalies. maintainers: - FN: Kin Lane email: kin@apievangelist.com