FinOps Foundation · Schema
FOCUS Contract Commitment Record
A contract commitment record as defined in FOCUS v1.3. Isolates contract terms including start and end dates, remaining units, and descriptions from cost and usage rows.
BudgetsCostsFinOps
Properties
| Name | Type | Description |
|---|---|---|
| CommitmentDiscountId | string | The unique identifier assigned to a commitment discount by the provider. |
| CommitmentDiscountName | stringnull | The display name assigned to a commitment discount. |
| CommitmentDiscountType | stringnull | A provider-assigned label describing the type of commitment discount. |
| CommitmentDiscountCategory | string | Whether the commitment discount is based on usage quantity or cost. |
| CommitmentStartDate | string | The start date and time of the contract commitment. |
| CommitmentEndDate | string | The end date and time of the contract commitment. |
| CommitmentTotalQuantity | numbernull | The total quantity of the commitment purchased. |
| CommitmentRemainingQuantity | numbernull | The remaining quantity of the commitment that has not yet been consumed. |
| CommitmentUnit | stringnull | The unit of measurement for the commitment quantity. |
| CommitmentDescription | stringnull | A human-readable description of the contract commitment. |
| BillingAccountId | string | The unique identifier for the billing account associated with the commitment. |
| BillingAccountName | stringnull | The display name for the billing account. |
| ProviderName | string | The name of the entity that made the commitment discount available. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/finops-foundation/refs/heads/main/json-schema/finops-foundation-contract-commitment-record-schema.json",
"title": "FOCUS Contract Commitment Record",
"description": "A contract commitment record as defined in FOCUS v1.3. Isolates contract terms including start and end dates, remaining units, and descriptions from cost and usage rows.",
"type": "object",
"properties": {
"CommitmentDiscountId": {
"type": "string",
"description": "The unique identifier assigned to a commitment discount by the provider."
},
"CommitmentDiscountName": {
"type": ["string", "null"],
"description": "The display name assigned to a commitment discount."
},
"CommitmentDiscountType": {
"type": ["string", "null"],
"description": "A provider-assigned label describing the type of commitment discount."
},
"CommitmentDiscountCategory": {
"type": "string",
"enum": ["Spend", "Usage"],
"description": "Whether the commitment discount is based on usage quantity or cost."
},
"CommitmentStartDate": {
"type": "string",
"format": "date-time",
"description": "The start date and time of the contract commitment."
},
"CommitmentEndDate": {
"type": "string",
"format": "date-time",
"description": "The end date and time of the contract commitment."
},
"CommitmentTotalQuantity": {
"type": ["number", "null"],
"description": "The total quantity of the commitment purchased."
},
"CommitmentRemainingQuantity": {
"type": ["number", "null"],
"description": "The remaining quantity of the commitment that has not yet been consumed."
},
"CommitmentUnit": {
"type": ["string", "null"],
"description": "The unit of measurement for the commitment quantity."
},
"CommitmentDescription": {
"type": ["string", "null"],
"description": "A human-readable description of the contract commitment."
},
"BillingAccountId": {
"type": "string",
"description": "The unique identifier for the billing account associated with the commitment."
},
"BillingAccountName": {
"type": ["string", "null"],
"description": "The display name for the billing account."
},
"ProviderName": {
"type": "string",
"description": "The name of the entity that made the commitment discount available."
}
},
"required": [
"CommitmentDiscountId",
"CommitmentDiscountCategory",
"CommitmentStartDate",
"CommitmentEndDate",
"BillingAccountId",
"ProviderName"
],
"additionalProperties": true
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/finops-foundation-contract-commitment-record"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.