> For the complete documentation index, see [llms.txt](https://docs.replicacyber.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.replicacyber.com/readme.md).
# Replica Documentation
Deploy secure isolated labs and workspaces in seconds — protected by our patented anonymous attack surface, enterprise observability, and comprehensive data controls.
{% columns %}
{% column valign="middle" %}
### Get started instantly
Deploy secure isolated labs and workspaces in seconds — protected by our patented anonymous attack surface, enterprise observability, and comprehensive data controls.
No guesswork, no complexity — just access to the tools and data you need.
User Guide
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
{% columns %}
{% column width="50%" %}
{% endcolumn %}
{% column width="50%" valign="middle" %}
### Learn about Replica's developer features
Read guides, watch tutorials, and learn more about working with Replica's developer features, APIs, and workflow automation with scheduled Jobs.
Developer GuideAPI Reference
{% endcolumn %}
{% endcolumns %}
Instant. Isolated. Frictionless.
Replica enables high-stakes operations with uncompromising security, seamless collaboration, and full compliance, protecting critical assets while ensuring complete control.
Cover image
Administration Guide
Learn how to configure the Replica platform so users get the most out of their experience.
---
# 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.replicacyber.com/readme.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.
