> For the complete documentation index, see [llms.txt](https://sdk.chorus.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sdk.chorus.one/our-products/chorus-one-widget.md).

# Chorus One Widget

The Chorus One Widget is a ready to integrate product built on iFrame that can be easily embed into existing website or app, allowing the end users to connect wallet and start earning rewards with Chorus One.

The Widget is built for platforms that want to do more than just offer staking — it’s designed to deliver **trusted, institutional-grade staking and rewards** with a seamless user experience. Whether you are a wallet, custodian, asset management or trading platform, the widget gives you the tools to engage users, grow loyalty, and unlock monetization — all backed by one of the most established validators in the industry.

Unlike generic earn widgets, the Chorus One Widget combines **deep protocol expertise** with a **fully customizable interface**, allowing partners to offer staking solutions that align perfectly with their brand and user base.

With the Chorus One Widget, platforms can:

* **Launch staking without code**: Deliver new staking services instantly, without diverting engineering resources.
* **Integrate flexibly**: Deploy as a branded standalone dApp or embed seamlessly into existing web or mobile applications.
* **Offer a complete staking journey**: From discovering staking opportunities to connecting wallets, depositing assets and monitoring detailed, real-time reward analytics — all in one consistent, transparent experience.
* **Leverage proven security & credibility**: Chorus One secures billions in assets and partners with leading institutions — providing confidence and reliability your users can trust.

By partnering with Chorus One, platforms don’t just add staking — they gain access to **world-class infrastructure, deep ecosystem relationships, and the assurance of a specialist who has been at the forefront of staking since day one.**

### The Chorus One Widget Advantages

#### **Branded Staking Experience**

Use the Chorus One Widget Builder to fully align the staking interface with your brand. Apply your own colors, fonts, and logos to deliver a seamless, on-brand user experience.

#### Broad Compatibility

With support for multiple networks and a wide range of wallets, the Chorus One Widget unlocks diverse staking and yield options — giving your users seamless access to the best earning opportunities in one unified interface.

#### **Low/No-Code Integration**

Integrate staking functionality quickly, even without a dedicated engineering team. The Chorus One Widget is lightweight, framework-agnostic, and can be embedded into any platform — from enterprise systems to no-code tools.

{% hint style="info" %}
***Currently Supported Networks Through Widget:***

* *Ethereum*
* *Solana*
* *TON*
* *USDC (Coming Soon)*
* *Monad*
* *Akash*
* *Atom*
* *Axelar*
* *Band*
* *Celestia*
* *dYdX*
* *Kava*
* *Sei*
  {% endhint %}


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sdk.chorus.one/our-products/chorus-one-widget.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.