> 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/enterprise-contract-types.md).

# Enterprise contract types

Snyk offers two licensing structures for Enterprise plans. The legacy structure is SKU-based: each SKU licenses a specific capability, priced on the annual high-watermark volume of licenses you procure. You can contract SKUs independently or as bundles that appear as one order-form line item while covering several capabilities. For the usage settings that apply to this structure, visit [SKU-based licensing usage settings](https://docs.snyk.io/platform-administration/snyk-platform-subscription/legacy-plans/usage-settings.md).

The current structure is the [Snyk Platform Subscription](https://docs.snyk.io/platform-administration/snyk-platform-subscription/snyk-platform-subscription-mechanics.md), a consumption-based license. You pre-purchase a balance of credits valid for your full contract term and draw it down as you use capabilities across the platform.

To see which structure applies to each capability in your plan, visit [View your plan](https://docs.snyk.io/platform-administration/snyk-platform-subscription/viewing-your-plan.md).


---

# 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/enterprise-contract-types.md?ask=<question>&goal=<user_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.
