> For the complete documentation index, see [llms.txt](https://developer.fotokite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.fotokite.com/~/changes/46/early-access-program.md).

# Early Access Program

The goal of this Early Access Program (EAP) is to test and refine the Fotokite API by gathering feedback, ensuring it becomes a robust and reliable interface that meets the needs and use cases of our partners.

## Who is the EAP suitable for? <a href="#who-is-the-eap-suitable-for" id="who-is-the-eap-suitable-for"></a>

The EAP is intended for Fotokite partners who plan to use the Fotokite API in the future to build their own integrations and want to contribute to shaping the API during its early development stages.

### How is the EAP structured? <a href="#how-is-the-eap-structured" id="how-is-the-eap-structured"></a>

The Fotokite API is released through a three-stage process: alpha, beta, and production. Details and changes for each release will be communicated in advance through the designated communication channels.&#x20;

During the alpha and beta phases, the API may undergo changes, and building production-ready applications during this time is strongly discouraged.

Throughout these early phases, we will provide basic onboarding documentation and code examples to support development and testing.

<figure><img src="https://3669484394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXUDGlNkSLzd9Nbig1oF3%2Fuploads%2FCMQMxwLy33nPRNMkaXqi%2Feap-timeline.png?alt=media&amp;token=08613ac1-f0ba-4231-8142-1e9f45110ac3" alt=""><figcaption></figcaption></figure>

**Alpha**

Timeline: Mid-July - Mid-September

Release: Mid-July

Features:

* The API specification
* Video streams
* Information about the system (name etc.)
* Telemetry data (flight altitude, orientation of the drone, battery status)
* System status
* Take-off, flying, landing
* Rotate the camera
* Receive notifications and error messages from the system

**Beta**

Timeline: Mid-September - December

Release: Mid-September

* Authentication
* Telemetry data (GPS)
* Information on the color camera and thermal imaging camera
* Camera zoom
* Change color scheme for thermal imaging camera
* System software version

**Production**

Release: December

* Start and stop video recording
* Retrieve recorded videos
* Encryption
* Remote ID

## Risks or Limitations <a href="#risks-or-limitations" id="risks-or-limitations"></a>

* Please note that our release dates are subject to change and cannot be guaranteed.
* As part of the Early Access program, content and listed features are subject to change and may be modified in scope.
* While we value all feedback, we may not be able to accommodate every request and must act in the best interest of our partners and overall project goals.

### Support <a href="#support" id="support"></a>

Support requests and API specific issues can be addressed directly to our development team via the communication channels provided.

System support, independent of the API, is submitted to our support team via regular support requests.


---

# 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.fotokite.com/~/changes/46/early-access-program.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.