Migrate from the legacy gpt88.cc site to Agent

Move from the legacy gpt88.cc entry point to Agent, then complete sign-in, API key creation and your first successful request.

The short answer

Do not treat “the old site still opens” as proof that it is still the right place for every operation. The reliable model is: the legacy site announces the migration, Agent handles accounts and services, and the docs site handles integration.

Complete the migration in five steps

migration-flowtext

1. Open the legacy site and confirm the migration notice
2. Go to https://agent.gpt88.cc
3. Register a new account or sign in with an existing account
4. Check the account, balance and available entry points
5. Open API Keys and the technical docs only when you are ready to integrate

Confirm the site and account first. Only after that should you troubleshoot models, routes, clients or API keys.

Register or sign in on Agent

New users can register at agent.gpt88.cc/register. Existing users can sign in at agent.gpt88.cc/login.

Confirm the address bar shows agent.gpt88.cc, not a similar-looking domain.
Use an inbox you can access for verification and password recovery.
Read the current terms, privacy notice and supported-region information before continuing.
After sign-in, verify that the account and balance entry points are visible.
Never paste passwords, verification codes or complete API keys into public documents or screenshots.

Choose the correct console entry

signed-in-console-flowtext

Signed in
  ├─ Dashboard /dashboard       account status, balance and shortcuts
  ├─ Purchase /purchase         top up or review subscription options
  ├─ API Keys /keys             create a key and choose a group
  ├─ Model Square /model-square compare public models and groups
  ├─ Usage /usage               inspect requests, usage and charges
  └─ Documentation doc.gpt88.cc configure Codex, Claude Code and other tools

Should you top up or create a key first?

Learning the interface: start with Dashboard, Model Square and Pricing.
Preparing an API call: confirm available balance, then create a project-named key in API Keys.
Preparing Codex: make one short API request before configuring the local client so account, key and local configuration issues remain distinguishable.

Standard API calls use https://api.gpt88.cc. Image and video workloads use https://img.gpt88.cc. The website entry point and the programmatic API endpoint are different things.

Remember the new site map

Entry	Purpose	Use it for
agent.gpt88.cc	Account and product entry	registration, sign-in, balance and image workspace
agent.gpt88.cc/keys	API key management	create and manage keys after sign-in
agent.gpt88.cc/model-square	Public model directory	compare groups, multipliers and model coverage
agent.gpt88.cc/pricing	Public pricing	review public offers and budget estimates
doc.gpt88.cc	Technical documentation	quickstart, APIs, SDKs and integrations
api.gpt88.cc	Standard API	OpenAI- and Claude-style API calls
img.gpt88.cc	Media API	long-running image and video workloads

Migration checklist

Confirm the correct Agent account and email.
Locate the balance or billing entry point.
Use Model Square to check the currently visible model groups.
Use the Quickstart guide for API integration.
Open the relevant Codex, Claude Code, Cursor or CC Switch integration guide.

Common mistakes

Continuing to perform account or top-up operations on the legacy site after seeing the migration notice.
Using agent.gpt88.cc as an API Base URL instead of the documented API host.
Confusing a web-login password with an API key.
Creating many keys before confirming the account and first request.
Assuming a public model group guarantees access for every account or key.

Optional analytics