# Demand from the agent and get a streamed response until it finishes

Requests Wabee AI Agent to answer a question regarding the mission that the agent was given to upon creation.
    
    The agent can make use of any of the available tools along with its own reasoning to complete the given task, depending on its complexity, the response might take some time to be returned to the user.
    
    Note: session_id field on request body is kept for compatibility purposes, it will be overwritten with the header value during request processing
    Note: stream filed on request body is kept for compatibility purposes, it will be ignored during request processing
    Note: this is pretty much the same as in /chain, the only difference is that this endpoint returns a streaming response instead of a JSON object
    Note: the id on the streamming response refers to the current request
    Note: the streamming response ends when finish_reason is different than null
    Note: All headers starting with stix will be sent as context for tools.

Endpoint: POST /core/v1/chain_streaming
Version: v1
Security: APIKeyHeader

## Header parameters:

  - `session-id` (any)
    Session unique identifier, used to keep track of previous interations and enhanced observability. We recommend using a UUID string.

  - `request-id` (any)
    Custom request unique identifier, if not provided a new one will be generated. We recommend using a UUID string.

## Request fields (application/json):

  - `messages` (array, required)
    List of messages to be processed by the agent
    Example: [{"content":"What is the economic outlook?","role":"user"}]

  - `messages.role` (string, required)
    defines the role associated with the message
    Example: "assistant"

  - `messages.content` (string, required)
    message content
    Example: "Hello, I am your virtual assistant"

  - `data_filter_hints` (any)
    Special metadata-like hints to be passed to the agent in order to instruct him on how to filter the data on some tools that support filter
    Example: [{"filter_key":"unitname","filter_type":"equals","filter_value":"Unit 1","tool_name":"bubble_data"}]

  - `auto_memory_retain` (boolean)
    Indicates whether the agent should automatically retain information from the session in memory. When enabled, allows the agent to learn from experiences and feedback.

  - `context_files` (any)
    The path for files which the agent already has access to and should be considered by it when processing the messages
    Example: ["inputs/chat-files/test123/file.pdf"]

  - `images` (any)
    List of images associated with the message

## Response 401 fields (application/json):

  - `body` (string, required)
    Error message or description

  - `status_code` (integer, required)
    HTTP status code
    Example: 400

  - `details` (any)
    Additional error details if available

## Response 403 fields (application/json):

  - `body` (string, required)
    Error message or description

  - `status_code` (integer, required)
    HTTP status code
    Example: 400

  - `details` (any)
    Additional error details if available

## Response 413 fields (application/json):

  - `body` (string, required)
    Error message or description

  - `status_code` (integer, required)
    HTTP status code
    Example: 400

  - `details` (any)
    Additional error details if available

## Response 422 fields (application/json):

  - `body` (string, required)
    Error message or description

  - `status_code` (integer, required)
    HTTP status code
    Example: 400

  - `details` (any)
    Additional error details if available

## Response 500 fields (application/json):

  - `body` (string, required)
    Error message or description

  - `status_code` (integer, required)
    HTTP status code
    Example: 400

  - `details` (any)
    Additional error details if available


## Response 200 fields