> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/help-center/guaranteed-commitments/premiums-and-terms.md).

# Premiums and Term Lengths

Archera Guaranteed Commitments have two variable components — a **term length** and a **premium** — that are inversely related. The longer the term length, the lower the premium, and vice versa: shorter term lengths have higher premiums.

The **Guaranteed Commitment Premium** is the difference between the standard Savings Rate of the underlying standard RI/SP and the net savings rate of the Guaranteed Commitment. You can see the Guaranteed Commitment premiums on your invoice page.

Keep in mind, Guaranteed Commitment premiums are only assessed on **realized** savings. Meaning — if for some reason you can't use the underlying infrastructure, you aren't responsible for the premium.

## Related Resources

* [How Does Guaranteed Commitment Pricing Work?](/help-center/guaranteed-commitments/pricing.md)
* [What are Guaranteed Commitment allowances?](/help-center/guaranteed-commitments/allowances.md)
* [What are my Guaranteed Commitment billing options if I'm still on AWS Credits?](/help-center/guaranteed-commitments/billing-options-aws-credits.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.archera.ai/help-center/guaranteed-commitments/premiums-and-terms.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.