@mastra/mcp-docs-server 1.2.11 → 1.2.12-alpha.3

package/.docs/guides/migrations/upgrade-to-v1/agent.md

@@ -45,7 +45,7 @@ To migrate, replace all calls to `mastra.getAgents()` with `mastra.listAgents()`
 
 ### `RuntimeContext` to `RequestContext`
 
-The `RuntimeContext` class has been renamed to `RequestContext` throughout the codebase. This change provides clearer naming that better describes its purpose as request-specific data and aligns with web framework conventions.
+The `RuntimeContext` class has been renamed to `RequestContext` throughout the codebase. The new name identifies the class as request-specific data and matches web framework conventions.
 
 To migrate, update all imports and parameter names from `RuntimeContext`/`runtimeContext` to `RequestContext`/`requestContext`.
 
@@ -91,7 +91,7 @@ To migrate, replace property access with the corresponding getter methods.
 
 ### Voice methods moved to `agent.voice` namespace
 
-Voice-related methods have been moved from the Agent class to the `agent.voice` namespace. This change provides better organization and clearer separation of concerns.
+Voice-related methods have moved from the Agent class to the `agent.voice` namespace, which groups the voice APIs together.
 
 To migrate, update voice method calls to use the `agent.voice` namespace.
 
@@ -112,7 +112,7 @@ To migrate, update voice method calls to use the `agent.voice` namespace.
 
 ### `agent.fetchMemory()` to `(await agent.getMemory()).recall()`
 
-The `fetchMemory()` method has been replaced with a more explicit API. This change provides better clarity about the asynchronous nature of memory access.
+The `fetchMemory()` method has been replaced with an API that makes asynchronous memory access explicit.
 
 To migrate, replace `fetchMemory()` calls with the new API.
 
@@ -167,7 +167,7 @@ Only update your imports if you want to standardize on one Zod version across yo
 
 ### Default options method renames for AI SDK versions
 
-Default options methods have been renamed to clarify legacy (AI SDK v4) vs new (AI SDK v5+) APIs. This change helps developers understand which AI SDK version they're targeting.
+Default options methods have been renamed to distinguish legacy (AI SDK v4) APIs from AI SDK v5+ APIs. The method name now indicates which AI SDK version it targets.
 
 To migrate, update method names based on which AI SDK version you're using.
 
@@ -184,7 +184,7 @@ To migrate, update method names based on which AI SDK version you're using.
 
 ### `modelSettings.abortSignal` to top-level `abortSignal`
 
-The `abortSignal` option has been moved from `modelSettings` to the top level of stream/generate options. This change provides a clearer separation between model-specific settings and execution control.
+The `abortSignal` option has moved from `modelSettings` to the top level of stream and generate options. Execution control now sits outside model-specific settings.
 
 To migrate, move `abortSignal` from `modelSettings` to the top level.
 
@@ -229,7 +229,7 @@ const agent = new Agent({
 +   id: 'my-agent',
     name: 'My Agent',
     instructions: 'You are a helpful assistant',
-    model: 'openai/gpt-5.5',
+    model: 'openai/gpt-5.6-sol',
   });
 ```
 

package/.docs/guides/migrations/upgrade-to-v1/cli.md

@@ -14,7 +14,7 @@ A new `mastra migrate` command helps run database migrations when upgrading Mast
 npx mastra migrate
 ```
 
