Changelog
Unreleased — Account security cleanup
- New accounts use email verification codes or enabled identity providers. Username/password registration and
/registerare removed; existing users can still sign in with a password. - Email binding now uses authenticated
POST /api/user/email/bind/startandPOST /api/user/email/bind. Changing an existing address requires codes from both mailboxes. The oldGET /api/verificationand GET binding route are removed. - Removed
POST /api/user/reset(the inactive reset stub); password reset continues through/api/user/reset/v2. - Removed
/api/log/token,/api/user/used-models,/api/user/models/classified,/api/user/self/stripe/pay, and/api/user/stripe/amount. Use/api/log/self, the model catalog and/api/user/stripe/pay. - Removed the unimplemented
/v1/fine-tunes*,/v1/images/variationsandDELETE /v1/models/:modelroutes. These removals supersede their previously announced sunset dates; no compatibility redirects remain.
2026-10-29 — Search endpoint removed
POST /v1/searchand/api/search/backends*are removed ahead of the announced 2026-11-01 sunset, together with the console page, the search health rows and the API key search fields listed below. Both routes now answer 404endpoint_not_supported(LZ-1010).- Error codes LZ-7302, LZ-7861 and LZ-7862 are retired. The old search docs pages redirect to this changelog.
2026-10-29 — Search endpoint deprecated
POST /v1/searchand the search-backend admin routes (/api/search/backends*) are deprecated and are removed in the first release after 2026-11-01. Their responses now carryDeprecationandSunsetheaders. No customer of api.lazu.ai called the endpoint, so the window is shorter than the usual 90 days.- Going with them: the console's Search backends page, the search health rows, and the API key fields
search_limits_enabled,search_providersandsearch_domain_allowlist. - Unchanged: models' built-in web search tools (
web_searchon/v1/responsesand Chat, Claude's web search on/v1/messages) keep working and are billed as before. Self-hosted deployments that rely on/v1/searchcan call the search provider directly.
2026-10-26 — Five self-hosting settings deprecated
LogConsumeEnabled=falseis deprecated. After 2027-01-24 consume logs are always written; bound their storage withLOG_RETENTION_DAYS.- The Worker download proxy (
WorkerUrl,WorkerValidKey,WorkerAllowHttpImageRequestEnabled) is deprecated. After 2027-01-24 media downloads and webhooks connect directly, under the media fetch policy. general_setting.quota_display_type=TOKENSis deprecated. After 2027-01-24 amounts in log text read in USD, as the console already shows them.SETTLEMENT_OUTBOX_ENABLED=trueis deprecated. After 2027-01-24 the settlement outbox and its reconciler are removed; failed settlements stay covered by the failure reconciler.DataExportEnabled(withDataExportInterval) is deprecated. After 2027-02-01 the hourlyusage_datatable andGET /api/data/go; the dashboard and usage pages do not read them. Export the table first if you keep it.- A deployment that configures any of these now logs a
deprecated setting:line at startup. Details are in the deployment guide's "Deprecated settings" section.
2026-10-26 — API routes scheduled for removal
Each route below now answers with Deprecation, Sunset and, where something replaces it, a Link: <…>; rel="successor-version" header. Admin routes go after 2026-12-01; user routes and public API shapes after 2027-02-01. Production access is checked before each removal.
POST /api/user/self/stripe/pay: usePOST /api/user/stripe/pay.POST /api/user/stripe/amount: the console computes the amount./api/user/used-models,/api/user/models/classified(use/api/user/models/catalog),PUT /api/user/:id/has_topped_up,/api/data/self(use/api/data/dashboard/self),/api/log/token(use/api/log/self),/api/usage/token(use/api/usage/summary),/api/log/self/in_flight(use/api/log/self/tasks),/api/log/self/tasks/:id.- The playground route
/pg/chat/completions; the console has no playground. /v1/fine-tunes*,/v1/images/variationsandDELETE /v1/models/:model, which answer 501, and the balance endpoints/v1/dashboard/billing/*and/dashboard/billing/*; the console wallet replaces them./api/community/*and/api/models/rankings.- Admin, after 2026-12-01:
/api/channel/tag/*and/api/channel/batch*(use per-channel actions),POST /api/notification/email/{send,announcement}(use announcements),/api/upload/*(use the scheduled upload inconfig.yaml),/api/workers/*andGET /api/data/(theusage_datatable it reads is deprecated too).
2026-09-30 — Agent sessions, receipts and long-context prices
- Rebuilt Agent sessions around tasks, models and individual request receipts.
- Added session activity views and subagent lanes. These show gateway activity; local tools are outside the observation boundary.
- Connected long-context pricing to cost calculation, request receipts and public model pages. The actual tier depends on the configured model and lane.
- Corrected sitemap modification dates to reflect actual content changes.
These dates refer to changes merged into the source repository. A self-hosted installation's availability depends on its deployed version. Reconcile a session's costs using the exported details.
2026-05-28 — Usage metadata and cache fields
- Added normalized cache usage fields for OpenAI-compatible responses:
cached_tokens,cache_write_tokens,cache_write_5m_tokens,cache_write_1h_tokens, andcache_miss_tokens. - Added
usage_capabilitiesto the model catalog so clients can discover reported and billable dimensions before sending a request. - Added
GET /api/usage/requests/{request_id}for request-level usage, billing line items, provider raw cache fields, and routing metadata. - Documented Qwen/DashScope, DeepSeek, Anthropic, Gemini, OpenAI, and OpenRouter cache reporting differences.
2026-05-12 — Static docs return to the VPS
- Restore Vocs as the active documentation app for
docs.lazu.ai. - Serve docs as a standalone static nginx container.
- Keep the product brand and API examples consistent across the website and docs.
2026-05-09 — OpenAPI reference cleanup
- Keep
packages/contracts/openapi/lazu-api-reference.v1.yamlas the source of truth. - Sync OpenAPI JSON/YAML into the docs public assets during build.
- Keep the interactive reference available for request and response field checks.