> 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/legacy-plans.md).

# Legacy plans

Legacy Snyk Enterprise plans and licensing that predate the Snyk Platform Subscription: the Snyk Platform Access plan and SKU-based licensing

{% hint style="warning" %}
The pages in this section cover legacy Enterprise plans. The Snyk Platform Subscription is the default Snyk Enterprise plan. For details, visit [How the Snyk Platform Subscription works](https://docs.snyk.io/platform-administration/snyk-platform-subscription/snyk-platform-subscription-mechanics.md).
{% endhint %}

Use these pages if your contract includes a plan or licensing structure that predates the Snyk Platform Subscription:

* [Snyk Platform Access plan](https://docs.snyk.io/platform-administration/snyk-platform-subscription/legacy-plans/credits-for-the-snyk-platform-access-plan.md): a test-based consumption plan for Snyk Code, Snyk Open Source, Snyk Container, and Snyk IaC. The plan reached end of sale in January 2026.
* [SKU-based licensing usage settings](https://docs.snyk.io/platform-administration/snyk-platform-subscription/legacy-plans/usage-settings.md): how to view test usage and contributing developer counts for capabilities licensed through SKUs.


---

# 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/legacy-plans.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.
