Setup & First Configuration
Checklist for a new reseller account — confirm the wallet, configure branding, bind a domain, set pricing, create your first customer.
Once the platform provisions your reseller account, follow this order to get your site live. The whole process takes about half an hour.
Before you start
Make sure you have received the following from your account manager:
- Reseller administrator credentials (email and password);
- Your reseller site address (a platform-assigned subdomain, or your own domain);
- The agreed procurement pricing and settlement terms.
After signing in, Personal → Agent Console in the left sidebar is your workspace.
Step 1: Confirm your wallet balance
Open the Finance tab and check the wallet balance.
At zero balance you cannot grant any credit to customers — no top-ups, no quota adjustments, no redemption codes.
If the balance is zero after provisioning, arrange prepaid procurement with your account manager first.
Step 2: Configure site branding
On the Overview tab, set:
| Item | Purpose |
|---|---|
| Site name | Browser title and page header |
| Logo | Your own brand mark |
| Homepage content | What your reseller site shows on its landing page; supports Markdown and HTML |
| Display language and currency | The defaults your customers see |
| Support entry point | Live-chat script or WhatsApp number |
Customer-service settings from the main platform site are not inherited. Your reseller site has no support entry point until you configure one — without it, customers who run into trouble have no way to reach you.
Step 3: Bind a domain (optional)
To use your own domain rather than the platform-assigned subdomain:
- Submit the domain in the domain section of the Overview tab;
- Add the DNS record shown on the page at your DNS provider;
- Return to the console and click verify.
Once verified, the HTTPS certificate is issued automatically — you do not need to supply one.
DNS propagation takes anywhere from a few minutes to tens of minutes. If verification keeps failing, confirm the record has propagated with a DNS lookup tool before contacting technical support.
Step 4: Set pricing
Open the Pricing tab and configure the groups and prices you will sell.
Key concepts:
- A group determines which models a customer can use and how they are charged;
- You can create groups under your own names (for example "Standard", "Enterprise", "Value"), and that is what customers see;
- Each group carries a price ratio that determines what customers actually pay.
The system blocks pricing below your procurement cost. If saving fails with a "price too low" message, that ratio would make you lose money on every call — raise it.
Step 5: Review group visibility
Not every group should be visible to customers. On the Pricing tab, check member visibility for each group:
- Visible → customers can select it when creating keys and in the Playground;
- Hidden → customers cannot select it, though existing keys already using it are unaffected.
A new reseller account comes with several pre-seeded groups, and some are hidden by default. That is deliberate. Certain groups map to special price lines, and exposing them to regular customers causes pricing chaos.
Do not simply switch them all on. When in doubt about a group, ask your account manager first.
Step 6: Create your first customer
Open the Users tab and create a test account:
- Create a customer with an email and initial password;
- Assign a group;
- Adjust quota to give it some test credit;
- Sign in to your reseller site as that account, create an API key and make a call.
Completing this loop means your site is ready to go live.
See Customer Management.
Pre-launch checklist
- Wallet balance is sufficient
- Site name and logo configured
- Support entry point configured (customers being unable to reach you is the most common launch incident)
- Domain verified and HTTPS working
- Pricing set, above procurement cost
- Group visibility reviewed one by one
- Full loop verified with a test account: sign up → credit → create key → successful call
- Sub-admin permissions configured if you have a team (see Team & Permissions)