Coding Plan terms

1. Scope

Coding Plan is a subscription for one developer. It includes Kimi K3, GLM-5.3, and DeepSeek V4.1 Flash, and it has no usage cap. Section 7 of the Terms applies to these models.

Each subscription is for one person. Do not share its credentials with other people. Section 3 of the Terms applies to your API keys and other credentials.

Coding Plan may serve an application’s end users under the same conditions as Standard API. Those conditions are the selected model’s terms, the acceptable use rules in Section 6 of the Terms, and the capacity described in Capacity and base rate. As Section 2 of the Terms provides, you are responsible for your applications and end users, including any notices and consents they require.

2. Plans and billing

Coding Plan is sold as two plans, Weekly and Monthly. Weekly costs $149 per developer, per week. Monthly costs $549 per developer, per month. Each week or month you pay for is a billing period. Both plans include the same models and the same capacity.

Each plan renews automatically at the end of its billing period until you cancel. Payment, taxes, and refunds follow Section 9 of the Terms, including the authorization to charge each renewal in Section 9.5.

You can switch from Weekly to Monthly at any time. We credit the unused days of your current week at $149 divided by 7 per day against the $549 Monthly fee. Monthly starts on the day of the switch and runs for 30 days. You can switch from Monthly to Weekly only at renewal.

You can cancel at any time. Access continues to the end of the billing period you have paid for, and the plan does not renew. No refund applies beyond Section 9.4 of the Terms.

3. Capacity and base rate

Coding Plan runs three of your requests at once, including during busy periods. Each of those requests runs at a guaranteed base output rate of 80 tokens per second (the “base rate”). These are your three slots.

When capacity allows, up to eight of your requests can run at once. Capacity above three is not reserved and carries no base rate.

Requests beyond your three slots wait in order for a free slot. A request that cannot start within our wait limit returns HTTP 429 with a Retry-After header.

We measure the base rate for each request as its output tokens divided by the time from its first output token to its last output token. The measurement excludes the time to the first token, the time a request waits for a slot, and slowdowns caused by your network, client, or coding tool.

These terms commit only to the three slots and the base rate. They do not promise availability, completion time, or more than eight requests at once.

4. Service credit

If more than 1% of the qualifying requests sent under your subscription in a billing period run below the base rate, you may request a service credit of 10% of that period’s fee. A request qualifies if you send it:

• while at most three of your requests, including that one, are in flight;
• within the model’s published context limit; and
• to a model that Coding Plan includes.

To request a credit, email contact@standardthinking.ai within 30 days after the billing period ends. Include the billing period and the request identifiers of the affected requests. We evaluate the request against our service records.

We apply an approved credit to the fee for a following billing period. It is not a cash refund and is not a prepaid Credit under Section 9.2 of the Terms. The credit is your sole and exclusive remedy for a missed base rate, except where applicable law does not permit this limitation.

5. Model training

Content and purpose

Requests sent through Coding Plan may be used to train and evaluate models developed by Standard Thinking. This covers the Input of those requests and the Output returned for them. You permit this use as this section describes. This section states what Section 5.3 of the Terms requires: the covered content, the purposes, the retention period, and the controls. We have not started this use. We will note the start date on this page before we begin.

Control

Coding Plan has no setting that turns this use off. Your control is your choice of product: Standard API and Product Plan requests are not used this way.

Retention

Content collected for training and evaluation is kept for no more than 30 days after the request is received. This limit includes copies and content-bearing extracts used for training or evaluation. Copying, preprocessing, de-identifying, or moving the data does not restart the period. We stop using and delete that content by the end of the period. Any copy that we must preserve by law is isolated and is not used for training or evaluation.

The limit applies to the content and its content-bearing copies. It does not by itself require us to retrain or withdraw a model whose training is complete, subject to our obligations under applicable law.

Exclusions

We do not use content for training or evaluation if it is:

• covered by a Zero Data Retention (“ZDR”) commitment;
• restricted data described in Section 9 of the Data Processing Policy; or
• content whose use would violate an applicable customer agreement or applicable law.

Providers and your responsibilities

We use this content only to train and evaluate models developed by Standard Thinking. Providers may help perform that work for us under confidentiality, purpose, access, retention, and deletion restrictions. We do not authorize them to use your content to train or improve their own models.

You must have the rights and authority needed to permit this use of the content you send, including content from your own end users. You must give any notice and obtain any consent that applicable law requires. Your permission does not transfer ownership of your content to us, authorize use of another person’s confidential material without that person’s permission, or relieve us of our own obligations under applicable law. If you lack authority to permit training on work-related code or other material, do not send it through Coding Plan.

Scope and changes

This section applies only to Input and Output submitted on or after the effective date, and only once these terms apply to you. It does not apply to earlier requests.

We give advance notice of a material change to this section as Section 19 of the Terms provides. A change that adds a purpose or lengthens the retention period does not apply to content we have already received.

6. Order of precedence

If these terms conflict with a signed order, enterprise agreement, or other written agreement that covers Coding Plan, that agreement controls. Otherwise these terms control over the Terms of Service for Coding Plan, within the limits in Section 1.3 of the Terms. Capitalized terms not defined here have the meanings in the Terms of Service.