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

# Welcome to Impossible Finance

Glad to have you here!

## What is Impossible Finance?

[Impossible Finance](https://impossible.finance/) is the go-to crypto investment platform that empowers you with high-quality, fair and accessible crypto opportunities

## What do we do?

#### For Users

If you are a user, we aim to help you learn & invest in new & high quality crypto projects using our Launchpad product.

#### For Projects

If you are a project, we aim to provide you guidance & insights, easing the complex process of starting your own crypto project & launching an IDO. 

### Intro Video

{% hint style="info" %}
Got 2 minutes? Check out a video overview of our product 
{% endhint %}

{% embed url="<https://youtu.be/goKf7DaVDuc>" %}


---

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

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

```
GET https://impossible.gitbook.io/impossible-finance-faq/start-here/welcome-to-impossible-finance.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 `automate deployments from our CI pipeline` 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.