TEKIZ.AI Fusion
One reviewed answer from several AI models.
Give Fusion a list of tasks that can run separately. Available models work on them in parallel, another model reviews the results, and your app receives one response.
Fusion is available on Pro and Max when worker and review models are online. A verified account may get a limited trial when one is offered.
Checking Fusion availability...
How it works
Run independent tasks in parallel.
Send numbered or bulleted tasks that can be checked separately. Fusion assigns them to available cloud or local models. A separate model reviews the work and returns one final answer. Unavailable services are skipped.
- Research: compare sources and tradeoffs.
- Implementation: assign small changes, then have another model review them.
- Agents: receive one response through the same API, with no new SDK.
curl "https://api.tekiz.ai/v1/chat/completions" \
-H "Authorization: Bearer sk_tekiz_..." \
-H "Content-Type: application/json" \
-d '{
"model": "tekizai/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
Call Fusion from an existing agent.
Gateway-style clients can attach tekizai: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": "tekizai/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": "tekizai:fusion"}],
"tool_choice": "required"
}
Access and privacy
Use only models you are allowed to use.
Hosted requests use TEKIZ.AI cloud models or approved Community nodes. Personal provider accounts are never shared with other customers.
- Hosted: Fusion runs only when both worker and review models are available.
- Local: use the same model alias with providers and local models you authorize.
- Privacy: logs keep request timing and route health, never prompts, model output, API keys, OAuth tokens, or provider credentials.