Preview availability
What you can use today, what is gated, and how to interpret the examples in these docs.
The hosted site currently exposes a production-deployed console preview. The application and its stored project state are real, but paid model execution and live payment collection are not enabled. These are separate capabilities; loading the console is not evidence that a training job can run.
Current surfaces
| Surface | Hosted behavior |
|---|---|
| Marketing and documentation | Public and readable without an account |
| Email-code sign-in and project setup | Clerk-backed verified accounts |
| Project settings and API keys | Backed by the platform database |
| Request, adapter, and usage views | Show the project's recorded state; no invented successful jobs |
| Billing | Explicit preview; no payment taken and no spendable credits issued |
| Inference and internalization | Admission disabled with execution_unavailable |
| Authentication delivery | Managed by Clerk |
| Public TypeScript package | Not published; the SDK is a private workspace package |
Running examples
The examples document the implemented public API shape for execution-enabled projects. On the current hosted deployment, an authenticated model submission returns 503 with error.code: "preview_only". Repeating it with another key or a larger purchase preview cannot enable execution.
You can still inspect the OpenAPI schema, build request validation, integrate the job state machine, and prepare your server-side credential handling. Keep application tests clearly separate from live model evidence. A local mocked response can test your UI, but it cannot demonstrate that a model learned anything.
Read-only operations authenticate normally. For example, a valid key can read the model catalogue or the subjects visible to its project and scopes. Empty history in a new preview project is expected.
Billing when enabled
The product uses prepaid credit with a $10 minimum purchase, no free trial balance, and no automatic top-up. The approved rates are $12/M input, $30/M output, $2.50/M verified cached input, $36/M training, and $0.30/GB-month retained memory. Learning has no flat fee and requires an explicit budget. Live checkout will use Polar and verified payment events to credit the project.
A successful purchase preview changes no balance. A production payment redirect will also not be sufficient evidence on its own: the verified payment event is authoritative. See Payments.
Supported model and API limits
GLM 5.3 is the only model in the current API catalogue. There is no customer-selectable model field or automatic fallback model. Other models are planned, but no availability date is promised here.
The API exposes full asynchronous results. Streaming, cancellation, user-configured webhooks, adapter export, subject deletion, and a public MCP endpoint are not exposed. Do not build an integration around private worker routes to approximate them. If a missing capability is essential, contact team@convergingthought.com with the intended workflow.