> For the complete documentation index, see [llms.txt](https://docs.solo-pad.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solo-pad.com/platform-overview/solopad-introduction.md).

# SoloPad Introduction

<figure><img src="/files/4NJ3Mble0vDrWwMa6Ppd" alt="" width="375"><figcaption></figcaption></figure>

SoloPad is the first self-service crypto launchpad that creates direct connections between emerging cryptocurrency projects and premier content creators. Our software platform does not charge any commission, setting us apart from typical marketing solutions that typically charge double digit commission rates. Designed by experienced crypto content creators, SoloPad leverages a deep understanding of the promotional dynamics within the crypto sphere to create a direct source of reliable influencers for projects while also enhancing the creator experience with rewarding opportunities. By focusing on simple pricing structures and dealflow transparency, SoloPad aims to disrupt and streamline the world of promotional collaborations in the cryptocurrency industry.


---

# 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://docs.solo-pad.com/platform-overview/solopad-introduction.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.
