Apply for a getapi.one API Key

This guide follows the getapi.one console flow. API Keys are not shown only once: after creation, you can still copy and manage them from the API Keys list.

Quick links

• Official website
• getapi.one sign-up and login guide
• API Key overview

Before you start

• Finish signing up and signing in to getapi.one. If you have not done that yet, read the getapi.one sign-up and login guide first.
• Confirm that you can open the console normally.
• Make sure the account has usable balance or an active plan.
• Prepare a private place to store the API Key, such as an environment variable, local config file, or Agent settings page.

Open the API Keys page

In the getapi.one console, open the left sidebar and select API Keys. If no key exists yet, the page will show an empty state and a create button in the upper-right corner.

Create an API Key

1. Select “+ Create API Key”.
2. Enter a recognizable name for the key.
3. Select a group if your account uses groups.
4. Set the expiration time and quantity as needed. For a long-term Agent key, you can keep it non-expiring.
5. Keep unlimited quota enabled, or adjust quota settings if you want to limit spending.
6. Open advanced settings only when you need access restrictions, then select “Save changes”.

After the key is created

After creation succeeds, return to the API Keys list. The key row will show its name, masked key, group, status, and actions. getapi.one keeps the key available in the list, so you can copy or manage it later instead of relying on a one-time display.

Agent configuration address

When configuring an Agent, keep the getapi.one API Key and API address together:

API address: https://www.getapi.one
Codex / CC Switch Base URL: https://www.getapi.one/v1
API Key: Copy from the getapi.one API Keys list

Do not mix keys and addresses across services. For Codex and CC Switch, use the Base URL ending in /v1. Other tools may use the service address directly; follow the tool-specific guide.

Security tips

Do not put API Keys in frontend code, public repositories, public documents, screenshots, or screen recordings. If you share screenshots for troubleshooting, hide the key, account, and balance first.

Next step

After the key is ready, use this API address and key in the Agent or tool-specific configuration guide.