# Active Web Proxy
This scenario is largely the same as the API Transformation scenario from an installation perspective. The only difference is that **the requests in this scenario comes from end users rather than server applications** and **the target for the requests are existing web applications or Software** as a Service applications.
Graph
This scenario lends itself to a myriad of use cases:
* Digital transformation, where an existing application *(often beyond the control of the business)* is functionally enhanced, without the explicit need for the existing application being aware of these changes
* Bot management, where the space.vars.X\_Agent\_Name\_Single detects bots and adds policies for how those bots are able to access the underlying application
* Robotic process automation where requests to the existing application results in data also being entered into secondary systems
* Orchestration of multi existing applications that are joined together to form a new experience
* … and many more
This scenario is especially useful for regaining control of web applications that are otherwise difficult, expensive or impossible to change
---
# Agent Instructions: 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:
```
GET https://docs.tomorrowx.com/cap/product-reference/architectural-scenarios/active-web-proxy.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.