> For the complete documentation index, see [llms.txt](https://docs.meeco.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meeco.me/latest/getting-started/setting-up.md).

# Setting Up

### Subscription Keys

Firstly, a developer must sign up at the [Meeco Developer Portal](http://dev.meeco.me/).

After following the signup procedure, confirming your account via an email and finally logging in, select "Get API Keys" from the home page.

Give your subscription a name, read through and agree to the Terms of Use, and subscribe.

This will generate the Primary and Secondary keys that are required to make requests in the developer portal.

**Please note that the keys need to be approved by us, and therefore may not be ready for immediate use**

The Primary key will be added to the `Meeco-Subscription-Key` header in all requests to the portal.

Once the subscription keys have been activated, (you will receive an email telling you once it is active) you can begin to use them to make requests.

Now, jump into the [Quickstart section](/latest/getting-started/quickstart.md) and follow along to create your first User and Vault item.


---

# 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.meeco.me/latest/getting-started/setting-up.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.