> For the complete documentation index, see [llms.txt](https://docs.multichain.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.multichain.info/start/creating-a-project.md).

# Create a Project

**Step 1:** Create a project by selecting the "Create Project" button on the "Dashboard" page.

![](/files/-MkNY-zrdU4FtKVIt-bF)

The project will automatically be assigned with the API Key and Secret Key which you can view as seen in the image below:

![Click "View Keys" to retrieve your project's API Key and Secret Key](/files/-MkNXhuU1aAJmtxNI9r6)

We understand that in many occasions Multichain account owners are usually project managers and limiting access for programmers to project settings/wallet is crucial. To mitigate this, programmers are only **required to change the API Key and Secret Key after app integration and before going live**.

![Replace development keys with Project Owner's keys after integration/setup](/files/-MkIu_1mWlqjmc1hswZ4)

{% hint style="info" %}
Each project has a unique [masterwallet](https://docs.multichain.info/faq/masterwallet-vs-subwallet) and dedicated project configurations. *(Each project should be dedicated to a single product)*
{% 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://docs.multichain.info/start/creating-a-project.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.