1. Create your organization and select a project
Open the dashboard and choose Create an organization. Enter your organization name and slug, your name, email, and password, and complete the terms acknowledgement and registration check. Aixy creates your personal account, Owner membership, and a default project. If you already have an Aixy account, use its current password to create another organization. If you received an invitation, accept it and use the project assigned by your administrator. For an existing organization, sign in with your email and password or passkey. Aixy opens your sole organization directly or asks you to choose when you belong to several. Use Switch organization from the account menu to change where you work. Select the project in the sidebar. To create a separate application or environment, open Projects from the account menu and choose Create project. Use a recognizable name such asDevelopment, then select it in the sidebar.
2. Connect a model provider
As an Owner, Org admin, or administrator of the selected project:- Open Providers → Add provider and choose OpenAI.
- Enter your provider’s API key. This is the key from your OpenAI account, not an Aixy key.
- Use Test connection to inspect authentication and model-catalog access.
- Save the connection.
3. Choose an available model
Open Models with the same project selected. Find a conversational model on your connected provider and check that it is allowed. Copy its full provider-qualified ID, for exampleopenai/gpt-4.1-mini. Use an ID available to your account throughout this guide.
Project users can select approved models; an administrator manages model access.
Models and access explains catalog information and inherited restrictions.
4. Create an Aixy project API key
Open API keys from the account menu and select Create API key:- Name the key, for example
Development quickstart. - Select the project you configured. Optionally record the workload and team cost center.
- Choose a lifetime and create the key.
- Copy the secret from Store the new secret into a protected local environment or secret store. It is shown once.
/v1.
Keep the key out of source control and browser application code.
You can confirm what this key can discover before making a model call:
id from that list.
5. Try the model in Playground
Open Playground, choose your model, and open Request settings to select the new API key and Chat Completions protocol. Send a short message such asReply with connected.
Playground uses the selected key’s project, permissions, and budgets. A successful reply confirms
that the provider account can execute this request. If a pricing notice appears under a hard
budget, follow the pricing setup and use
Recheck prices before sending.
6. Send a request from your application
Run one of these examples from a trusted local or server environment. The Python example uses only the standard library; the JavaScript example runs in Node.js with built-infetch.
choices[0].message.content. Save the
x-request-id response header to find this exact request in the dashboard.
7. Verify usage and apply your first controls
Open Activity, search for the request ID, and inspect its provider, model, status, timing, tokens, and cost evidence. Metadata arrives asynchronously; refresh after a short delay. Use Usage for aggregate traffic and Cost control for attributed spend and budgets. Before expanding usage:- Configure model access for the models the project should use.
- Review pricing and create a budget.
- Test guardrails with representative input.
- Connect your editor or coding agent, or create a routing model for a stable application-facing model name.
If the first request fails
See Activity for request-level diagnosis and Authentication
for key lifecycle controls.