> For the complete documentation index, see [llms.txt](https://docs.kiln.fi/v1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiln.fi/v1/integrations/custody-platforms/stake-from-anchorage.md).

# Stake from Anchorage

{% hint style="warning" %}
Kiln is a non-custodial staking provider. As a customer and owner of your assets, **it is YOUR responsibility to check and verify all the transactions you are signing**. While Kiln provides tooling to help you interact with your stakes (web applications, APIs), **Kiln is not responsible for the transactions that you sign.**
{% endhint %}

Anchorage supports staking on all the below protocols, which are also supported by Kiln. To stake with Kiln, select the Kiln operator in the Anchorage UI or enter the Kiln validator address as found on this page: 

{% content-ref url="/pages/sFgbc3zbAPcdznwHcXQk" %}
[Protocols](/v1/kiln-products/validators/protocols.md)
{% endcontent-ref %}

| Asset             | Stake via UI |
| ----------------- | ------------ |
| Aptos (APT)       | ✅            |
| Cosmos Hub (ATOM) | ✅            |
| DyDx (DYDX)       | ✅            |
| Ethereum (ETH)    | Get in touch |
| Osmosis (OSMO)    | ✅            |
| Sei (SEI)         | ✅            |
| Solana (SOL)      | ✅            |
| Sui (SUI)         | ✅            |

Note, Anchorage also supports staking on the following protocols which are not yet supported by Kiln: Axelar (AXL), Agoric (BLD), Celo (CELO). If you'd like to stake these assets you hold in Anchorage, please get in touch with us.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kiln.fi/v1/integrations/custody-platforms/stake-from-anchorage.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 `build a script that syncs our docs to a CMS` 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.