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

# Drip SDK

Drip offers an SDK that allows projects to run Drip Pools with their own branding, as part of their own dApps.

As an example, existing projects can integrate a "Stake USDC/ETH" section next to their native token staking pool on their dApp, where their users can stake their stable assets to farm and claim the native project token, claim it, and then immediately stake them all on the same page.

Another example would be running customized launchpools directly on the project's native website to provide a smoother onboarding process for depositors and avoid confusion or friction coming from users seeing other launchpools as would be the case on the Drip dApp (Think of competing LBPs running at the same time on Fjord for example).

The SDK for this process is currently readily for any team setting up a Drip Pool.


---

# 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://drip.gitbook.io/drip-finance/drip-sdk.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.