> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/ai-workbench-qore/console/agent-builder/deploy.md).

# Deploy

Ship the agent into your product, safely.

**Deploy** is where the agent leaves the builder and becomes something your users can reach — embedded in an app, called from your backend, or packaged for another environment.

The pages here fall into two halves that belong together: how the agent gets *out* to your product, and the controls that decide what it may do once it is there. A deployed agent is reachable by people who never saw the builder, so the credential, domain, PII, and guardrail settings on this page are the boundary between "the agent can act" and "the agent can only act the way you intended."

## Getting the agent out

* [Export Agent](/ai-workbench-qore/console/agent-builder/deploy/export-agent.md) — Package an agent for reuse across environments.
* [Integrate Agent](/ai-workbench-qore/console/agent-builder/deploy/agent-integration.md) — Embed or call the agent from your product.

## Controlling what it can do

* [Access & Security](/ai-workbench-qore/console/agent-builder/deploy/authentication.md) — Create access keys and choose where the widget may run.
* [Authentication](/ai-workbench-qore/console/agent-builder/deploy/authentication-1.md) — Verify who is calling the agent through your identity provider.
* [PII Tokenization](/ai-workbench-qore/console/agent-builder/deploy/guardrails/pii-masking.md) — Protect sensitive user and business data.
* [Guardrails (Beta)](/ai-workbench-qore/console/agent-builder/deploy/guardrails.md) — Define safety and compliance controls.

***

Once the agent is live, [Monitor](/ai-workbench-qore/console/agent-builder/monitor.md) is where you watch it and feed corrections back into [Build](/ai-workbench-qore/console/agent-builder/build.md).

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% endcolumn %}
{% endcolumns %}


---

# 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.uptiq.ai/ai-workbench-qore/console/agent-builder/deploy.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.