-The command bundles your project, connects to your configured storage, and runs any necessary migrations. Currently supports migrating duplicate spans entries that may prevent unique constraint creation.
+The command bundles your project and connects to your configured storage before running any necessary migrations. It currently supports migrating duplicate span entries that may prevent unique constraint creation.
 
 See the [Storage migration guide](https://mastra.ai/guides/migrations/upgrade-to-v1/storage) for details on when this migration is needed.
 

package/.docs/guides/migrations/upgrade-to-v1/client.md

@@ -2,7 +2,7 @@
 
 # Client SDK
 
-Client SDK changes align with server-side API updates including renamed utilities, updated pagination, and type naming conventions.
+Client SDK changes align with server-side API updates, including utility renames, updated pagination, and type naming conventions.
 
 ## Changed
 
@@ -126,7 +126,7 @@ To migrate, update type imports to use the new naming pattern.
 
 ### Pagination parameters from `offset/limit` to `page/perPage`
 
-All client SDK methods that used `offset/limit` now use `page/perPage`. This change provides a more intuitive pagination model aligned with web pagination patterns.
+All client SDK methods that used `offset/limit` now use `page/perPage`, matching page-based web pagination.
 
 To migrate, update pagination parameters in all client SDK method calls. Example:
 
@@ -211,7 +211,7 @@ To migrate, use `runById()` instead, which now returns the same unified `Workflo
 
 ### `toAISdkFormat` function
 
-The `toAISdkFormat()` function has been removed from `@mastra/ai-sdk`. This change provides clearer naming for stream conversion utilities.
+The `toAISdkFormat()` function has been removed from `@mastra/ai-sdk`. Use the stream conversion utilities shown below instead.
 
 To migrate, use `toAISdkStream()` instead.
 

package/.docs/guides/migrations/upgrade-to-v1/evals.md

@@ -25,7 +25,7 @@ To migrate, replace all calls to `getScorers()` with `listScorers()`.
 
 ### `runExperiment` to `runEvals`
 
-The `runExperiment()` function has been renamed to `runEvals()`. This change provides clearer naming that better describes the evaluation functionality.
+The `runExperiment()` function has been renamed to `runEvals()` to identify that it runs evaluations.
 
 To migrate, update function calls from `runExperiment` to `runEvals`.
 
@@ -152,7 +152,7 @@ import type {
 
 ### Message content structure to nested format
 
-Tool invocations and text content are now accessed through a nested `content` object structure instead of being flat properties on the message. This change provides better type safety and aligns with the database message format.
+Tool invocations and text content are now accessed through a nested `content` object instead of flat message properties. The nested structure matches the database message format and its types.
 
 To migrate, access tool invocations via `message.content.toolInvocations` and text via `message.content.content` or use the `getTextContentFromMastraDBMessage()` helper.
 

package/.docs/guides/migrations/upgrade-to-v1/memory.md

@@ -260,7 +260,7 @@ To migrate, use `MastraDBMessage` for storage or AI SDK v5 message formats direc
 
 ### `processors` config from Memory constructor
 
-The `processors` config option in the Memory constructor has been deprecated and now throws an error. Processors should be configured at the Agent level instead. This change provides clearer configuration boundaries and better encapsulation.
+The `processors` config option in the Memory constructor is no longer supported and throws an error. Configure processors at the Agent level, where processor behavior is scoped to agent execution.
 
 To migrate, move processor configuration from Memory to Agent using `inputProcessors` and/or `outputProcessors`.
 

package/.docs/guides/migrations/upgrade-to-v1/overview.md

@@ -6,11 +6,11 @@
 
 Mastra v1 was released in January 2026. We recommend starting any new projects with Mastra v1, or upgrading your existing project to continue receiving updates and support.
 
-This guide provides a comprehensive overview of breaking changes when upgrading from Mastra 0.x to v1.0. The migration is organized by package and feature area to help you systematically update your codebase.
+This guide covers the breaking changes when upgrading from Mastra 0.x to v1.0. The migration is organized by package and feature area to help you systematically update your codebase.
 
 > **Need help?:** Need help with the migration? Join our [Discord community](https://discord.gg/BTYqqHKUrf) to ask questions.
 
-> **Coming from Mastra Cloud?:** The legacy Mastra Cloud product has been replaced by the [Mastra platform](https://mastra.ai/docs/mastra-platform/overview), which splits hosting into two separate products: **Studio** (visual environment, observability) and **Server** (production API). Old Mastra Cloud access tokens don't work with Mastra platform — you must create new ones with `mastra auth tokens create`.
+> **Coming from Mastra Cloud?:** The legacy Mastra Cloud product has been replaced by the [Mastra platform](https://mastra.ai/docs/mastra-platform/overview), which splits hosting into two separate products: **Studio** (visual environment, observability) and **Server** (production API). Old Mastra Cloud access tokens don't work with Mastra platform. Create new ones with `mastra auth tokens create`.
 >
 > If you upgrade to v1 packages without also migrating your `telemetry:` config to `observability:` and creating a Studio project, observability data will stop flowing. Follow the [Mastra Cloud migration guide](https://mastra.ai/guides/migrations/mastra-cloud) end to end.
 
@@ -18,7 +18,7 @@ This guide provides a comprehensive overview of breaking changes when upgrading
 
 ### Update all Mastra packages to `latest` tag
 
-Use your package manager to update your project's versions. Be sure to update **all** Mastra packages at the same time to ensure compatibility (all `@mastra/*` packages and `mastra`).
+Use your package manager to update your project's versions. Update **all** Mastra packages together to ensure compatibility (all `@mastra/*` packages and `mastra`).
 
 Here's how you update the most commonly used packages:
 

package/.docs/guides/migrations/upgrade-to-v1/processors.md

@@ -27,7 +27,7 @@ import type { InputProcessor } from '@mastra/core/processors';
 
 ### Processor message types from `MastraMessageV2` to `MastraDBMessage`
 
-Processor message types have changed from `MastraMessageV2` to `MastraDBMessage`. This change provides consistency with scorer configuration and better type safety by aligning with the database message format.
+Processor message types have changed from `MastraMessageV2` to `MastraDBMessage`. Processors and scorers now use the database message format and its types.
 
 To migrate, update processor message type imports and usage.
 

package/.docs/guides/migrations/upgrade-to-v1/storage.md

@@ -39,7 +39,7 @@ Run the migration command which automatically deduplicates spans and adds the co
 npx mastra migrate
 ```
 
-The CLI bundles your project, connects to your configured storage, and runs the migration. It keeps the most complete record (based on `endTime` and attributes) when removing duplicates.
+The CLI bundles your project and connects to your configured storage before running the migration. It keeps the most complete record (based on `endTime` and attributes) when removing duplicates.
 
 #### Option 2: Manual SQL (PostgreSQL)
 
@@ -144,7 +144,7 @@ To migrate, update your imports and instantiation:
   });
 ```
 
-> **Note:** If you're using a single store implementation (like `PostgresStore` or `LibSQLStore`) directly, no changes are needed. This only affects code that explicitly uses `MastraStorage` for composite storage.
+> **Note:** If you're using a single store implementation (like `PostgresStore` or `LibSQLStore`) directly, keep the existing configuration. This only affects code that explicitly uses `MastraStorage` for composite storage.
 
 ### Required `id` property for storage instances
 
@@ -168,7 +168,7 @@ const storage = new PostgresStore({
 
 ### Pagination from `offset/limit` to `page/perPage`
 
-All pagination APIs now use `page` and `perPage` instead of `offset` and `limit`. This change provides a more intuitive pagination model that aligns with common web pagination patterns.
+All pagination APIs now use `page` and `perPage` instead of `offset` and `limit`, matching page-based web pagination.
 
 To migrate, update all pagination parameters from `offset/limit` to `page/perPage`. Note that `page` is 0-indexed.
 
@@ -388,9 +388,9 @@ To migrate, use the memory store, remove format parameters, and update code to w
 
 ### Vector store API from positional to named arguments
 
-All vector store methods now use named arguments instead of positional arguments. This change improves code readability and makes method signatures more maintainable.
+All vector store methods now use an arguments object instead of positional arguments. This makes each value's purpose visible at the call site and lets method signatures evolve without relying on argument order.
 
-To migrate, update all vector store method calls to use named arguments.
+To migrate, update all vector store method calls to use an arguments object.
 
 ```diff
 - await vectorDB.createIndex(indexName, 3, 'cosine');
@@ -417,9 +417,9 @@ To migrate, update all vector store method calls to use named arguments.
 
 ### Vector store method renames
 
-The `updateIndexById` and `deleteIndexById` methods have been renamed to `updateVector` and `deleteVector` respectively. This change provides clearer naming that better describes the operations.
+The `updateIndexById` and `deleteIndexById` methods have been renamed to `updateVector` and `deleteVector` respectively. The new names identify that these methods operate on vectors.
 
-To migrate, rename the methods and use named arguments.
+To migrate, rename the methods and pass an arguments object.
 
 ```diff
 - await vectorDB.updateIndexById(indexName, id, update);
@@ -449,9 +449,9 @@ To migrate, pass the connection string as an object property.
 
 ### PGVector `defineIndex` to `buildIndex`
 
-The `defineIndex()` method has been removed in favor of `buildIndex()`. This change provides clearer naming for the index building operation.
+The `defineIndex()` method has been removed in favor of `buildIndex()`, which identifies that the method builds an index.
 
-To migrate, rename the method and use named arguments.
+To migrate, rename the method and pass an arguments object.
 
 ```diff
 - await vectorDB.defineIndex(indexName, 'cosine', { type: 'flat' });
@@ -464,7 +464,7 @@ To migrate, rename the method and use named arguments.
 
 ### `PostgresStore`: `schema` to `schemaName`
 
-The `schema` parameter has been renamed to `schemaName` in the PostgresStore constructor. This change provides clearer naming to avoid confusion with database schema concepts.
+The `schema` parameter has been renamed to `schemaName` in the PostgresStore constructor. The new name identifies the value as the database schema's name.
 
 To migrate, rename the parameter.
 
@@ -521,7 +521,7 @@ To migrate, use paginated methods via domain stores. For fetching all records, u
 
 ### `getTraces` and `getTracesPaginated`
 
-The `getTraces()` and `getTracesPaginated()` methods have been removed from storage. Traces are now handled through the observability package rather than core storage. This change provides better separation of concerns between core storage and observability features.
+The `getTraces()` and `getTracesPaginated()` methods have been removed from storage. Use the observability package to access traces instead of core storage.
 
 To migrate, use observability storage methods instead.
 

package/.docs/guides/migrations/upgrade-to-v1/tools.md

@@ -8,9 +8,9 @@ Tool execution signatures have been updated to use separate input and context pa
 
 ### `createTool` execute signature to `(inputData, context)` format
 
-All `createTool` execute functions now use a new signature with separate `inputData` and `context` parameters instead of a single destructured object. This change provides clearer separation between tool inputs and execution context.
+All `createTool` execute functions now use a signature with separate `inputData` and `context` parameters instead of a single destructured object. Tool inputs and execution context are now passed independently.
 
-**Note:** This change only applies to `createTool`. If you're using `createStep` for workflows, the signature remains `async (inputData, context)` and doesn't need to be changed.
+This signature change only applies to `createTool`. For workflow `createStep` calls, keep the `async (inputData, context)` signature.
 
 To migrate, update `createTool` signatures to use `inputData` as the first parameter (typed from `inputSchema`) and `context` as the second parameter.
 
@@ -88,7 +88,7 @@ To skip the `suspendSchema` or `resumeSchema` validation, don't define `suspendS
 
 ### `RuntimeContext` to `RequestContext`
 
-The `RuntimeContext` class has been renamed to `RequestContext` throughout the tool execution context. This change provides clearer naming that better describes its purpose as request-specific data.
+The `RuntimeContext` class has been renamed to `RequestContext` throughout the tool execution context. The new name identifies the class as request-specific data.
 
 To migrate, update references from `runtimeContext` to `requestContext` in tool execution functions.
 

package/.docs/guides/migrations/upgrade-to-v1/tracing.md

@@ -6,9 +6,9 @@ The observability system has been restructured in v1 with a dedicated `@mastra/o
 
 > **Observability data stops flowing on upgrade:** If you upgrade Mastra packages to v1 without migrating your `telemetry:` config to `observability:`, the old config is ignored at runtime. Your service will start cleanly with no error, but **no traces, logs, or metrics will be sent anywhere**. If you were sending data to Mastra Cloud, the dashboard will go empty.
 >
-> Complete this migration in the same change that bumps your Mastra packages, and verify traces appear in [Mastra Studio](https://mastra.ai/docs/studio/observability) before considering the upgrade complete. If you previously hosted on Mastra Cloud, also follow the [Mastra Cloud migration guide](https://mastra.ai/guides/migrations/mastra-cloud) — the new platform requires a new access token and a Studio project before `MastraPlatformExporter` can route data to it.
+> Complete this migration in the same change that bumps your Mastra packages, and verify traces appear in [Mastra Studio](https://mastra.ai/docs/studio/observability) before considering the upgrade complete. If you previously hosted on Mastra Cloud, also follow the [Mastra Cloud migration guide](https://mastra.ai/guides/migrations/mastra-cloud). The new platform requires a new access token and a Studio project before `MastraPlatformExporter` can route data to it.
 
-> **Exporter rename:** `MastraPlatformExporter` (sends data to Mastra platform) replaces the previous `CloudExporter`, and `MastraStorageExporter` (persists data to Mastra Storage) replaces the previous `DefaultExporter`. The original classes still ship from `@mastra/observability` and behave identically, but they're deprecated. New code should use `MastraPlatformExporter` and `MastraStorageExporter`; existing imports of `CloudExporter`/`DefaultExporter` continue to work until they're removed in a future major version.
+> **Exporter rename:** `MastraPlatformExporter` (sends data to Mastra platform) replaces the previous `CloudExporter`, and `MastraStorageExporter` (persists data to Mastra Storage) replaces the previous `DefaultExporter`. The original classes remain available from `@mastra/observability` and behave identically, but they're deprecated. New code should use `MastraPlatformExporter` and `MastraStorageExporter`. Existing imports of `CloudExporter` or `DefaultExporter` continue to work until they're removed in a future major version.
 
 ## Migration paths
 

package/.docs/guides/migrations/upgrade-to-v1/voice.md

@@ -8,7 +8,7 @@ Voice packages have been renamed from speech to voice with updated class names a
 
 ### Voice configuration property names
 
-Voice configuration properties have been renamed for consistency. `speakProvider` is now `output`, `listenProvider` is now `input`, and `realtimeProvider` is now `realtime`. This change provides more intuitive property names.
+Voice configuration properties have been renamed for consistency. `speakProvider` is now `output`, `listenProvider` is now `input`, and `realtimeProvider` is now `realtime`. The new names match each property's role in voice input and output.
 
 To migrate, update configuration property names when configuring agents with voice capabilities.
 

package/.docs/guides/migrations/upgrade-to-v1/workflows.md

@@ -65,7 +65,7 @@ To migrate, rename method calls from `createRunAsync` to `createRun`.
 
 ### `runCount` to `retryCount` (deprecated)
 
-The `runCount` parameter has been deprecated in favor of `retryCount` in workflow step execution. This change provides clearer naming that better describes retry behavior. The old `runCount` still works but shows deprecation warnings.
+The `runCount` parameter has been deprecated in favor of `retryCount` in workflow step execution. The new name identifies the value as the number of retries. The old `runCount` still works but shows deprecation warnings.
 
 To migrate, rename `runCount` to `retryCount` in step execution functions.
 

package/.docs/guides/migrations/vnext-to-standard-apis.md

@@ -161,7 +161,7 @@ The following options are available in the standard `.stream()` and `generate()`
           name: z.string(),
           age: z.number(),
         }),
-        model: 'openai/gpt-5.5', // Optional model override for structuring
+        model: 'openai/gpt-5.6-sol', // Optional model override for structuring
         errorStrategy: 'fallback',
         fallbackValue: { name: 'unknown', age: 0 },
         instructions: 'Extract user information', // Override default structuring instructions
@@ -299,7 +299,7 @@ The following options are available in the standard `.stream()` and `generate()`
       schema: z.object({
         summary: z.string(),
       }),
-      model: 'openai/gpt-5.5',
+      model: 'openai/gpt-5.6-sol',
     },
   })
   ```

package/.docs/models/environment-variables.md

@@ -89,6 +89,7 @@ List of required environment variables for each model provider and gateway suppo
 | [Mistral](https://mastra.ai/models/providers/mistral)                                          | `mistral/*`                | `MISTRAL_API_KEY`                                                                                     |
 | [Mixlayer](https://mastra.ai/models/providers/mixlayer)                                        | `mixlayer/*`               | `MIXLAYER_API_KEY`                                                                                    |
 | [Moark](https://mastra.ai/models/providers/moark)                                              | `moark/*`                  | `MOARK_API_KEY`                                                                                       |
+| [Modal](https://mastra.ai/models/providers/modal)                                              | `modal/*`                  | `MODAL_PROXY_TOKEN`                                                                                   |
 | [Model Oracle AI](https://mastra.ai/models/providers/model-oracle-ai)                          | `model-oracle-ai/*`        | `MODEL_ORACLE_API_KEY`                                                                                |
 | [ModelScope](https://mastra.ai/models/providers/modelscope)                                    | `modelscope/*`             | `MODELSCOPE_API_KEY`                                                                                  |
 | [Moonshot AI](https://mastra.ai/models/providers/moonshotai)                                   | `moonshotai/*`             | `MOONSHOT_API_KEY`                                                                                    |

package/.docs/models/gateways/custom-gateways.md

@@ -35,7 +35,7 @@ const myPrivateGateway: MastraModelGatewayInterface = {
     return {
       'my-provider': {
         name: 'My Provider',
-        models: ['openai/gpt-5.5'],
+        models: ['openai/gpt-5.6-sol'],
         apiKeyEnvVar: 'MY_API_KEY',
         gateway: 'private',
         url: 'https://api.myprovider.com/v1',
@@ -81,7 +81,7 @@ class MyPrivateGateway extends MastraModelGateway {
     return {
       'my-provider': {
         name: 'My Provider',
-        models: ['openai/gpt-5.5', 'anthropic/claude-sonnet-4-6'],
+        models: ['openai/gpt-5.6-sol', 'anthropic/claude-sonnet-4-6'],
         apiKeyEnvVar: 'MY_API_KEY',
         gateway: this.id,
         url: 'https://api.myprovider.com/v1',
@@ -192,7 +192,7 @@ const agent = new Agent({
   id: 'my-agent',
   name: 'My Agent',
   instructions: 'You are a helpful assistant',
-  model: 'private/my-provider/openai/gpt-5.5', // Uses MyPrivateGateway
+  model: 'private/my-provider/openai/gpt-5.6-sol', // Uses MyPrivateGateway
 });
 
 mastra.addAgent(agent, 'myAgent');

package/.docs/models/gateways/openrouter.md

@@ -2,7 +2,7 @@
 
 # ![OpenRouter logo](https://models.dev/logos/openrouter.svg)OpenRouter
 
-OpenRouter aggregates models from multiple providers with enhanced features like rate limiting and failover. Access 340 models through Mastra's model router.
+OpenRouter aggregates models from multiple providers with enhanced features like rate limiting and failover. Access 338 models through Mastra's model router.
 
 Learn more in the [OpenRouter documentation](https://openrouter.ai/models).
 
@@ -282,8 +282,6 @@ ANTHROPIC_API_KEY=ant-...
 | `perplexity/sonar-pro`                                     |
 | `perplexity/sonar-pro-search`                              |
 | `perplexity/sonar-reasoning-pro`                           |
-| `poolside/laguna-m.1`                                      |
-| `poolside/laguna-m.1:free`                                 |
 | `poolside/laguna-s-2.1`                                    |
 | `poolside/laguna-s-2.1:free`                               |
 | `poolside/laguna-xs-2.1`                                   |

package/.docs/models/gateways/vercel.md

@@ -2,7 +2,7 @@
 
 # ![Vercel logo](https://models.dev/logos/vercel.svg)Vercel
 
-Vercel aggregates models from multiple providers with enhanced features like rate limiting and failover. Access 306 models through Mastra's model router.
+Vercel aggregates models from multiple providers with enhanced features like rate limiting and failover. Access 307 models through Mastra's model router.
 
 Learn more in the [Vercel documentation](https://ai-sdk.dev/providers/ai-sdk-providers).
 
@@ -61,6 +61,7 @@ ANTHROPIC_API_KEY=ant-...
 | `alibaba/qwen3.5-plus`                   |
 | `alibaba/qwen3.6-27b`                    |
 | `alibaba/qwen3.6-plus`                   |
+| `alibaba/qwen3.7-flash`                  |
 | `alibaba/qwen3.7-max`                    |
 | `alibaba/qwen3.7-plus`                   |
 | `alibaba/wan-v2.5-t2v-preview`           |

package/.docs/models/index.md

@@ -2,7 +2,7 @@
 
 # Model Providers
 
-Mastra provides a unified interface for working with LLMs across multiple providers, giving you access to 5115 models from 162 providers through a single API.
+Mastra provides a unified interface for working with LLMs across multiple providers, giving you access to 5118 models from 163 providers through a single API.
 
 ## Features
 
@@ -29,7 +29,7 @@ const agent = new Agent({
   id: "my-agent",
   name: "My Agent",
   instructions: "You are a helpful assistant",
-  model: "openai/gpt-5.5"
+  model: "openai/gpt-5.6-sol"
 })
 ```
 
@@ -110,7 +110,7 @@ const documentProcessor = new Agent({
   id: "document-processor",
   name: "Document Processor",
   instructions: "Extract and summarize key information from documents",
-  model: "openai/gpt-5.5"
+  model: "openai/gpt-5.6-sol"
 })
 
 // Use a powerful reasoning model for complex analysis
@@ -160,7 +160,7 @@ const planner = new Agent({
       openai: { reasoningEffort: "low" }
     }
   },
-  model: "openai/gpt-5.5",
+  model: "openai/gpt-5.6-sol",
 });
 
 const lowEffort =
@@ -187,7 +187,7 @@ const agent = new Agent({
   id: "custom-agent",
   name: "Custom Agent",
   model: {
-    id: "openai/gpt-5.5",
+    id: "openai/gpt-5.6-sol",
     apiKey: process.env.OPENAI_API_KEY,
     headers: {
       "OpenAI-Organization": "org-abc123"
@@ -211,7 +211,7 @@ const agent = new Agent({
   instructions: 'You are a helpful assistant.',
   model: [
     {
-      model: "openai/gpt-5.5",
+      model: "openai/gpt-5.6-sol",
       maxRetries: 3,
     },
     {

package/.docs/models/providers/baseten.md

@@ -48,7 +48,7 @@ for await (const chunk of stream) {
 | `baseten/zai-org/GLM-4.7`                          | 200K    |       |           |       |       |       | $0.60      | $2          |
 | `baseten/zai-org/GLM-5`                            | 203K    |       |           |       |       |       | $0.95      | $3          |
 | `baseten/zai-org/GLM-5.1`                          | 203K    |       |           |       |       |       | $1         | $4          |
-| `baseten/zai-org/GLM-5.2`                          | 524K    |       |           |       |       |       | $1         | $4          |
+| `baseten/zai-org/GLM-5.2`                          | 1.0M    |       |           |       |       |       | $1         | $4          |
 | `baseten/zai-org/GLM-5.2-Fast`                     | 524K    |       |           |       |       |       | $2         | $7          |
 
 ## Advanced configuration

package/.docs/models/providers/chutes.md

@@ -2,7 +2,7 @@
 
 # ![Chutes logo](https://models.dev/logos/chutes.svg)Chutes
 
-Access 14 Chutes models through Mastra's model router. Authentication is handled automatically using the `CHUTES_API_KEY` environment variable.
+Access 15 Chutes models through Mastra's model router. Authentication is handled automatically using the `CHUTES_API_KEY` environment variable.
 
 Learn more in the [Chutes documentation](https://llm.chutes.ai).
 
@@ -41,6 +41,7 @@ for await (const chunk of stream) {
 | `chutes/MiniMaxAI/MiniMax-M2.5-TEE`             | 197K    |       |           |       |       |       | $0.15      | $1          |
 | `chutes/moonshotai/Kimi-K2.5-TEE`               | 262K    |       |           |       |       |       | $0.44      | $2          |
 | `chutes/moonshotai/Kimi-K2.6-TEE`               | 262K    |       |           |       |       |       | $0.66      | $4          |
+| `chutes/moonshotai/Kimi-K3-TEE`                 | 1.0M    |       |           |       |       |       | $3         | $15         |
 | `chutes/Nemotron-3-Nano-Omni-30B-TEE`           | 131K    |       |           |       |       |       | $0.02      | $0.10       |
 | `chutes/Qwen/Qwen3-235B-A22B-Thinking-2507-TEE` | 262K    |       |           |       |       |       | $0.30      | $1          |
 | `chutes/Qwen/Qwen3-32B-TEE`                     | 41K     |       |           |       |       |       | $0.10      | $0.42       |

package/.docs/models/providers/crossmodel.md

@@ -68,8 +68,8 @@ for await (const chunk of stream) {
 | `crossmodel/openai/gpt-5.6-terra`          | 1.1M    |       |           |       |       |       | $3         | $15         |
 | `crossmodel/qwen/qwen3.6-flash`            | 1.0M    |       |           |       |       |       | $0.19      | $1          |
 | `crossmodel/qwen/qwen3.6-plus`             | 1.0M    |       |           |       |       |       | $0.32      | $2          |
-| `crossmodel/qwen/qwen3.7-max`              | 1.0M    |       |           |       |       |       | $2         | $6          |
-| `crossmodel/qwen/qwen3.7-plus`             | 1.0M    |       |           |       |       |       | $0.32      | $1          |
+| `crossmodel/qwen/qwen3.7-max`              | 1.0M    |       |           |       |       |       | $2         | $5          |
+| `crossmodel/qwen/qwen3.7-plus`             | 1.0M    |       |           |       |       |       | $0.29      | $1          |
 | `crossmodel/tencent/hy3`                   | 262K    |       |           |       |       |       | $0.16      | $0.64       |
 | `crossmodel/tencent/hy3-preview`           | 262K    |       |           |       |       |       | $0.19      | $0.63       |
 | `crossmodel/x-ai/grok-4.3`                 | 1.0M    |       |           |       |       |       | $1         | $3          |

package/.docs/models/providers/deepinfra.md

@@ -62,7 +62,7 @@ for await (const chunk of stream) {
 | `deepinfra/Qwen/Qwen3.5-397B-A17B`                            | 262K    |       |           |       |       |       | $0.45      | $3          |
 | `deepinfra/Qwen/Qwen3.5-9B`                                   | 262K    |       |           |       |       |       | $0.10      | $0.15       |
 | `deepinfra/Qwen/Qwen3.6-27B`                                  | 262K    |       |           |       |       |       | $0.32      | $3          |
-| `deepinfra/Qwen/Qwen3.6-35B-A3B`                              | 262K    |       |           |       |       |       | $0.15      | $0.95       |
+| `deepinfra/Qwen/Qwen3.6-35B-A3B`                              | 262K    |       |           |       |       |       | $0.10      | $0.95       |
 | `deepinfra/Qwen/Qwen3.7-Max`                                  | 256K    |       |           |       |       |       | $3         | $8          |
 | `deepinfra/XiaomiMiMo/MiMo-V2.5`                              | 262K    |       |           |       |       |       | $0.40      | $2          |
 | `deepinfra/XiaomiMiMo/MiMo-V2.5-Pro`                          | 1.0M    |       |           |       |       |       | $1         | $3          |

package/.docs/models/providers/hyper.md

@@ -38,17 +38,17 @@ for await (const chunk of stream) {
 | ---------------------------------------------------- | ------- | ----- | --------- | ----- | ----- | ----- | ---------- | ----------- |
 | `hyper/deepseek-v4-flash`                            | 1.0M    |       |           |       |       |       | $0.20      | $0.40       |
 | `hyper/deepseek-v4-pro`                              | 1.0M    |       |           |       |       |       | $2         | $5          |
-| `hyper/gemma-4-26b-a4b-it`                           | 256K    |       |           |       |       |       | $0.13      | $0.42       |
+| `hyper/gemma-4-26b-a4b-it`                           | 256K    |       |           |       |       |       | $0.12      | $0.41       |
 | `hyper/glm-5`                                        | 203K    |       |           |       |       |       | $0.81      | $3          |
 | `hyper/glm-5.1`                                      | 203K    |       |           |       |       |       | $2         | $5          |
 | `hyper/glm-5.2`                                      | 1.0M    |       |           |       |       |       | $1         | $4          |
-| `hyper/gpt-oss-120b`                                 | 131K    |       |           |       |       |       | $0.18      | $0.65       |
+| `hyper/gpt-oss-120b`                                 | 131K    |       |           |       |       |       | $0.18      | $0.68       |
 | `hyper/kimi-k2.5`                                    | 262K    |       |           |       |       |       | $0.53      | $3          |
 | `hyper/kimi-k2.6`                                    | 262K    |       |           |       |       |       | $0.95      | $4          |
 | `hyper/kimi-k2.7-code`                               | 256K    |       |           |       |       |       | $0.95      | $4          |
 | `hyper/llama-3.3-70b-instruct`                       | 128K    |       |           |       |       |       | $0.61      | $1          |
 | `hyper/llama-4-maverick-17b-128e-instruct-fp8`       | 430K    |       |           |       |       |       | $0.28      | $0.93       |
-| `hyper/minimax-m2.7`                                 | 205K    |       |           |       |       |       | $0.35      | $1          |
+| `hyper/minimax-m2.7`                                 | 205K    |       |           |       |       |       | $0.41      | $2          |
 | `hyper/qwen3-coder-480b-a35b-instruct-int4-mixed-ar` | 106K    |       |           |       |       |       | $0.57      | $2          |
 | `hyper/qwen3-next-80b-a3b-instruct`                  | 262K    |       |           |       |       |       | $0.12      | $1          |
 | `hyper/qwen3.6-flash`                                | 1.0M    |       |           |       |       |       | $1         | $4          |

package/.docs/models/providers/llmgateway.md

@@ -2,7 +2,7 @@
 
 # ![LLM Gateway logo](https://models.dev/logos/llmgateway.svg)LLM Gateway
 
-Access 185 LLM Gateway models through Mastra's model router. Authentication is handled automatically using the `LLMGATEWAY_API_KEY` environment variable.
+Access 186 LLM Gateway models through Mastra's model router. Authentication is handled automatically using the `LLMGATEWAY_API_KEY` environment variable.
 
 Learn more in the [LLM Gateway documentation](https://llmgateway.io/docs).
 
@@ -200,9 +200,9 @@ for await (const chunk of stream) {
 | `llmgateway/qwen3-max`                         | 262K    |       |           |       |       |       | $0.84      | $3          |
 | `llmgateway/qwen3-next-80b-a3b-instruct`       | 131K    |       |           |       |       |       | $0.15      | $1          |
 | `llmgateway/qwen3-next-80b-a3b-thinking`       | 131K    |       |           |       |       |       | $0.15      | $1          |
-| `llmgateway/qwen3-vl-235b-a22b-instruct`       | 131K    |       |           |       |       |       | $0.30      | $2          |
+| `llmgateway/qwen3-vl-235b-a22b-instruct`       | 262K    |       |           |       |       |       | $0.20      | $0.88       |
 | `llmgateway/qwen3-vl-235b-a22b-thinking`       | 131K    |       |           |       |       |       | $0.98      | $4          |
-| `llmgateway/qwen3-vl-30b-a3b-instruct`         | 131K    |       |           |       |       |       | $0.20      | $0.70       |
+| `llmgateway/qwen3-vl-30b-a3b-instruct`         | 262K    |       |           |       |       |       | $0.15      | $0.60       |
 | `llmgateway/qwen3-vl-flash`                    | 262K    |       |           |       |       |       | $0.05      | $0.40       |
 | `llmgateway/qwen3-vl-plus`                     | 262K    |       |           |       |       |       | $0.20      | $2          |
 | `llmgateway/qwen3.5-9b`                        | 262K    |       |           |       |       |       | $0.10      | $0.15       |
@@ -210,6 +210,7 @@ for await (const chunk of stream) {
 | `llmgateway/qwen3.6-flash`                     | 262K    |       |           |       |       |       | $0.15      | $0.90       |
 | `llmgateway/qwen3.6-max-preview`               | 262K    |       |           |       |       |       | $1         | $8          |
 | `llmgateway/qwen3.6-plus`                      | 262K    |       |           |       |       |       | $0.50      | $3          |
+| `llmgateway/qwen3.7-flash`                     | 1.0M    |       |           |       |       |       | $0.03      | $0.13       |
 | `llmgateway/qwen3.7-max`                       | 1.0M    |       |           |       |       |       | $1         | $4          |
 | `llmgateway/qwen3.7-plus`                      | 1.0M    |       |           |       |       |       | $0.40      | $2          |
 | `llmgateway/qwen35-397b-a17b`                  | 262K    |       |           |       |       |       | $0.60      | $4          |