Skip to content

Changelog

What changed, newest first.

Changes to the public site, the developer console and the admin control plane. Entries describe the interface, and say so when an operation still depends on the server API.

Releases

6 entries

  1. Sep 21, 2026Site
    Access labels now describe subscription tiers
    • Model availability in the catalog, pricing table and comparison view is stated as a plan tier — all plans, Developer and up, or Pro and up — instead of the retired add-on and wallet wording.
    • The comparison view derives its rows from the published plan records, so a change in the plan data is reflected there without a separate edit.
  2. Sep 21, 2026Site
    Billing answers added to the FAQ
    • Added answers for plan changes, mid-period upgrade charges, cancellation, auto-renew, invoices and receipts, refunds, annual billing, failed payments, and what happens when a usage limit is reached.
    • Each answer describes behavior the account screens display. Where a policy is configurable, the answer points at the policy shown on the billing screen rather than stating a fixed rule.
  3. Sep 18, 2026Console
    Invoices, transactions and payment method
    • The billing section of the console lists invoices with their number, period, subtotal, tax, total and status, and shows the stored payment method as a reference: brand, last four digits and expiry.
    • Transaction history gained status and type filters with per-record receipt actions.
    • Updating a payment method collects nothing on these screens. Card details are entered on the payment provider's own page.
  4. Sep 18, 2026Console
    Subscription view reports effective state
    • The subscription view shows plan, interval, price, current period, renewal or expiry date, auto-renew state, and usage against each limit, with status values such as trialing, active, past due, cancelling and cancelled shown as text.
    • Where an action needs the billing API — changing plan, cancelling, resuming — the screen states that the operation is unavailable until the API is connected instead of reporting a result that did not happen.
  5. Sep 15, 2026Admin
    Admin control plane routes
    • The /admin namespace is in place with its own denser layout: overview, plans and plan editor, customers and customer detail, subscriptions, transactions, models, features, content publishing, billing settings, and the audit log.
    • Administrative mutations are presented as API calls that return an audit event. Until the server authorizes them by role, they report an error rather than a simulated success.
  6. Sep 12, 2026Site
    Public surfaces and status
    • Pricing, comparison, model catalog, documentation, examples, API reference, status, FAQ and support are published as static pages with canonical URLs.
    • Customer, authentication and admin paths are excluded from prerendering and marked noindex — the sessions and records behind them are not public content.

How to read this page

Scope of a changelog entry.

An entry here means a screen, route or answer changed. It is not a statement that the operation it describes is live: anything that needs a payment provider, webhooks or persistence is marked in the console as unavailable until the server API is connected.

Model additions and retirements are recorded in the model catalog and announced before an identifier is retired. No entry on this page promises an uptime figure or a response-time target.

Where to follow up

If an entry raises a question.

  • Report a regressionInclude the request ID from the activity log.
    Support
  • Check current healthConfirm whether a component is degraded.
    Status
  • Read the current behaviorBilling rules and limit behavior are answered in the FAQ.
    FAQ