AcademicFix Studio 1.1.1 · Connection guide
Connect an OpenAI API key to Studio and limit spending
The OpenAI API is an optional connection. Identify the project that owns your key and set its spending control before running a real response test in Studio.
Content checked: 16 October 2026 · AcademicFix Editorial Team
First choose the right connection route
Studio can also use an eligible ChatGPT account or local Codex session. Those routes do not require an OpenAI API key. Key-based use follows the separate API account’s billing and usage terms; Studio includes no model subscription or API credit.
Create the key in the OpenAI Platform
- Open the official API keys page and select the project you intend to use. A separate Studio project makes usage and spending easier to inspect.
- Create a standard API key in that project. If your account offers permission scopes, grant only the access needed. Do not use an Admin API key for the Studio connection.
- Keep the key secret. Do not put passwords, keys or tokens in Studio chat, a research document, screenshots or feedback.
Source: OpenAI API quickstart.
Separate alerts from enforced spend limits
An OpenAI spend alert sends a notification; it does not stop API requests. To enforce a monthly cap, turn on “Enforce a hard limit” for the project or organization. This control lives in the API Platform; Studio’s Usage view is not a substitute.
- In the OpenAI Platform, open the intended project’s settings and Limits.
- Under Spend, choose Edit spend limit and enter the monthly amount.
- Enable Enforce a hard limit and save. You can also add a spend alert at a lower threshold.
- Monitor project spending in the OpenAI Platform; review the limit when models or usage volume change.
Source: OpenAI spend limits · API error codes.
Test the connection in Studio
- Open Models in Studio and choose the OpenAI preset under the optional API route. Enter the key only in the connection field.
- Refresh the model list and choose a model your account can access. Appearing in the list is not proof of a working response.
- Start the short response test yourself. It can make a billable API request; check which model answered and the test time.
- Assign the verified model to the intended agents or team. Separate agent calls using the same API project can contribute to that project’s spending.
By default, Studio keeps an API key in memory while the app is open. Remembering it is optional and uses Windows protection for the current user; you can forget a remembered key from the connection.
Studio models and connections guide · Key storage explanation.
If something fails, check four separate points
- Whether the key belongs to the intended OpenAI project and has the needed permissions.
- Whether the selected model is available to the account and actually answers the short test.
- Current project and organization spend, credit and limit state in the OpenAI Platform.
- For a 429, the actual error code: spend caps, usage limits and rate limits are different conditions.
Studio does not automatically switch to a paid API when a subscription request fails. A connection that worked earlier does not prove current access.
Sources and scope
The OpenAI dashboard steps follow official documentation checked on 16 October 2026; screens can vary with account permissions and later interface changes. Studio steps follow the 1.1.1 user guide. This article makes no fixed per-task cost or zero-cost claim.