FOCUS Specification
FinOps Foundation — component or architectural context.
Definition
A bounded technical identity.
Token-based consumption measures or prices selected AI activity using input, output, cached, reasoning, or other provider-defined token units.
Why it matters
Make the technical question explicit.
Token units are widely available but can vary by model, tokenizer, provider, context policy, caching, and workload, so they require normalization before comparison or allocation.
Technical context
AI economics
This page provides a stable descriptive reference for the stated concept. Implementations, products, operating models, and applicable requirements remain context-specific and replaceable.
Evidence and terminology boundary
Evidence class C.
The cited authority supports component concepts or architectural context. It does not define this exact compound identity; LJP uses the phrase descriptively.
Machine-readable resources
Public identity resources
Namespace manifest · LLM summary · Robots policy · Sitemap
No ontology, API, agent card, MCP endpoint, or executable service is published. JSON-LD describes this page; it is not a formal vocabulary.
Credibility boundary
What this page does not claim.
The identity is not a tokenizer, meter, price list, billing service, or accounting rule.
This identity is not an agent, workload, sensor, control plane, runtime, operating platform, database, network, or standards authority. It is not an endorsement, certification, or conformance claim.
Library context
Portfolio discovery record
View the Library record. Licensing, stewardship, partnership or acquisition discussions welcome.