Pricing Configuration

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.

How your wholesale price is decided

What you charge customers is built on top of your wholesale price. You do not set that price yourself. When tier-based wholesale pricing is enabled for the site, the platform uses three sources, and the first one that applies wins. Sites that have not enabled it retain their existing cost rules; ask the platform to verify the effective price:

Partner tiers are Diamond, Gold, Silver and Member, assigned by the platform under your commercial agreement. A top-up does not automatically assign or upgrade a tier. Your shelf shows the effective wholesale discount; ask your account manager to verify your tier and price source when needed.

When this section matters: after you negotiate a new tier, or when a route's margin differs from your expectations. Check whether the row still carries a negotiated price and whether tier-based wholesale pricing is enabled for the site.

Creating a group

Click to create a new group in the pricing table:

Understanding price ratios

The ratio applies to the model's base price: a higher ratio means the customer pays more and you earn more.

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.

All of the above describes the fixed mode. If a row is set to follow the platform, the customer price is derived from the platform's direct price times your markup factor, and the ratio on the row no longer decides what the customer pays — see the next section.

Two pricing modes: fixed and follow-the-platform

Every shelf row uses a pricing mode that determines whether it follows platform group or customer-tier ratios. Fixed mode fixes the ratio, not the absolute model unit price. Changes to model base prices can affect both modes.

The platform verifies and sets your site's actual markup factor. For example, 1.2 adds twenty percent to the platform's direct price; this is a calculation example, not a universal default for new sites. Follow mode uses the platform price for that customer's tier, so if the platform prices tiers differently, your selling price is tiered too.

Which to use: choose fixed mode when you want to manage each route's ratio independently, or follow mode when selling prices should follow applicable platform prices. You can mix both. If a contract promises a fixed amount, fixing the ratio alone is insufficient; ask your account manager to verify model base prices and the full billing agreement.

Charging different customers different prices

One shelf row can sell at different prices to different customers, so you do not need a separate group for every discount:

• By customer segment: one price per segment you have defined — trial customers at one price, contracted customers at another;
• A reserved price for one large customer: a price negotiated with a single account, leaving everyone else untouched.

The lookup order is single-customer price → segment price → the row's default price; the first one found wins. These overrides apply in both pricing modes: on a fixed row they override the ratio you pinned, on a follow row they override the price that was derived.

When to use it: when customers differ enough in volume that you negotiate stepped discounts. For one or two special accounts, a reserved price in Customer Management is less work; to cut the price for everyone, changing the row's default price is less work still. Every extra override makes month-end margin checks harder, so keep the number of steps small.

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.

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.

When the platform adds new supply for you

When the platform lists new suppliers in bulk, extra rows appear on your shelf carrying a New listing badge:

• these rows are hidden by default and are not offered as default manual supplier choices. Requests still depend on source permissions, user-group rules and existing key strategies; hiding a row does not replace authorization checks;
• they default to follow-the-platform pricing, which means a price is already derived from your markup factor;
• the badge disappears on its own 30 days after listing; the row itself is unaffected.

The routine when you see the badge: check the row's wholesale discount and the derived selling price → make it visible if the numbers work → leave it hidden indefinitely if you do not want to sell it yet. There is no need to delete it.

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.

Bundling several routes into one option

You can bundle several routes into a single named supplier bundle of your own. Customers pick the bundle when they create a key, instead of working out which route they should be on.

• The routing mode is configurable: ordered routing tries eligible members in sequence; automatic routing applies existing reseller routing rules within the bundle's members. A bundle does not grant additional source permissions;
• A bundle has no independent price: charges follow the request's applicable pricing and billing agreement. Prepaid requests with persistent preauthorization retain their frozen customer price on retries, rather than necessarily repricing from the final route. Use the actual source to reconcile costs and logs;
• A new bundle is hidden by default: confirm its members and their order before releasing it to customers.

When to use it: when customers just want something that works and do not care which supplier is behind it, or when you want to package a primary route plus a backup as a single selling point and stop explaining group choices to every new account. Conversely, if you want customers comparing routes and choosing for themselves, skip bundles and expose the groups directly.

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.

1. Click Add retry rule or a row's Edit button to open the side drawer.
2. 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.
3. 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.
4. 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

Related