> For the complete documentation index, see [llms.txt](https://docs.probe.splx.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.probe.splx.ai/settings/platform-settings/organization-settings/subscription.md).

# Subscription

All the information regarding your subscription is located on this page.

Navigate to the [**Organization Setting**](/settings/platform-settings/organization-settings.md) and select the **Subscription** from the navigation bar on the left side to show your subscription details.

* **Current Credits Balance** - Displays the number of remaining credits available for use across the organization.
* **Subscription Plan** - Indicates the active subscription tier assigned to the organization.
* **Billing Cycle** - Shows how often the subscription is billed (e.g., monthly or annually).
* **Credits Per Renewal** - Specifies how many credits are added to the account at each billing renewal.
* **Upcoming Credits Renewal Date** - The date on which the next credit allocation will occur.
* **Subscription Expiration Date -** The date when the current subscription term ends.

Additionally, you can allocate your subscription credits to any workspace from the [**Credit Allocation**](/settings/platform-settings/organization-settings/credit-allocation.md) page.


---

# 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.probe.splx.ai/settings/platform-settings/organization-settings/subscription.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.