Pricing Configuration
Creating your own groups, setting customer price ratios and controlling group visibility.
The Pricing tab determines what prices your customers see. It is the core of reseller economics.
What a group is
A supplier group links model availability with applicable pricing. When creating an API key, customers can choose authorized groups manually or select Fast & Stable (Enterprise) or Cost Effective (Value) to let the system choose among sources that are both authorized and registered in supply pools.
Keep three questions separate: the routing strategy determines how to choose, source permissions determine what may be chosen, and pricing rules determine the charge. Strategy names do not add a uniform Enterprise / Value package discount. Historical Enterprise, Value, and Standard groups remain; the new strategy names do not delete or rename them.
The platform provides several underlying routes; you create groups under your own names on top of them.
| Concept | Who sees it | Example |
|---|---|---|
| Your group name | Your customers | "Standard", "Enterprise", "Value" |
| Underlying route | Only you | The "based on group" option during configuration |
Customers only ever see the name you chose. You are free to follow your own product taxonomy rather than the platform's.
Creating a group
Click to create a new group in the pricing table:
| Field | Description |
|---|---|
| Group name | What customers see. Must be unique within your account; any language is fine |
| Based on group | Which underlying route it builds on, which determines the available models |
| Price ratio | Determines what the customer actually pays |
| Member visibility | Whether customers can select it on keys and in the Playground |
After editing a group, you must click Save on that row. Navigating away without saving discards the change.
Understanding price ratios
The ratio applies to the model's base price: a higher ratio means the customer pays more and you earn more.
There is a price floor. If your ratio would put the customer price below your procurement cost, saving is rejected with a message.
This is a safeguard against selling at a loss. Do not retry repeatedly — raise the ratio. For your specific procurement pricing, consult the commercial materials from the platform or contact your account manager.
When pricing, leave enough gross margin to cover:
- your operating costs (support, marketing, payment terms);
- exchange-rate movement, if you collect in local currency;
- room for promotional discounts.
Member visibility
Every group has a visibility switch:
- Visible → customers can select it in the group dropdown when creating keys and in the Playground;
- Hidden → not a default choice for all customers. Access also depends on user-group rules and individual permissions. Existing keys are checked against current permissions on each request; an old key does not preserve revoked access.
A new reseller account comes with several pre-seeded groups, and some are hidden by default. This is intentional.
Hidden groups typically map to special price lines. Exposing them to regular customers means a customer can select a route they were never meant to have, directly reducing your revenue.
Do not switch them all on just to "give customers more choice". When unsure whether a group should be exposed, ask your account manager first.
Opening a group to one customer
To give a large customer access to a dedicated group, do not change the global visibility — set it per customer on the Users tab. That satisfies the individual case without affecting everyone else.
Additional groups
Configure Appended selectable groups under User groups to grant members access to additional supplier groups. These permissions constrain both manual supplier choices and the sources available to automatic routing.
How platform administrators grant supplier access
Open Agent Management → Manage on the target agent's row → Agent Pricing → Shelf system group. List the required system source as a reseller group, then configure Appended selectable groups for the relevant user group or set permissions for an individual customer.
Access to the stability or price pool comes from authorized, active sources. Making a source a rescue route for the other pool does not grant access to that other strategy. Configuring selectable sources controls what customers can use; the routing upgrade does not replace administrator authorization.
How platform administrators maintain supply pools
Supply-pool settings use a compact table with supplier-name search and pool filters. Each source's Fast & Stable and Cost Effective roles appear side by side and can be set to Main, Rescue only, or Excluded. Source details are maintained in an edit dialog.
Health and rescue parameters are collapsed by default. Expand them when needed. Saving validates groups, pool membership, numeric ranges, and temporary-override expiry; editing is locked while saving. If another operation updates the server configuration, reload the current version before editing again. An active temporary override shows a badge and locks the corresponding normal role control.
Pool roles affect selection. They do not change customer permissions or define a uniform strategy price.
How platform administrators configure retry rules
Open System Settings → Models & Routing → Retry Routing and use the Visual editor to manage system-wide rules. This entry is for platform administrators with the required management permissions, not the API-key routing selector for ordinary customers.
The table shows rule names, actions, priorities, match conditions, and retry destinations. Search by rule or channel name, with eight rules per page. Channel selectors display name + ID and support name or ID search; disabled, missing, or temporarily unnamed channels have a status hint. If names cannot load or channel-view permission is unavailable, existing IDs are retained rather than replaced with other channels.
- Click Add retry rule or a row's Edit button to open the side drawer.
- Set the rule name, enabled state, action, and priority, then configure matching HTTP status codes, models, request packages, failed channels, and other conditions. Different conditions use AND; items within one condition use OR. An empty condition is unrestricted.
- For retrying rules, choose Supply pools with main / rescue roles, or Channels, groups and tags. Destinations only narrow existing eligible candidates; they do not grant permissions or define a fixed channel-attempt order. Changing destination type clears incompatible destination fields in the draft. Selecting Skip retry clears destination filters and the rule's retry count.
- Click Apply to draft, review the table, then click Save retry routing. Applying, deleting a rule, inserting a template, or switching editor tabs does not activate the configuration by itself; changes take effect only after a successful save.
Follow the matching order shown in the editor: skip-retry rules first, then other actions by descending priority, with ties retaining rule order. Channel rules precede system rules. A retry count of 0 uses the existing system limit; it does not mean unlimited retries.
Advanced JSON and the visual editor share one draft. Unedited JSON fields, including advanced strategy options, are preserved. Use the advanced view to repair invalid JSON or rules marked Needs JSON review; existing text is not automatically cleared. Editing is locked during saving. If server rules have changed, copy your draft if needed, then click Reset to load the latest version before editing again. If the list changes while a rule drawer is open, cancel and reopen that rule before applying it.
Pricing with automatic routing
Settlement uses the request's applicable source pricing and existing membership or reseller pricing, without a separate uniform discount based on the Enterprise / Value label. Cost Effective favors lower prices among healthy candidates; it does not promise the absolute cheapest route on every request.
For a prepaid reseller request that has been pre-charged and has a durable authorization, retries preserve the frozen customer price ratio and billing terms for that request. A supplier switch does not mean the customer price is recalculated from the final source. Reconcile charges using Usage Logs and Billing, rather than inferring the charge from the final route alone.
The blast radius of a pricing change
Changing a price ratio affects subsequent requests using that group, including requests made with existing keys. Prepaid reseller requests with an established durable authorization retain their frozen billing terms through retries.
To raise prices:
- Announce it in advance via a site announcement;
- Keep existing customers on the original price by creating a new group for new customers;
- Watch usage patterns after the change.