API · SDK · runtime · authentication lifecycle intelligence

Last updated · 9 September 2026

SchemaTrace

Breaking changes, enforcement dates and migration requirements.

ST-2026-164 · API endpoints & versions

Google schedules 16 managed open-model MaaS endpoints for retirement

Sixteen identified managed open-model MaaS endpoints were deprecated on 21 July 2026 and retire on 21 October 2026, when their endpoints are permanently deactivated and API calls fail.

Google CloudMaaSopen modelsmanaged endpointsretirement

Previous state

The named -maas model IDs were accessible through Google-managed open-model endpoints.

Current state

The endpoints are deprecated and permanently deactivate at retirement; API requests using retired IDs fail.

Who needs to care

Applications calling the 16 named managed open-model MaaS IDs through Gemini Enterprise Agent Platform.

What to do

Inventory the named IDs and migrate to an appropriate supported managed model or separately deploy a documented alternative before retirement.

What the source does not prove

Only these managed endpoint IDs are retiring: deepseek-ocr-maas, deepseek-r1-0528-maas, deepseek-v3.2-maas, deepseek-v3.1-maas, glm-5-maas, glm-4.7-maas, gpt-oss-20b-maas, kimi-k2-thinking-maas, llama-3.3-70b-instruct-maas, minimax-m2-maas, multilingual-e5-large-instruct-maas, multilingual-e5-small-maas, qwen3-235b-a22b-instruct-2507-maas, qwen3-coder-480b-a35b-instruct-maas, qwen3-next-80b-a3b-instruct-maas and qwen3-next-80b-a3b-thinking-maas. Model Garden and self-deployed alternatives are not claimed retired.

Lifecycle history

Dated event sequence

  1. Sixteen endpoints deprecated

    Google published the shared deprecation date.

  2. Endpoints retire

    The managed endpoints permanently deactivate and calls fail.

Evidence ledger

First-party sources

  1. 01
    Google Cloud — Open model deprecations

    Official managed-open-model lifecycle table · 2026-07-21

    Open official source ↗