> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/platform-administration/snyk-platform-subscription/snyk-platform-subscription-mechanics.md). # How the Snyk Platform Subscription works How the Snyk Platform Subscription works: credit balances, daily deduction, on-demand use, new capabilities, and the rate card in your contract The Snyk Platform Subscription is the default Snyk Enterprise plan. You purchase credits at the beginning of your subscription, valid for the full term of your contract. Credits carry entitlements for all capabilities across the platform and are fungible across capabilities. You consume credits from your balance based on your contracted rate card. Every order form that contains a subscription for credits includes a link to a rate card that describes how use of the platform translates into credit consumption. For details, see [Rate card and your contract](#rate-card-and-your-contract). Snyk deducts credits from your balance daily, based on the volume of billable events each day. You can use credits at any pace over the duration of a contract to accommodate natural ramping, seasonality, or growth. Unused credits remaining when a contract ends are non-refundable and do not automatically carry over to a renewal. To follow your consumption, visit [Track credit consumption](/platform-administration/snyk-platform-subscription/understanding-credit-consumption.md). If you exhaust your initial balance of credits, you can continue to use the platform on an on-demand basis. Snyk invoices on-demand consumption at the per-credit price in your contract. When Snyk introduces new platform capabilities as Generally Available, Snyk automatically adds them to your rate card. As a result, you gain immediate access to new platform functionality, and the credit-consumption mechanics stay transparent and documented. New capabilities always default to off in the [capability control panel](/platform-administration/snyk-platform-subscription/capability-control-panel.md), so a Tenant Admin must authorize them before they consume credits. ## Rate card and your contract Your rate card is the one linked in your order form. Every Enterprise order form that includes credits links a specific, versioned rate card, and that version governs your contract for its full term. Refer to it for the consumption rates and units of measure that apply to you. Snyk publishes the current rate card at [Credit-based billing policies](https://snyk.io/policies/credit-based-billing/). That page always shows the latest version, which can differ from the version linked in your order form. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.snyk.io/platform-administration/snyk-platform-subscription/snyk-platform-subscription-mechanics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.