specification: FinOps Framework specificationVersion: '1.0' schema: https://www.finops.org/framework/ provider: Prove providerId: prove created: '2026-06-21' modified: '2026-06-21' reconciled: false tags: - Identity Verification - Authentication - Phone Intelligence - KYC - Fraud Prevention - FinOps - Cost Management - FOCUS description: >- FinOps view of Prove spend. Prove bills under a sales-led contract rather than a public rate card, so spend is driven by metered identity-verification and authentication transactions (Pre-Fill verifications, Trust Score / Unify authentications, Auth events, and Identity Manager records). Because rates are negotiated, cost allocation depends on tagging client request IDs and customer IDs per workload. Specific unit rates are not reconciled in this artifact. notes: >- Obtain the contracted unit rates and metering definitions from Prove and map them to the meters below during reconciliation. Distinguish billable successful verifications from non-billable failed or sandbox calls. sources: - https://www.prove.com - https://developer.prove.com - https://focus.finops.org/focus-specification/v1-3/ 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: Prove serviceCategory: Identity and Security billingModel: pricingCategory: Contract-Based billingFrequency: Monthly billingCurrency: USD chargeCategories: - Usage - Purchase focusColumns: ServiceName: Prove API ServiceCategory: Identity and Security ProviderName: Prove PublisherName: Prove InvoiceIssuerName: Prove BillingCurrency: USD ChargeCategory: Usage PricingCategory: Contract-Based meters: - name: prefill_verifications description: Pre-Fill verification flows completed (start/validate/challenge/complete), typically billed per successful verification. unit: verifications aggregation: sum dimensions: - account - clientCustomerId - clientRequestId - name: trust_score_authentications description: Unify / Trust Score authentications, billed per authentication or per recognized session. unit: authentications aggregation: sum dimensions: - account - clientCustomerId - name: auth_events description: Prove Auth phone authentication events (start/continue/finish). unit: authentications aggregation: sum dimensions: - account - clientCustomerId - name: identity_records description: Identities enrolled and maintained in the Identity Manager. unit: identities aggregation: sum dimensions: - account - clientCustomerId principles: - name: Visibility description: Tag every request with clientRequestId and clientCustomerId to attribute spend per workload and customer. - name: Allocation description: Map Pre-Fill, Trust Score, Auth, and Identity meters to internal cost centers and product lines. - name: Optimization description: Avoid redundant verifications by reusing enrolled identities and passive Unify recognition before initiating a fresh Pre-Fill flow. - name: Accountability description: Review monthly billable-transaction counts against the contracted commitment and forecast. maintainers: - FN: Kin Lane email: kin@apievangelist.com