# Getting API Keys

### API Keys

#### OPENAI

The first thing you will need is an OpenAI API key, this can be generated from the OpenAI platform:\
<https://platform.openai.com/settings/organization/api-keys>

{% hint style="info" %}
V1.0.0 only supports OpenAI model
{% endhint %}

#### SCENARIO

For now we will leverage the use of [Scenario](https://www.scenario.com/) to do the heavy lifting. In our case [Scenario](https://www.scenario.com/) will train a lora based on our images and generate new content.\
\
To use Scenario you will have to [signup](https://www.scenario.com/), the cost is approx. $15/m, giving you 1500 creative units. Using the PLAYER1 framework an image will cost 10 units. However note that majority of the credits will be used when training a model.\
\
Once you're signed up you can generate an api key by following the instructions here:\
<https://docs.scenario.com/docs/get-api-key>

{% hint style="info" %}
We are currently working on version 2.0.0, where you will be able to use the PLAYER1 token to train models and generate images. This will be a lot more cheaper to run than Scenario
{% endhint %}


---

# 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://player1.gitbook.io/player1-docs/getting-started/getting-api-keys.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.