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

# Integration

Integration with RockSolid is a straightforward process. The steps involved depend on the style of integration:

1. Link only
2. White label / 'Powered by'
3. Fully Hosted

**Link only**

Each RockSolid vault comes with a url. For example the RockSolid rETH Vault is accessible at <https://app.rocksolid.network/vaults/0x936facdf10c8c36294e7b9d28345255539d81bc7>&#x20;

All functionality, such as deposit, withdraw and view holdings are available there.

**White label / Powered by**

RockSolid vaults are designed to be fully integrated into your front-end, such as a liquid staking protocol or a centralized exchange "earn" product. This let's users stay in your website or app with the familiar UI, but still get all the benefits of a RockSolid vault. See the [Rocket Pool integration](https://stake.rocketpool.net/rocksolid/vault/deposit) for an example.

You will interact with our [Smart Contracts](https://docs.rocksolid.network/integration/smart-contracts.md) and [API](https://docs.rocksolid.network/integration/api.md) for this style of integration.

**Fully Hosted**

The entire RockSolid app can be themed and hosted by RockSolid, but accessed from your domain. For example, **<https://vault.protocol.xyz>.** Contact us at <hello@rocksolid.network> for more information.&#x20;


---

# 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.rocksolid.network/integration.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.
