Reselling ai.ml

A reseller organization sells ai.ml to its own customers. The customers sign up on your storefront, under your name and on your domain, and pay your prices. You decide who can join, what each customer pays, and who on your team manages what. To turn an organization into a reseller, ask support: it is a commercial agreement, and it sets your revenue share.

Everything here is in the console under Reseller, and in the API reference. These routes use the console session only, not API keys: moving money and admitting customers are things a person does.

Customers

A customer is an organization of its own: its own keys, members, projects and invoices. It has one of two ways to pay:

• Independent. It tops up from its own card or UPI mandate. You earn your revenue share on what it spends, at list price.
• Shared. It spends credit that you move to it from your balance (Allocate credit). It earns you no revenue share, since you paid for the credit.

Customers' API keys carry your key label (acme-live-…), not ai.ml's.

Prices: tiers

A tier is a retail markup on the platform's list price, from 0 to 200 %. Put a customer on a tier and every request it makes is priced at list price plus your markup. The same markup applies to the hold taken before a request, to the progress checks on a long stream, and to the cost on the response. Each cost line is worked out once from the exact product and rounded once, so a markup never compounds a rounding.

The markup is yours. Every hour ai.ml credits your balance with the markup your customers paid in the previous hour, together with your revenue share on independent customers' list-price spend. Your customers' own ledgers show what they paid, not your markup.

A customer paying with its own provider key pays only the platform fee, with no markup.

Your storefront

Reseller → Storefront sets:

• your name, logo and brand colour;
• your support e-mail and pages;
• your display currency and language;
• who can sign up: anyone, only with an invite you send, or nobody;
• the default tier new customers start on.

Your domain

Your domain serves everything your customers use: the console at its root, the API under /v1, and sign-in. Your customers never see an ai.ml address.

1. Add the domain under Domains, for example ai.yourcompany.com.
2. Add a CNAME record from the domain to the target shown on the domain (customers.ai.ml).
3. Publish the TXT record shown, _aiml-storefront.<your domain>, containing the token shown.
4. Press Verify.

Once the domain is verified, a certificate is issued for it, which usually takes a few minutes; the domain reads issuing certificate until then. When it is live, the domain shows your customers' API base URL, https://<your domain>/v1, which they use in place of ai.ml's in any OpenAI- or Anthropic-compatible SDK. If the certificate cannot be issued, the domain says why: fix the CNAME, then press Verify again.

The console on your domain carries your name and logo, signs people in and keeps them there, and sign-ups become your customers on your default tier. A domain belongs to one reseller only, so nobody else can register one you added, even before you verify it.

Your e-mail

The notices your customers receive come from you: a new API key, keys about to expire, an invoice they asked to be sent, a plan that could not be renewed, a webhook endpoint switched off. They carry your storefront's name, link to your domain, and replies go to your support address.

To have them sent from your own domain as well:

1. Under E-mail, enter the sending domain, for example mail.yourcompany.com, and optionally the part before the @ (noreply by default).
2. Publish the two records shown: a TXT record for DKIM, and a CNAME for the return path.
3. Press Verify.

Until the DKIM record verifies, notices go out from the platform's address under your storefront's name. Once it verifies, they come from your address.

Invites

With sign-up set to invite-only, Invites mints codes. Each code admits as many sign-ups as its uses, for 30 days, and is shown only once. The platform's own invites do not work on your storefront, and yours do not work anywhere else.

Your team

Owners and admins of the reseller organization can do everything. Reseller → Staff grants other members individual modules:

Talking to your customers

• Announcements appear at the top of every customer's console while they are active.
• Campaigns are batches of up to 1,000 credit codes paid for from your balance. Only your customers can redeem them. Codes nobody redeems come back to your balance when they expire or when you cancel the campaign. A campaign can be funded once your first payment has stood for seven days, and only from paid credit, not from expiring promotional credit.
• Tickets: your customers file tickets from Support in their console. You see them under Reseller → Tickets, and the platform's support team sees them too.

Invoices

When you fund a customer's balance from your own (Sub-orgs → Allocate), you sold them that credit, so the tax invoice is yours. Under Reseller → Invoicing, save the identity your invoices carry: legal name, address, GSTIN, PAN and state, an LUT number if you invoice customers outside India, and a number series of 2–4 letters and digits. With Issue an invoice in my name on, every allocation issues your tax invoice in the same step: CGST and SGST or IGST by your state and the customer's, numbered in your series (ACME/26-27/00001), in the customer's currency at the day's rate. Your customers see it under Invoices in their console; you see every one under Invoices issued in your name, with its PDF.

These are your supplies under your GSTIN: file them in your own GST returns. If a B2B invoice of yours needs an e-invoice IRN, generate it through your own GSP; the platform does not e-invoice documents it did not supply. To correct one, issue your own credit note: the platform's correction tools do not change documents in your name.

A customer who tops up their own balance pays the platform, so their tax invoice is the platform's, as the law requires. It names you as the provider they buy through, with your support address.

What is not white-labelled yet

• The sign-in page is the platform's identity provider, and the address bar shows it while your customer signs in.
• API response headers keep their x-aiml- names, and the API reference at docs.ai.ml is the platform's.
• Legal notices about the platform's sub-processors come from the platform, because they are the platform's statements as the processor.