@mastra/mcp-docs-server 1.1.18-alpha.1 → 1.1.18

package/.docs/docs/memory/storage.md

@@ -14,7 +14,7 @@ export const mastra = new Mastra({
 })
 ```
 
-> **Sharing the database with Mastra Studio:** When running `mastra dev` alongside your application (e.g., Next.js), use an absolute path to ensure both processes access the same database:
+> **Sharing the database with Studio:** When running `mastra dev` alongside your application (e.g., Next.js), use an absolute path to ensure both processes access the same database:
 >
 > ```typescript
 > url: 'file:/absolute/path/to/your/project/mastra.db'
@@ -129,7 +129,7 @@ Mastra organizes conversations using two identifiers:
 
 Both identifiers are required for agents to store information:
 
-**Generate**:
+**.generate()**:
 
 ```typescript
 const response = await agent.generate('hello', {
@@ -140,7 +140,7 @@ const response = await agent.generate('hello', {
 })
 ```
 
-**Stream**:
+**.stream()**:
 
 ```typescript
 const stream = await agent.stream('hello', {
@@ -151,7 +151,7 @@ const stream = await agent.stream('hello', {
 })
 ```
 
-> **Note:** [Studio](https://mastra.ai/docs/getting-started/studio) automatically generates a thread and resource ID for you. When calling `stream()` or `generate()` yourself, remember to provide these identifiers explicitly.
+> **Note:** [Studio](https://mastra.ai/docs/studio/overview) automatically generates a thread and resource ID for you. When calling `stream()` or `generate()` yourself, remember to provide these identifiers explicitly.
 
 ### Thread title generation
 

package/.docs/docs/observability/metrics/overview.md

@@ -0,0 +1,114 @@
+# Metrics overview
+
+Mastra automatically emits performance and usage metrics from traced execution. There's no manual instrumentation needed. Metrics are derived from spans as they complete.
+
+Three categories of metrics are emitted automatically:
+
+- **Duration metrics**: Execution time for agents, workflows, tools, model calls, and processors.
+- **Token usage metrics**: Input and output token counts broken down by type (text, cache, audio, image, reasoning).
+- **Cost estimation**: Estimated cost per model call based on an embedded pricing registry.
+
+> **Note:** Metrics require a separate OLAP store for observability. Relational databases like PostgreSQL, LibSQL, etc. are not supported for metrics. In-memory storage resets on restart.
+>
+> For local development, you can use [DuckDB](https://mastra.ai/reference/vectors/duckdb). We don't recommend using in-memory/DuckDB for production, ClickHouse support is coming soon for scalable metrics storage.
+
+## When to use metrics
+
+- Monitor latency across agents, tools, workflows, and model calls
+- Track token consumption and cost trends over time
+- Identify error-heavy agents or tools by comparing success and error rates
+- Compare performance before and after prompt, model, or code changes
+
+## Get started
+
+Install the required packages:
+
+**npm**:
+
+```bash
+npm install @mastra/observability @mastra/libsql @mastra/duckdb
+```
+
+**pnpm**:
+
+```bash
+pnpm add @mastra/observability @mastra/libsql @mastra/duckdb
+```
+
+**Yarn**:
+
+```bash
+yarn add @mastra/observability @mastra/libsql @mastra/duckdb
+```
+
+**Bun**:
+
+```bash
+bun add @mastra/observability @mastra/libsql @mastra/duckdb
+```
+
+Then configure observability with a composite store that routes the observability domain to DuckDB:
+
+```ts
+import { Mastra } from '@mastra/core/mastra'
+import { LibSQLStore } from '@mastra/libsql'
+import { DuckDBStore } from '@mastra/duckdb'
+import { MastraCompositeStore } from '@mastra/core/storage'
+import { Observability, DefaultExporter, SensitiveDataFilter } from '@mastra/observability'
+
+export const mastra = new Mastra({
+  storage: new MastraCompositeStore({
+    id: 'composite-storage',
+    default: new LibSQLStore({
+      id: 'mastra-storage',
+      url: 'file:./mastra.db',
+    }),
+    domains: {
+      observability: await new DuckDBStore().getStore('observability'),
+    },
+  }),
+  observability: new Observability({
+    configs: {
+      default: {
+        serviceName: 'mastra',
+        exporters: [new DefaultExporter()],
+        spanOutputProcessors: [new SensitiveDataFilter()],
+      },
+    },
+  }),
+})
+```
+
+## Studio
+
+The Studio metrics dashboard visualizes all automatic metrics with KPI cards, detailed breakdowns, and configurable time ranges. See [Studio observability](https://mastra.ai/docs/studio/observability) for a full walkthrough.
+
+## What Mastra measures
+
+Mastra emits three categories of metrics automatically:
+
+- **Duration**: Execution time in milliseconds for agents, workflows, tools, model calls, and processors.
+- **Token usage**: Input and output token counts, broken down by type (text, cache, audio, image, reasoning).
+- **Cost estimation**: Estimated cost per model call, based on an embedded pricing registry.
+
+Each metric carries trace correlation context so you can drill from a dashboard spike to the exact span that caused it.
+
+For the full list of metric names, labels, and cost fields, see the [Automatic metrics reference](https://mastra.ai/reference/observability/metrics/automatic-metrics).
+
+## How automatic metrics work
+
+Mastra auto-instruments agent runs, workflow steps, tool calls, and model generations as spans. When a span ends, the observability layer extracts metrics from it:
+
+1. **Duration**: Calculated from the span's start and end timestamps.
+2. **Token usage**: Extracted from the `usage` attribute on model generation spans.
+3. **Cost estimation**: Runs each token metric through an embedded pricing registry that matches by provider and model name.
+
+Before storage, all metric labels pass through a cardinality filter that blocks known high-cardinality values (such as trace IDs and UUIDs) to keep storage efficient. Metrics are then batched by an internal event buffer and flushed to storage by the `DefaultExporter`.
+
+## Next steps
+
+- [Automatic metrics reference](https://mastra.ai/reference/observability/metrics/automatic-metrics)
+- [Tracing overview](https://mastra.ai/docs/observability/tracing/overview)
+- [Studio observability](https://mastra.ai/docs/studio/observability)
+- [Observability overview](https://mastra.ai/docs/observability/overview)
+- [DefaultExporter reference](https://mastra.ai/docs/observability/tracing/exporters/default)

package/.docs/docs/observability/overview.md

@@ -23,10 +23,12 @@ For production environments with high traffic, we recommend using **ClickHouse**
 
 Configure Observability in your Mastra instance:
 
-```typescript
-import { Mastra } from '@mastra/core'
+```ts
+import { Mastra } from '@mastra/core/mastra'
 import { PinoLogger } from '@mastra/loggers'
 import { LibSQLStore } from '@mastra/libsql'
+import { DuckDBStore } from '@mastra/duckdb'
+import { MastraCompositeStore } from '@mastra/core/storage'
 import {
   Observability,
   DefaultExporter,
@@ -36,9 +38,15 @@ import {
 
 export const mastra = new Mastra({
   logger: new PinoLogger(),
-  storage: new LibSQLStore({
-    id: 'mastra-storage',
-    url: 'file:./mastra.db', // Storage is required for tracing
+  storage: new MastraCompositeStore({
+    id: 'composite-storage',
+    default: new LibSQLStore({
+      id: 'mastra-storage',
+      url: 'file:./mastra.db',
+    }),
+    domains: {
+      observability: await new DuckDBStore().getStore('observability'),
+    },
   }),
   observability: new Observability({
     configs: {

package/.docs/docs/observability/tracing/exporters/default.md

@@ -58,7 +58,7 @@ export const mastra = new Mastra({
       default: {
         serviceName: 'mastra',
         exporters: [
-          new DefaultExporter(), // Persists traces to storage for Mastra Studio
+          new DefaultExporter(), // Persists traces to storage for Studio
           new CloudExporter(), // Sends traces to Mastra Cloud (requires MASTRA_CLOUD_ACCESS_TOKEN)
         ],
         spanOutputProcessors: [new SensitiveDataFilter()],
@@ -68,9 +68,7 @@ export const mastra = new Mastra({
 })
 ```
 
-## Viewing traces
-
-### Studio
+## Studio
 
 Access your traces through Studio:
 

package/.docs/docs/observability/tracing/exporters/laminar.md

@@ -7,25 +7,25 @@
 **npm**:
 
 ```bash
-npm install @mastra/laminar@beta
+npm install @mastra/laminar@latest
 ```
 
 **pnpm**:
 
 ```bash
-pnpm add @mastra/laminar@beta
+pnpm add @mastra/laminar@latest
 ```
 
 **Yarn**:
 
 ```bash
-yarn add @mastra/laminar@beta
+yarn add @mastra/laminar@latest
 ```
 
 **Bun**:
 
 ```bash
-bun add @mastra/laminar@beta
+bun add @mastra/laminar@latest
 ```
 
 ## Configuration

package/.docs/docs/observability/tracing/exporters/sentry.md

@@ -7,25 +7,25 @@
 **npm**:
 
 ```bash
-npm install @mastra/sentry@beta
+npm install @mastra/sentry@latest
 ```
 
 **pnpm**:
 
 ```bash
-pnpm add @mastra/sentry@beta
+pnpm add @mastra/sentry@latest
 ```
 
 **Yarn**:
 
 ```bash
-yarn add @mastra/sentry@beta
+yarn add @mastra/sentry@latest
 ```
 
 **Bun**:
 
 ```bash
-bun add @mastra/sentry@beta
+bun add @mastra/sentry@latest
 ```
 
 ## Configuration

package/.docs/docs/observability/tracing/overview.md

@@ -31,7 +31,7 @@ export const mastra = new Mastra({
       default: {
         serviceName: 'mastra',
         exporters: [
-          new DefaultExporter(), // Persists traces to storage for Mastra Studio
+          new DefaultExporter(), // Persists traces to storage for Studio
           new CloudExporter(), // Sends traces to Mastra Cloud (if MASTRA_CLOUD_ACCESS_TOKEN is set)
         ],
         spanOutputProcessors: [
@@ -55,7 +55,7 @@ This configuration includes:
 
 - **Exporters**:
 
-  - `DefaultExporter` - Persists traces to your configured storage for Mastra Studio
+  - `DefaultExporter` - Persists traces to your configured storage for Studio
   - `CloudExporter` - Sends traces to Mastra Cloud (requires `MASTRA_CLOUD_ACCESS_TOKEN`)
 
 - **Span Output Processors**: `SensitiveDataFilter` - Redacts sensitive fields

package/.docs/docs/rag/chunking-and-embedding.md

@@ -9,7 +9,7 @@ const docFromMarkdown = MDocument.fromMarkdown('# Your Markdown content...')
 const docFromJSON = MDocument.fromJSON(`{ "key": "value" }`)
 ```
 
-## Step 1: Document processing
+## Document processing
 
 Use `chunk` to split documents into manageable pieces. Mastra supports multiple chunking strategies optimized for different document types:
 
@@ -65,7 +65,7 @@ const chunks = await doc.chunk({
 
 We go deeper into chunking strategies in our [`chunk()` reference documentation](https://mastra.ai/reference/rag/chunk).
 
-## Step 2: Embedding generation
+## Embedding generation
 
 Transform chunks into embeddings using your preferred provider. Mastra supports embedding models through the model router.
 

package/.docs/docs/server/auth/composite-auth.md

@@ -225,10 +225,4 @@ function handleUser(user: User) {
     console.log('Clerk user:', user.email)
   }
 }
-```
-
-## Related
-
-- [Auth Overview](https://mastra.ai/docs/server/auth) - Authentication concepts
-- [Simple Auth](https://mastra.ai/docs/server/auth/simple-auth) - Token-to-user mapping
-- [Custom Auth Provider](https://mastra.ai/docs/server/auth/custom-auth-provider) - Build your own provider
+```

package/.docs/docs/server/auth/custom-auth-provider.md

@@ -507,7 +507,5 @@ See the [source code](https://github.com/mastra-ai/mastra/tree/main/auth) for im
 
 ## Related
 
-- [Auth Overview](https://mastra.ai/docs/server/auth) - Authentication concepts and configuration
-- [JWT Auth](https://mastra.ai/docs/server/auth/jwt) - Simple JWT authentication
-- [Clerk Auth](https://mastra.ai/docs/server/auth/clerk) - Clerk integration
-- [Custom API Routes](https://mastra.ai/docs/server/custom-api-routes) - Controlling authentication on custom endpoints
+- [Auth Overview](https://mastra.ai/docs/server/auth): Authentication concepts and configuration
+- [Custom API Routes](https://mastra.ai/docs/server/custom-api-routes): Controlling authentication on custom endpoints

package/.docs/docs/server/auth/jwt.md

@@ -61,7 +61,7 @@ export const mastra = new Mastra({
 
 > **Info:** Visit [MastraJwtAuth](https://mastra.ai/reference/auth/jwt) for all available configuration options.
 
-Inside [Studio](https://mastra.ai/docs/getting-started/studio), go to **Settings** and under **Headers** select the **"Add Header"** button. Enter `Authorization` as the header name and `Bearer <your-jwt>` as the value.
+Inside [Studio](https://mastra.ai/docs/studio/overview), go to **Settings** and under **Headers** select the **"Add Header"** button. Enter `Authorization` as the header name and `Bearer <your-jwt>` as the value.
 
 ## Configuring `MastraClient`
 

package/.docs/docs/server/auth/simple-auth.md

@@ -171,10 +171,4 @@ SimpleAuth is designed for simplicity, not production security:
 - No cryptographic verification
 - All tokens must be known at startup
 
-For production applications, consider using [JWT](https://mastra.ai/docs/server/auth/jwt), [Clerk](https://mastra.ai/docs/server/auth/clerk), [Auth0](https://mastra.ai/docs/server/auth/auth0), or another identity provider.
-
-## Related
-
-- [Auth Overview](https://mastra.ai/docs/server/auth) - Authentication concepts
-- [JWT Auth](https://mastra.ai/docs/server/auth/jwt) - JSON Web Token authentication
-- [Custom Auth Provider](https://mastra.ai/docs/server/auth/custom-auth-provider) - Build your own provider
+For production applications, consider using [JWT](https://mastra.ai/docs/server/auth/jwt), [Clerk](https://mastra.ai/docs/server/auth/clerk), [Auth0](https://mastra.ai/docs/server/auth/auth0), or another identity provider.

package/.docs/docs/server/auth.md

@@ -1,8 +1,8 @@
 # Auth overview
 
-Mastra lets you choose how you handle authentication, so you can secure access to your API and [Studio](https://mastra.ai/docs/getting-started/studio) using the identity system that fits your stack.
+Mastra lets you choose how you handle authentication, so you can secure access to your API and [Studio](https://mastra.ai/docs/studio/overview) using the identity system that fits your stack.
 
-You can start with basic shared secret JWT authentication and switch to providers like Supabase, Firebase Auth, Auth0, Clerk, or WorkOS when you need more advanced identity features.
+You can start with basic shared secret JWT authentication and switch to known providers when you need more advanced identity features.
 
 ## What auth secures
 
@@ -13,7 +13,7 @@ Configuring authentication locks down two things at once:
 
 Authentication is optional. If no auth is configured, all routes and Studio are publicly accessible. Public access can be enabled on individual custom routes using `requiresAuth: false`.
 
-See [Custom API Routes](https://mastra.ai/docs/server/custom-api-routes) for controlling authentication on custom endpoints.
+See [Custom API Routes](https://mastra.ai/docs/server/custom-api-routes) for controlling authentication on custom endpoints. Visit the [Studio Auth docs](https://mastra.ai/docs/studio/auth) for more on securing your Studio deployment.
 
 > **Note:** Authentication for Studio is currently supported by the following providers: Simple Auth, JWT, WorkOS, and Better Auth.
 

package/.docs/docs/server/custom-adapters.md

@@ -1,6 +1,6 @@
 # Custom adapters
 
-Create a custom adapter when you need to run Mastra with a framework other than Hono or Express. This might be necessary if you have specific request/response handling requirements that `@mastra/hono` and `@mastra/express` don't support.
+Create a custom adapter when the prebuilt server adapters (Hono, Express, Fastify, Koa) don't support your framework or you have specific request/response handling requirements.
 
 A custom adapter translates between Mastra's route definitions and your framework's routing system. You'll implement methods that register middleware, handle requests, and send responses using your framework's APIs.
 
@@ -368,6 +368,8 @@ app.listen(4111)
 ```
 
 > **Tip:** The existing [@mastra/hono](https://github.com/mastra-ai/mastra/blob/main/server-adapters/hono/src/index.ts) and [@mastra/express](https://github.com/mastra-ai/mastra/blob/main/server-adapters/express/src/index.ts) implementations are good references when building your custom adapter. They show how to handle framework-specific patterns for context storage, middleware registration, and response handling.
+>
+> If you want to use [Studio](https://mastra.ai/docs/studio/overview) with your server adapter, use [`mastra studio`](https://mastra.ai/reference/cli/mastra) to only launch the Studio UI.
 
 ## Related
 

package/.docs/docs/server/custom-api-routes.md

@@ -262,7 +262,7 @@ For more information about authentication providers, see the [Auth documentation
 
 ## Continue generation after client disconnect
 
-Built-in streaming helpers such as [`chatRoute()`](https://mastra.ai/reference/ai-sdk/chat-route) forward the incoming request's `AbortSignal` to `agent.stream()`. That is the right default when a browser disconnect should cancel the model call.
+Built-in streaming helpers such as [`chatRoute()`](https://mastra.ai/reference/ai-sdk/chat-route) forward the incoming request's `AbortSignal` to `agent.stream()`. That's the right default when a browser disconnect should cancel the model call.
 
 If you want the server to keep generating and persist the final response even after the client disconnects, build a custom route around the underlying `MastraModelOutput`. Start the agent stream without forwarding `c.req.raw.signal`, then call `consumeStream()` in the background so generation continues server-side.
 

package/.docs/docs/server/mastra-client.md

@@ -10,9 +10,7 @@ To ensure smooth local development, make sure you have:
 - TypeScript `v4.7` or higher (if using TypeScript)
 - Your local Mastra server running (typically on port `4111`)
 
-## Usage
-
-The Mastra Client SDK is designed for browser environments and uses the native `fetch` API for making HTTP requests to your Mastra server.
+> **Note:** The Mastra Client SDK is designed for browser environments and uses the native `fetch` API for making HTTP requests to your Mastra server.
 
 ## Installation
 

package/.docs/docs/server/mastra-server.md

@@ -43,6 +43,14 @@ export const mastra = new Mastra({
 - **[Mastra Client SDK](https://mastra.ai/docs/server/mastra-client)**: Type-safe client for calling agents, workflows, and tools from browser or server environments.
 - **[Authentication](https://mastra.ai/docs/server/auth)**: Secure endpoints with JWT, Clerk, Supabase, Firebase, Auth0, or WorkOS.
 
+## REST API
+
+You can explore all available endpoints in the OpenAPI specification at <http://localhost:4111/api/openapi.json>, which details every endpoint and its request and response schemas.
+
+To explore the API interactively, visit the Swagger UI at <http://localhost:4111/swagger-ui>. Here, you can discover endpoints and test them directly from your browser.
+
+> **Note:** The OpenAPI and Swagger endpoints are disabled in production by default. To enable them, set [`server.build.openAPIDocs`](https://mastra.ai/reference/configuration) and [`server.build.swaggerUI`](https://mastra.ai/reference/configuration) to `true` respectively.
+
 ## Stream data redaction
 
 When streaming agent responses, the HTTP layer redacts system prompts, tool definitions, API keys, and similar data from each chunk before sending it to clients. This is enabled by default.

package/.docs/docs/server/request-context.md

@@ -82,6 +82,23 @@ export const mastra = new Mastra({
 
 > **Info:** Visit [Middleware](https://mastra.ai/docs/server/middleware) for how to use server middleware.
 
+## Studio
+
+When developing locally, you can define named presets in a JSON file and load them into [Studio](https://mastra.ai/docs/studio/overview) with the [`--request-context-presets`](https://mastra.ai/reference/cli/mastra) CLI flag. This adds a dropdown to the request context editor in Studio so you can quickly switch between configurations without manually editing JSON each time.
+
+```bash
+mastra dev --request-context-presets ./presets.json
+```
+
+```json
+{
+  "development": { "userId": "dev-user", "env": "development" },
+  "production": { "userId": "prod-user", "env": "production" }
+}
+```
+
+When you select a preset from the dropdown, the JSON editor populates with that preset's values. Editing the JSON manually switches the dropdown back to **"Custom"**.
+
 ## Accessing values with agents
 
 You can access the `requestContext` argument from any supported configuration options in agents. These functions can be sync or `async`. Use the `.get()` method to read values from `requestContext`.
@@ -446,23 +463,6 @@ requestContextSchema: z.object({
 
 **Handle tool validation errors**: Since tools return error objects instead of throwing, check for errors in your agent or workflow logic when tool execution is critical.
 
-## Testing with Studio presets
-
-When developing locally, you can define named presets in a JSON file and load them into Studio with the [`--request-context-presets`](https://mastra.ai/reference/cli/mastra) CLI flag. This adds a dropdown to the request context editor in Studio so you can quickly switch between configurations without manually editing JSON each time.
-
-```bash
-mastra dev --request-context-presets ./presets.json
-```
-
-```json
-{
-  "development": { "userId": "dev-user", "env": "development" },
-  "production": { "userId": "prod-user", "env": "production" }
-}
-```
-
-When you select a preset from the dropdown, the JSON editor populates with that preset's values. Editing the JSON manually switches the dropdown back to "Custom".
-
 ## Related
 
 - [Agent Request Context](https://mastra.ai/docs/memory/overview)

package/.docs/docs/server/server-adapters.md

@@ -10,7 +10,7 @@ Server adapters let you run Mastra with your own HTTP server instead of the Hono
 
 > **Tip:** For deployments without custom server requirements, use `mastra build` instead. It configures server setup, registers middleware, and applies deployment settings based on your project configuration. See [Server Configuration](https://mastra.ai/docs/server/mastra-server).
 >
-> If you want to use [Studio](https://mastra.ai/docs/getting-started/studio) with your server adapter, use [`mastra studio`](https://mastra.ai/reference/cli/mastra) to only launch the Studio UI.
+> If you want to use [Studio](https://mastra.ai/docs/studio/overview) with your server adapter, use [`mastra studio`](https://mastra.ai/reference/cli/mastra) to only launch the Studio UI.
 
 ## Available adapters
 
@@ -553,10 +553,10 @@ See [MCP](https://mastra.ai/docs/mcp/overview) for configuration details and how
 
 ## Related
 
-- [Hono Adapter](https://mastra.ai/reference/server/hono-adapter) - Hono-specific setup
-- [Express Adapter](https://mastra.ai/reference/server/express-adapter) - Express-specific setup
-- [Custom Adapters](https://mastra.ai/docs/server/custom-adapters) - Building adapters for other frameworks
-- [Server Configuration](https://mastra.ai/docs/server/mastra-server) - Using `mastra build` instead
-- [Authentication](https://mastra.ai/docs/server/auth) - Configuring auth for your server
-- [MastraServer Reference](https://mastra.ai/reference/server/mastra-server) - Full API reference
-- [createRoute() Reference](https://mastra.ai/reference/server/create-route) - Creating type-safe custom routes
+- [Hono Adapter](https://mastra.ai/reference/server/hono-adapter): Hono-specific setup
+- [Express Adapter](https://mastra.ai/reference/server/express-adapter): Express-specific setup
+- [Custom Adapters](https://mastra.ai/docs/server/custom-adapters): Building adapters for other frameworks
+- [Server Configuration](https://mastra.ai/docs/server/mastra-server): Using `mastra build` instead
+- [Authentication](https://mastra.ai/docs/server/auth): Configuring auth for your server
+- [MastraServer Reference](https://mastra.ai/reference/server/mastra-server): Full API reference
+- [createRoute() Reference](https://mastra.ai/reference/server/create-route): Creating type-safe custom routes

package/.docs/docs/streaming/events.md

@@ -145,93 +145,4 @@ Each progress event includes:
 - **`totalCount`**: Total number of iterations
 - **`currentIndex`**: Index of the iteration that completed
 - **`iterationStatus`**: Status of the iteration (`success`, `failed`, or `suspended`)
-- **`iterationOutput`**: Output of the iteration (when successful)
-
-## Inspecting agent networks
-
-When using multi-agent collaboration with `agent.network()`, iterate over the stream to track how tasks are delegated and executed across agents, workflows, and tools.
-
-```typescript
-const networkAgent = mastra.getAgent('networkAgent')
-
-const networkStream = await networkAgent.network('Research dolphins then write a report')
-
-for await (const chunk of networkStream) {
-  console.log(chunk)
-}
-```
-
-> **Info:** Visit [Agent.network()](https://mastra.ai/reference/agents/network) for more information.
-
-### Example network output
-
-Network streams emit events that track the orchestration flow. Each iteration begins with routing, followed by execution of the selected primitive.
-
-```typescript
-// Routing agent decides what to do
-{
-  type: 'routing-agent-start',
-  from: 'NETWORK',
-  runId: '7a3b9c2d-1e4f-5a6b-8c9d-0e1f2a3b4c5d',
-  payload: {
-    agentId: 'routing-agent',
-    // ...
-  }
-}
-// Routing agent makes a selection
-{
-  type: 'routing-agent-end',
-  from: 'NETWORK',
-  runId: '7a3b9c2d-1e4f-5a6b-8c9d-0e1f2a3b4c5d',
-  payload: {
-    // ...
-  }
-}
-// Delegated agent begins execution
-{
-  type: 'agent-execution-start',
-  from: 'NETWORK',
-  runId: '8b4c0d3e-2f5a-6b7c-9d0e-1f2a3b4c5d6e',
-  payload: {
-    // ...
-  }
-}
-// Events from the delegated agent's execution
-{
-  type: 'agent-execution-event-text-delta',
-  from: 'NETWORK',
-  runId: '8b4c0d3e-2f5a-6b7c-9d0e-1f2a3b4c5d6e',
-  payload: {
-    type: 'text-delta',
-    payload: {
-      // ...
-    }
-  }
-}
-```
-
-### Filtering network events
-
-You can filter events by type to track specific aspects of the network execution:
-
-```typescript
-const networkStream = await networkAgent.network('Analyze data and create visualization')
-
-for await (const chunk of networkStream) {
-  // Track routing decisions
-  if (chunk.type === 'routing-agent-end') {
-    console.log('Selected:', chunk.payload.resourceType, chunk.payload.resourceId)
-    console.log('Reason:', chunk.payload.selectionReason)
-  }
-
-  // Track agent delegations
-  if (chunk.type === 'agent-execution-start') {
-    console.log('Delegating to agent:', chunk.payload.agentId)
-  }
-
-  // Track workflow delegations
-  if (chunk.type === 'workflow-execution-start') {
-    console.log('Executing workflow:', chunk.payload.name)
-  }
-}
-```
+- **`iterationOutput`**: Output of the iteration (when successful)

package/.docs/docs/streaming/overview.md

@@ -64,8 +64,6 @@ const stream = await testAgent.stream([{ role: 'user', content: 'Help me organiz
 
 // Convert to AI SDK v5+ compatible stream
 const aiSDKStream = toAISdkV5Stream(stream, { from: 'agent' })
-
-// Use with AI SDK v5+ methods
 ```
 
 For converting messages to AI SDK v5+ format, use the `toAISdkV5Messages()` utility from `@mastra/ai-sdk/ui`:
@@ -77,46 +75,6 @@ const messages = [{ role: 'user', content: 'Hello' }]
 const aiSDKMessages = toAISdkV5Messages(messages)
 ```
 
-### Using `Agent.network()`
-
-The `network()` method enables multi-agent collaboration by executing a network loop where multiple agents can work together to handle complex tasks. The routing agent delegates tasks to appropriate subagents, workflows, and tools based on the conversation context.
-
-> **Note**: This method is experimental and requires memory to be configured on the agent.
-
-```typescript
-const testAgent = mastra.getAgent('testAgent')
-
-const networkStream = await testAgent.network('Help me organize my day')
-
-for await (const chunk of networkStream) {
-  console.log(chunk)
-}
-```
-
-> **Info:** Visit [Agent.network()](https://mastra.ai/reference/agents/network) for more information.
-
-#### Network stream properties
-
-The network stream provides access to execution information:
-
-- **`networkStream.status`**: Promise resolving to the workflow execution status
-- **`networkStream.result`**: Promise resolving to the complete execution results
-- **`networkStream.usage`**: Promise resolving to token usage information
-
-```typescript
-const testAgent = mastra.getAgent('testAgent')
-
-const networkStream = await testAgent.network('Research dolphins then write a report')
-
-for await (const chunk of networkStream) {
-  console.log(chunk)
-}
-
-console.log('Final status:', await networkStream.status)
-console.log('Final result:', await networkStream.result)
-console.log('Token usage:', await networkStream.usage)
-```
-
 ## Streaming with workflows
 
 Streaming from a workflow returns a sequence of structured events describing the run lifecycle, rather than incremental text chunks. This event-based format makes it possible to track and respond to workflow progress in real time once a run is created using `.createRun()`.