> 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/credits-for-the-snyk-platform-access-plan.md).

# Credits for the Snyk Platform Access plan

{% hint style="warning" %}
You can no longer purchase or enroll in this plan.
{% endhint %}

The Snyk Platform Access plan is now end-of-sale (as of January 2026). It is a trial of test-based consumption pricing that unifies Snyk Code, Open Source, Container, and IaC under a single license. Under this model, you pay a flat per-developer platform access fee and an up-front commitment of credits to consume for testing across Snyk Code, Open Source, Container, and IaC capabilities.

This is a different Enterprise plan from the Snyk Platform Subscription. For more information, see [Enterprise contract types](/platform-administration/snyk-platform-subscription/enterprise-contract-types.md). For more information on how credits work under the Snyk Platform Access plan, visit [Snyk Platform Access policies](https://snyk.io/policies/definition-of-snyk-platform-access/).


---

# 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/credits-for-the-snyk-platform-access-plan.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.