What each side undertakes.

To provide the service as the documentation describes it, and to state for each public surface the stability the registry gives it: stable, beta or alpha. A beta or alpha surface may change, and the change is announced in the changelog before it takes effect.

To use the service within the documentation and these terms, through the surfaces it exposes, and to keep its keys secret.

To issue keys to your organisation alone, to hold its data in a tenant isolated at the database layer, and to act only on requests that carry its context.

To be responsible for every request made under its keys, to name an administrator who may act for it, and to rotate a key as soon as it suspects the key is known to anyone else.

To stop a run before any action your organisation has marked as protected, to bind each approval to the organisation, the person, the run and the exact version of the action, and to let an approval expire unused.

That a person who approves an action does so for the organisation, and that an action taken on a valid approval is the organisation's own act. The organisation decides which actions are protected, and reviews that choice.

To run input and output guards on every run and to refuse what they catch: injection, malformed requests, leaked personal data and claims without a source. To tell your organisation when a guard has refused something.

Not to use the service to break the law, to process information it has no right to process, to attack or probe systems, to produce content meant to deceive, or in any way the policies of the model providers in use forbid.

To state its prices on the pricing page, to reserve the cost of a model call before it is made and settle it after, and to itemise the spend of every run on its receipt. To enforce the budgets your organisation sets and never to extend a hard budget without a person's decision.

To pay the fees as billed for the plan it has chosen, to keep a payment method current, and to treat the spend on a receipt as the record of what a run cost.

To process your organisation's content only to do the work it has asked for, under the privacy notice and the data processing terms. Never to use that content to train or evaluate models unless the organisation has opted in. To provide export and erasure as the privacy notice describes.

That it holds the rights it needs to the content it places in the service, that it remains the controller of that content, and that it answers requests from its own people about their information, with Q Division's assistance.

To say plainly where the service stands. No production gate has yet been passed, and no service level is offered until one is. To report incidents honestly, and to answer support requests sent to the address below within two working days.

To report a fault with the run identifier from the receipt, and to accept that a beta or alpha surface may change with notice.

To suspend access only for non-payment, for a breach of article 04, or to protect other organisations or the service, and to give notice first wherever that is possible. On ending, to keep the organisation's export available for thirty days, and then to erase its content under the privacy notice.

That it may stop using the service at any time, that fees for the current period remain due, and that it exports what it wishes to keep within that period.

To accept the liability the law does not allow it to exclude. Beyond that, its total liability under these terms is limited to the fees your organisation paid for the service in the twelve months before the event giving rise to the claim. Your organisation's agreement may set a different cap, and governs where it does.

To be responsible for its own use of the service, for the content it places in it, and for the actions its people approve.

To publish the revision and its date at the top of this page, and to tell organisations in service before a change to these terms takes effect. These terms are governed by the law of Mauritius, and the courts of Mauritius have jurisdiction over any dispute about them.

To read a change when it is announced, and to stop using the service before the change takes effect if it does not accept it.