> For the complete documentation index, see [llms.txt](https://vibemx.gitbook.io/neuronai-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vibemx.gitbook.io/neuronai-studio/integration/stream-adapters.md).

# Stream Adapters

NeuronAI Studio allows you to expose agents and workflows to external frontend applications (React, Next.js, Vue, mobile apps) using dedicated wire-protocol streaming endpoints.

## Config

External integration is configured in `config/neuronai-studio.php`:

```php
'stream_adapters' => [
    'enabled' => env('NEURONAI_STUDIO_INTEGRATE_ENABLED', true),
    'route_prefix' => env('NEURONAI_STUDIO_INTEGRATE_PREFIX', 'api/neuronai'),
    'middleware' => ['api'], // Override as needed, e.g. ['api', 'auth:sanctum']
    'protocols' => [
        'vercel' => ['enabled' => true],
        'agui' => ['enabled' => true],
    ],
],
```

## Available Endpoints

When `stream_adapters.enabled` is set to `true`, the following integration endpoints are registered:

| Method | Endpoint                                              | Description                           |
| ------ | ----------------------------------------------------- | ------------------------------------- |
| `POST` | `{prefix}/agents/{agent}/stream/{protocol}`           | Stream an Agent response              |
| `POST` | `{prefix}/workflows/{workflow}/stream/{protocol}`     | Stream a Workflow execution           |
| `POST` | `{prefix}/workflows/traces/{trace}/resume/{protocol}` | Resume a paused Workflow (Human node) |

Supported `{protocol}` values: `vercel`, `agui`.

## Architecture Isolation

The external integration routes are completely separate from the internal Studio UI and playground. They run under their own prefix and middleware, allowing you to secure external client access (e.g. with `auth:sanctum` or API tokens) without affecting the Studio administration dashboard.

### Studio playground vs end-user chat

| Surface                          | Protocol                                                      | UI                                                                                                    |
| -------------------------------- | ------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| Studio Playground                | Internal Studio SSE (`token`, `tool_*`, workflow step events) | Custom React shell (`studio-chat`)                                                                    |
| Host app / public chat (planned) | `vercel` or `agui` adapters                                   | Prefer a market harness such as **assistant-ui** on Vercel AI SDK `useChat`, or a native AG-UI client |

The **same runners** back both paths. The playground validates agent/workflow behavior for Studio users; a future shareable/embed chat should speak the integrate adapters so web, mobile, and desktop clients stay portable without forking Studio SSE.

## Next Steps

* [Vercel AI SDK Integration Guide](/neuronai-studio/integration/vercel-ai-sdk.md)
* [AG-UI Protocol Guide](/neuronai-studio/integration/ag-ui.md)
* [Playground & Threads](/neuronai-studio/agents/playground-and-threads.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://vibemx.gitbook.io/neuronai-studio/integration/stream-adapters.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.