> For the complete documentation index, see [llms.txt](https://dev.ropo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.ropo.com/readme.md).

# Developer Platform

Welcome to your team’s developer platform

<h2 align="center">Ropo Developer Portal</h2>

<p align="center"></p>

<p align="center">Welcome to the Ropo One® Developer Portal – your go-to space for technical resources that help you connect systems, automate workflows, and enhance the way you use our solutions. Here you’ll find clear API documentation, integration guides, and technical references to support you through every step of your development or implementation journey. </p>

<p align="center">This portal is designed for our customers and the technical teams who support them, offering everything you need to get started quickly and make the most of Ropo One’s capabilities. </p>

<p align="center"></p>

<p align="center"><img src="https://2882741421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMgm9UFMz3YzTNO6EFQm7%2Fuploads%2Fqt1vcYOTHqejGzlhNk3C%2FFrame%20593.png?alt=media&amp;token=6b967e1c-f4ae-4cd6-8fcd-9c2c54f9c165" alt=""></p>

<p align="center"></p>

{% columns %}
{% column %}
{% embed url="<https://ropo.com/>" %}
{% endcolumn %}

{% column %}
{% embed url="<https://status.ropo.com/>" %}

{% 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://dev.ropo.com/readme.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.