specification: FinOps Framework specificationVersion: '1.0' schema: https://www.finops.org/framework/ 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/ provider: Cloudmersive providerId: cloudmersive publisherName: Cloudmersive serviceCategory: 'Developer Tools / API' 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: - FinOps - FOCUS - Documents - Conversions - OCR - Cost Management description: 'FOCUS-aligned FinOps for Cloudmersive: flat monthly subscription tiers (Basic through Business Advantage) with included call quotas plus enterprise / on-premises options for committed throughput.' sources: - https://www.cloudmersive.com/pricing - https://www.cloudmersive.com/pricing-small-business billingModel: pricingCategory: Tiered Subscription billingFrequency: Monthly billingCurrency: USD chargeCategories: - Purchase - Usage - Tax - Adjustment focusColumns: ServiceName: Cloudmersive ServiceCategory: 'Developer Tools / API' ProviderName: Cloudmersive PublisherName: Cloudmersive InvoiceIssuerName: Cloudmersive PricingCategory: Tiered Subscription PricingUnit: subscription-month BillingCurrency: USD ChargeCategory: Purchase meters: - name: subscription_fee description: Flat monthly subscription fee for the active plan tier. unit: month aggregation: sum dimensions: - plan - name: api_calls description: Count of API calls consumed against the plan's monthly allowance. unit: request aggregation: sum dimensions: - plan - product - api_key - name: concurrency_peak description: Peak concurrent requests per second observed against the API key. unit: request aggregation: max dimensions: - plan - api_key principles: - name: Visibility description: Monitor monthly call counts via the Cloudmersive customer portal; alert before exhausting the plan quota since calls in excess queue rather than fail fast. - name: Allocation description: Issue separate API keys per environment and per consuming application so call counts can be attributed to a team or product. - name: Optimization description: Right-size the plan against observed monthly volume and concurrency. For sustained traffic above 4 calls/second, evaluate single-tenant cloud or on-premises deployment instead of stacking small-business plans. - name: Accountability description: Tie subscription renewals to the engineering team consuming the API; review quota burn-down mid-cycle and escalate to a higher tier before the queue depth materially impacts SLAs. maintainers: - FN: Kin Lane email: kin@apievangelist.com