# Getting Started

Welcome to the Laevitas Api GateWay v1.0 documentation! This guide will help you get up and running in no time.

## Introduction

Laevitas Api GateWay v1.0 is a powerful and flexible gateway designed to streamline your API requests, manage traffic, and ensure optimal performance. Whether you're a developer or an enthusiast, this guide will provide you with all the necessary steps to start using our gateway.

## Prerequisites

Before you begin, ensure you have the following:

* An active Laevitas account.
* **API key (Enterprise Subscription Required)**: You can obtain this from your dashboard. Please note that access to the API key requires an enterprise subscription.
* Basic knowledge of RESTful APIs.

## Setting Up

1. **Register or Login**:
   * If you haven't already, [register](https://app.laevitas.ch/auth/register) for a Laevitas account or [login](https://app.laevitas.ch/auth) if you have one.
2. **Obtain your API Key**:
   * Navigate to your dashboard.
   * Under the 'API' section, generate a new API key. Remember, you need an enterprise subscription to access the API key.
3. **Install SDK (Optional)**:
   * If you're using our SDK, install it using the package manager of your choice:

     ```bash
     npm install laevitas-sdk
     ```

## Making Your First Request

With your enterprise API key in hand, you're ready to make your first request:

```bash
curl -X GET 'https://api.laevitas.com/analytics/futures/instruments' -H 'apikey: YOUR_API_KEY'
```


---

# Agent Instructions: 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:

```
GET https://docs.laevitas.ch/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.