> For the complete documentation index, see [llms.txt](https://developer.gospace.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.gospace.com/start-building/setup-your-development-environment.md).

# Setup your development environment

Learn how to install and configure the gospace SDKs, set up your environment variables, and prepare your system for building and running API integrations.

{% tabs %}
{% tab title="Node.js" %}

### Prerequisites

* Node.js v18 LTS or newer
* npm v9+
* A valid gospace API key

### 1. Install Node.js and npm

Check your version:

```bash
node -v
npm -v
```

If you need to upgrade, download from [nodejs.org](https://nodejs.org/) or use a version manager:

```bash
nvm install 18
nvm use 18
```

### 2. Create a New Project

```bash
mkdir gospace-dev
cd gospace-dev
npm init -y
```

### 3. Install the gospace AI SDK

```bash
npm install @gospace-ai/api
```

### 4. Store Your API Key Securely

```bash
npm install dotenv
```

Create `.env`:

```env
GOSPACE_API_KEY=your_api_key_here
```

Load it in your code:

```ts
import "dotenv/config";
import GospaceAI from "@gospace-ai/api";

const gospace = new GospaceAI(process.env.GOSPACE_API_KEY!);
```

{% endtab %}
{% endtabs %}


---

# 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://developer.gospace.com/start-building/setup-your-development-environment.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.