> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/use-groundcover/agent-mode/requirements.md).

# Requirements & Compatibility

Agent Mode requires access to cloud-based LLM services for inference. This page covers which deployment types support Agent Mode and what setup is needed.

## Supported Deployments

| Deployment Type                 | Agent Mode | Setup Required                                                                                              |
| ------------------------------- | ---------- | ----------------------------------------------------------------------------------------------------------- |
| **groundcover Cloud**           | Yes        | None                                                                                                        |
| **BYOC AWS**                    | Yes        | None                                                                                                        |
| **BYOC GCP**                    | Yes        | [Enable models in Vertex AI](/architecture/byoc/setup-byoc-with-gcp/enable-ai-models-for-agent-mode.md)     |
| **BYOC Azure**                  | Yes        | None ([what gets provisioned](/architecture/byoc/setup-byoc-with-azure/enable-ai-models-for-agent-mode.md)) |
| **On-premises (AWS/GCP/Azure)** | Yes        | Use your own Anthropic API key, or contact your account team for a native cloud provider                    |
| **On-premises (other)**         | Yes        | Use your own Anthropic API key                                                                              |

{% hint style="info" %}
**No cost until you use it.** Agent Mode is enabled by default on groundcover Cloud and BYOC deployments once provisioning completes, and LLM inference costs are incurred only when users start using the Agent. If you use your own Anthropic API key, Anthropic bills the usage to your account. GCP BYOC requires a manual setup step because Google Cloud requires customers to explicitly approve third-party Anthropic models in Vertex AI Model Garden before they can be invoked. AWS Bedrock and Microsoft Foundry have no equivalent gate.
{% endhint %}

For on-premises deployments on AWS, GCP, or Azure, groundcover can provision the native LLM service: AWS Bedrock, Google Cloud Vertex AI, or Microsoft Foundry. You can also use a direct Anthropic API key on any supported backend. On-premises deployments on other infrastructure use the direct Anthropic API. All configurations require outbound access to the selected LLM provider.

## Anthropic API key

Agent Mode supports using your own Anthropic API key for inference on any backend where AI features are available. This is useful when you want usage billed through your Anthropic account or when a native cloud-provider LLM service is not available for your deployment.

Workspace administrators configure the key separately for each backend. Inference requests are sent directly to Anthropic after the key is configured. See [Configuring Settings](/use-groundcover/agent-mode/configuring-settings.md#anthropic-api-key) for the self-service setup and key rotation steps.

## GCP BYOC setup

GCP BYOC deployments require manually enabling the Anthropic Claude models in your project's Vertex AI Model Garden before Agent Mode will work. See [Enable AI models for Agent Mode](/architecture/byoc/setup-byoc-with-gcp/enable-ai-models-for-agent-mode.md) for step-by-step instructions.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.groundcover.com/use-groundcover/agent-mode/requirements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.