Phaseo Team31 May 20265 min read
ICYMI: What We Shipped in May 2026
A plain-English recap of May improvements across video, observability, provider activation, SDKs, model pages, and catalog coverage.

May was one of the busiest Phaseo release months so far. The product moved further beyond a model directory and deeper into gateway workflows: video, async jobs, observability, provider activation, and SDK work all moved forward.
This recap covers the work that shipped from 1 May 2026 through 31 May 2026, based on the release history, commit history, and catalog data for the month.
What Shipped
Video and async jobs became more complete
May shipped a large gateway update covering video rollout, usage visibility, request diagnostics, and the batch and video async lifecycle.
That included support for status checks, cancellation, content retrieval, downloads, and clearer usage details. In plain English: long-running work became easier to start, track, inspect, and debug.
This was an important product shift. Video and batch jobs do not behave like simple chat requests. They take longer, they can fail in different ways, and users need better ways to follow progress. May made those workflows feel more like first-class parts of the gateway.
Observability moved closer to real production use
Request diagnostics became more useful in May. The gateway added clearer request detail, early error visibility, provider activation states, and better usage refresh paths.
For teams running real workloads, this reduces guesswork. If a request fails, routes differently than expected, or uses an unexpected provider, the product should help explain what happened.
That is the difference between a demo gateway and something a team can actually operate. Observability is not only about charts; it is about giving people enough context to fix the next request.
Provider activation and pricing became clearer
Provider availability became easier to understand across catalog pages and internal data. Provider activation states started showing more consistently, pricing summaries and hover cards improved, and realtime minute pricing was corrected.
May also included provider data refreshes for Google, Anthropic, Baseten, Venice, Novita, CrofAI, AWS, and others. Several of those updates were small on their own, but together they made the catalog more current and more dependable.
This is especially useful when the same model has several providers. Users need to know not just that a model exists, but where it can be run, what it costs, and whether the route is active.
The TypeScript Agent SDK launched
May introduced the first public TypeScript Agent SDK work for Phaseo. The release added SDK code, examples, docs, devtools alignment, and migration tooling around the gateway contract.
The goal was to make longer-running agent workflows easier to build without making every team stitch together their own loop, tools, telemetry, and retry behaviour from scratch.
The first examples focused on practical workflows: coding review, research, support triage, and parallel local tools. That gave developers a clearer starting point than a bare API reference.
Model discovery got more automated
We added GitHub issue sync for provider model changes, controlled notifications, and clearer model discovery handling. We also refreshed benchmark data and improved date ordering and model-family behaviour.
This work helped the catalog keep up with fast provider changes without turning every update into a manual hunt. It also made it easier to separate real provider changes from noisy discovery output.
The catalog is only useful if it stays current. May was about reducing the manual work needed to keep it that way.
Also Shipped
- Header search loading was deferred so the main page could load before the search index.
- Homepage monthly token stats were corrected.
- Media retry settings and duplicate handling were fixed.
- Benchmark rank ordering was corrected.
- Organisation social links gained URL validation.
- Free-model credit gating and workspace policy enforcement were hardened.
- Dependency updates landed across Next.js, Mintlify, Hono, Zod, PostHog, and CI tooling.
Model Highlights
May brought a wide model mix. OpenAI added chat-latest and several realtime models. Google moved Gemini 3.1 Flash-Lite and Gemini 3.5 Flash forward, then added image-model releases later in the month. xAI added Grok Imagine Image Quality, Grok Build 0.1, and a Grok Imagine Video 1.5 Preview entry.
The month also included Claude Opus 4.8, Command A+, Qwen 3.7 Max variants, Cursor Composer 2.5, Step 3.7 Flash, CrofAI Greg RP, and NVIDIA Cosmos3 Super Reasoner.
Browse the latest release data here:
Shipping Snapshot
The local git history shows 77 commits during May. The month centred on video and async jobs, provider activation, observability, SDK launch work, pricing fixes, model discovery automation, and a steady run of catalog releases.
Models Released In May 2026
The catalog includes these models with May 2026 release dates:
- 5 May: chat-latest (
openai/chat-latest) - 6 May: Grok Imagine Image Quality (
x-ai/grok-imagine-image-quality) - 7 May: Gemini 3.1 Flash-Lite (
google/gemini-3.1-flash-lite) - 7 May: GPT Realtime 2 (
openai/gpt-realtime-2) - 7 May: GPT Realtime Translate (
openai/gpt-realtime-translate) - 7 May: GPT Realtime Whisper (
openai/gpt-realtime-whisper) - 15 May: Grok Build 0.1 (
x-ai/grok-build-0.1) - 18 May: Composer 2.5 (
cursor/composer-2.5) - 19 May: Gemini 3.5 Flash (
google/gemini-3.5-flash) - 19 May: Qwen 3.5 LiveTranslate Flash Realtime (2026-05-19) (
qwen/qwen3.5-livetranslate-flash-realtime-2026-05-19) - 20 May: Command A+ (
cohere/command-a-plus) - 21 May: Qwen 3.7 Max (
qwen/qwen3.7-max) - 25 May: Qwen 3.7 Max (2026-05-17) (
qwen/qwen3.7-max-2026-05-17) - 25 May: Qwen 3.7 Max Preview (
qwen/qwen3.7-max-preview) - 26 May: Qwen 3.7 Plus (2026-05-26) (
qwen/qwen3.7-plus-2026-05-26) - 28 May: Claude Opus 4.8 (
anthropic/claude-opus-4.8) - 28 May: Greg RP (
crofai/greg-rp) - 28 May: Gemini 3.1 Flash Image (Nano Banana 2) ()
Next Up
May set up June for more catalog automation, more provider coverage, better monitor pages, and more work around onboarding and local developer workflows.