specification: FinOps Framework specificationVersion: '1.0' schema: https://www.finops.org/framework/ provider: Jina AI providerId: jina-ai 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 - AI - Embeddings - LLM description: 'FOCUS-aligned FinOps for Jina AI: token-based pay-as-you-go metering across Embeddings, Reranker, Reader, Classifier, Segmenter, and DeepSearch. Token balance on the API key drives both cost and the rate-limit tier (Free / Paid / Premium). Cloud-marketplace procurement available via AWS, Azure, GCP.' sources: - https://jina.ai/embeddings/ - https://jina.ai/api-dashboard/ 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: Jina AI GmbH serviceCategory: AI Infrastructure billingModel: pricingCategory: Token-Based Usage billingFrequency: On-Demand billingCurrency: USD chargeCategories: - Purchase - Usage - Refund - Credit focusColumns: ServiceName: Jina AI ServiceCategory: AI Infrastructure ProviderName: Jina AI PublisherName: Jina AI GmbH InvoiceIssuerName: Jina AI GmbH BillingCurrency: USD meters: - name: tokens_consumed unit: token aggregation: sum dimensions: - service - model - api_key - name: embedding_requests unit: request aggregation: sum dimensions: - model - input_modality - name: reranker_requests unit: request aggregation: sum dimensions: - model - name: reader_requests unit: request aggregation: sum dimensions: - mode - name: token_balance unit: token aggregation: max dimensions: - api_key principles: - name: Visibility description: Use the Jina API Dashboard to monitor remaining token balance per API key and per-service consumption; export usage to your data warehouse for FOCUS-aligned reporting. - name: Allocation description: Issue separate API keys per team / product / environment so token consumption maps cleanly to a chargeback dimension; tag application traces with the key identifier. - name: Optimization description: Choose the smallest model that hits quality bar (e.g., jina-embeddings-v2 vs v3), truncate input text before embedding, cache embeddings of stable corpora, batch reranker queries, and use the Reader caching path (r.jina.ai) for stable URLs. - name: Accountability description: AI / Search platform owner reconciles monthly Stripe invoices (or marketplace bills) against forecasted token spend; sets balance-low alerts on production keys. maintainers: - FN: API Evangelist email: info@apievangelist.com