> 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/partners/readme.md).

# Archera Partner Wiki

Welcome and thanks for choosing to partner with Archera. Our mission is to reduce the rate customers pay for cloud services. We achieve this by offering **Insured Commitments** on AWS, Azure, and GCP.

If you have any questions, feel free to send a message in your shared Slack or Teams channel with Archera or email us at <partnersupport@archera.ai>.

You can check out our API documentation at [docs.archera.ai/api-reference](https://docs.archera.ai/api-reference).

#### Where to start?

* Check out the [Core Concepts](/partners/archera-overview/core-concepts.md) & [Insured Commitments](/partners/archera-overview/insured-commitments.md) pages if you're new to Archera or would like a refresher.
* If you're a Sales professional and want to quickly get up to speed on Archera's value proposition, get access to key discovery questions, find follow-up collateral, and more, check out the [Sales Quickstart Guide](/partners/sales-quickstart/sales-quickstart-guide.md).
* Check out the [List of Common Scenarios & Questions](/partners/customer-success-quickstart/list-of-common-scenarios-and-questions.md) for frequently asked questions about the Archera platform.


---

# 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/partners/readme.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.