Documentation Menu

Orchestration Layer

Orchestration is not a standalone model. It analyzes the incoming request, routes it to the right model or agent path, and combines partial results into a single response.

01 Flow02 Routing03 Advantages04 API05 Next

01How It Works

The decision flow first identifies the request type and difficulty, then selects the required models or agents. In the final stage, outputs pass through a consistency check and are returned as a single answer.

Decision flow

User Request

Intent, context, tool requirements, and output format are collected in one input.

Decision Engine

01
Complexity
02
Modality
03
Tool need

Unified Response

Selected step outputs are validated, simplified, and returned as one answer.

Birk-Fast
Activated when needed
Birk-Agent-Light
Activated when needed
Birk-Agent-Heavy
Activated when needed

02Routing Examples

The same endpoint can run different requests with different strategies. Simple work goes to a fast model; multi-step work goes to agents and pipeline structure.

01
“Translate this text into English.”
RouteBirk-Fast
ReasonThe fastest model is enough for a simple, single-step text transformation.
02
“Analyze the last 30 days of sales data and report the reasons.”
RouteBirk-Agent-Light
ReasonAn agent model is selected because SQL tooling, data reading, and mid-level analysis are required.
03
“Watch the meeting video, extract action items, and create follow-up tasks.”
RouteBirk-Agent-Heavy + Birk-Agent-Light
ReasonVideo understanding is assigned to the heavy model; task creation is assigned to a tool-using agent.
04
“Scan the codebase, find security issues, report them, and notify the team.”
RouteHeavy + Light + Fast
ReasonDeep analysis, tool execution, and concise summarization are split into separate steps.

03Why Orchestration?

Automatic Routing

Request complexity, modality, and tool requirements are read; the task is transferred to the most suitable model or agent path.

Cost Control

Simple work is not sent to heavy models. Each step runs with the most efficient capacity that is sufficient.

Parallel Execution

Independent subtasks run at the same time, and their results are combined into one response.

Single API

The integration side keeps one call; background selection and distribution are handled by the orchestration layer.

04API Usage

cURL
curl https://api.briqmind.com/v1/chat/completions \
  -H "Authorization: Bearer $BRIQ_API_KEY" \
  -d '{
    "workflow": "orchestration",
    "messages": [
      {
        "role": "user",
        "content": "Scan the codebase and produce a security report."
      }
    ]
  }'

orchestration is selected, model choice and task distribution are handled automatically.