Obtain an OpenAI API Key for TEDI
Use this guide to create an OpenAI API key, then paste it into TEDI under Models → Providers . Vendor console labels can change; use the official OpenAI Platform if a menu name differs.
Before you begin
- Access to an OpenAI Platform account (or permission to create one for your company).
- Billing set up on the Platform account when required for API usage (ChatGPT Plus alone does not replace API billing).
- TEDI installed on the machine where you will paste the key.
Step 1: Open OpenAI Platform
- Go to https://platform.openai.com .
- Sign in or create an account.
Note: The developer Platform is separate from the consumer ChatGPT website. You need a Platform API key for TEDI.
Step 2: Confirm billing (when prompted)
- In Platform, open billing / payment settings for your organization or project.
- Add a payment method or prepaid credits if the Platform requires it before keys can call models.
- Optionally set a spending limit so unexpected usage cannot run away.
Step 3: Create an API key
- Open the API keys page: https://platform.openai.com/api-keys (or API keys in the Platform sidebar).
- Select Create new secret key (wording may vary slightly).
- Give the key a clear name (for example,
TEDI-Vista-PC). - Choose the project / permissions your admin expects (project-scoped keys are typical).
- Create the key.
Step 4: Copy the key immediately
- OpenAI shows the full secret once . Copy it before closing the dialog.
- Store a backup in your password manager if you need to re-enter it later.
- If you lose the value, revoke or delete the old key and create a new one.
Step 5: Paste the key into TEDI
- Open TEDI → Models → Providers .
- Under Add provider , choose OpenAI , then Add (skip if OpenAI is already listed).
- Expand the OpenAI card.
- Paste the key into API key .
- Enable at least one model, set Default model for this provider , then Save .
- In Active selection , set Active provider to OpenAI and choose an Active model .
Full TEDI UI walkthrough: Configure LLM Providers in TEDI .
Security checklist
- Do not email the key or paste it into a support ticket.
- Do not commit the key to source control or shared docs.
- If the key may have been exposed, revoke it in Platform and create a replacement.