> 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/app-builder/operate.md).
# Operate
Monitor costs, acquisition, analytics, and app health after launch.
Deploying a financial application is the first step, not the last. Once it's live, the priority shifts from development to governance, fiscal transparency, and scale. **Operate** is the administrative control tower for your ecosystem of AI-driven tools.
In a production banking environment, every interaction carries a cost and every user journey requires attribution.
For account-wide governance and monitoring, use the [Control Center](/ai-workbench-qore/start-here/control-center.md).
## Usage and cost control
The **Usage & Cost Control** dashboard gives a high-fidelity view of how AI resources are consumed across your digital ecosystem — from a single Commercial Loan Portal to a suite of internal Compliance Agents.
**App build-time cost visibility.** App build-time cost visibility has been added, so you know what you're spending before you even publish.
For account-wide credit usage, spending limits, and alerts, use [Cost Control](/ai-workbench-qore/control-center/cost-control.md) in Control Center.
### Resource tracking
Live telemetry on credit and token consumption, rather than retrospective reporting.
* **Token-Level Visibility**: Monitor LLM token usage across providers (e.g., Vertex AI, Claude) to understand the exact cost of each automated interaction.
* **Credit Management:** Track platform credits in real time, whether you're on Pay-As-You-Go or a pre-allocated enterprise plan.
* **Automated Institutional Invoicing:** Detailed invoices break usage down so you can reconcile expenses or re-allocate costs to departments or branch locations.
{% hint style="info" %}
**Auto-unpublish on Dev/QA environments after 5 hours**
In line with our ongoing cost-control efforts, apps on Dev and QA environments will now auto-unpublish after 5 hours of inactivity.
{% endhint %}
### Budget optimization
Attribute costs to specific business outcomes.
* **Identify High-Consumption Assets:** See which apps or agents are most resource-intensive. If a Wealth Management Chatbot consumes more tokens than expected, refine its prompt or switch it to **Flash Mode** to improve unit economics.
* **Departmental Allocation:** Attribute usage to business units, enabling charge-back models where Commercial Lending and Retail Banking are billed only for the AI logic they use.
* **Budget Guardrails:** Set proactive alerts and thresholds so a pilot project stays within its quarterly budget — you're notified before usage hits critical levels.
## Analytics and referrals
Understanding where a high-value lead came from is essential for optimizing marketing spend and managing partner relationships. **Referral Tracking** monitors user acquisition with granular precision.
For unified engagement data across published apps, use [Observe](/ai-workbench-qore/control-center/observe.md) in Control Center. For one app's traffic, use [Analytics](/ai-workbench-qore/console/app-builder/analytics.md).
* **UTM-Based Referrals:** Track which campaigns, emails, or digital ads convert into active users.
* **Partner Link Attribution:** Assign unique referral codes to external partners — mortgage brokers, insurance agents, branch locations. When a user onboards via a partner link, the acquisition is permanently attributed to the correct source.
* **Conversion Insights:** Identify which referral channels drive the highest quality applications by tracking the path from click to submitted loan application.
* **Performance Auditing:** Review acquisition data to ensure marketing budget goes to the highest-performing channels.
* **Seamless Integration:** Referral data is captured at the point of entry and can be passed into your CRM or internal reporting systems through an agent's [API Call](/ai-workbench-qore/platform-resources/skill-library/api-call.md) skill.
## System health
Maintain visibility into platform stability and response times to ensure your deployment delivers the experience your brand promises.
For organization-wide dashboards across every app and agent, see [Monitoring & Performance Dashboards](/ai-workbench-qore/control-center/observe.md) under Governance. For a single agent's runtime behavior, see [Monitor](/ai-workbench-qore/console/agent-builder/monitor.md) in the Agent Builder.
For account-wide activity, model calls, and API requests, use [Observe](/ai-workbench-qore/control-center/observe.md) in Control Center.
***
{% columns %}
{% column width="83.33333333333334%" %}
Maintained by Abhishek Paul
AI-assisted, human-approved
{% endcolumn %}
{% column width="16.666666666666664%" %}
{% 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/app-builder/operate.md?ask=&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.
