> For the complete documentation index, see [llms.txt](https://docs.squads.so/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.squads.so/main/development/introduction/use-cases.md).

# Use Cases

Squads is a powerful primitive that enables a variety of use-cases related to self-custody and account abstraction. Here are few of the major use-cases for Squads' tools:

### **Configurable App Vaults**

Use Squads to custody funds associated with your app, and allow various stakeholders to have control over the flow of these funds. An example of this would be a crowdfunding app, where funds raised are custodied in Squads, with the fundraiser admins and members of the app team as members.

### **Custom User Interfaces**

Use the Squads v4 SDK to create a custom UI, built to your liking for your Squad. This allows for a bespoke smart account experience, and less dependency on Squads' official services. For reference, check out our [public UI](https://github.com/Squads-Protocol/squads-v4-public-ui).

### Squads Blinks

Build custom Solana actions and blockchain links (blinks) associated with a Squad that are shareable on a variety of websites like X.


---

# 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:

```
GET https://docs.squads.so/main/development/introduction/use-cases.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
