Tekiz Fusion

A compact execution path

Parallelize bounded tasks.

Fusion fans out top-level numbered or bulleted items that can be independently checked. It can use faster cloud or local workers for those tasks, then an independent verifier returns the final answer. Unavailable or unauthorized routes are skipped.

• Research: compare sources and tradeoffs.
• Implementation: delegate bounded changes while a stronger route reviews them.
• Agents: receive one normal completion, with no new SDK.

curl "https://api.tekiz.ai/v1/chat/completions" \
  -H "Authorization: Bearer sk_sage_..." \
  -H "Content-Type: application/json" \
  -d '{
    "model": "sage-router/fusion",
    "messages": [
      {"role": "user", "content": "1. Compare the launch options against cost and delivery risk.\n2. Identify the two material implementation risks.\n3. Recommend one option with a concise rationale."}
    ]
  }'

For existing agents

Give Frontier explicit work to send through Fusion.

Gateway-style clients can attach sage-router:fusion without forwarding unknown tool markers downstream. Set tool_choice to required for explicit invocation, and use a short list when work can run independently.

{
  "model": "sage-router/frontier",
  "messages": [
    {"role": "user", "content": "1. Summarize the strongest case for this launch.\n2. Summarize the strongest case against it.\n3. Recommend a next step with the decision criteria."}
  ],
  "tools": [{"type": "sage-router:fusion"}],
  "tool_choice": "required"
}

Capacity and privacy

Routes stay within their authorization.

Hosted requests use dedicated cloud capacity or approved local capacity. Tekiz does not pool personal provider accounts or send work to routes the deployment is not authorized to use.