Kilo Gateway × WorkDaddy: LLM Provider Integration (2026)

Use Kilo Gateway as the engine behind your WorkDaddy agent team: 346 models available, context windows up to 2M tokens, connected in minutes with your own key.

Kilo Gateway is one of 178 LLM providers supported by WorkDaddy’s model layer in 2026, in the Aggregators & Gateways group. The catalog currently lists 346 models from Kilo Gateway: 186 with explicit reasoning, 165 with vision input, and 260 with tool calling — the capability that matters most for agent work. The largest context window reaches 2M tokens.

At a glance

Models available 346
Reasoning models 186
Vision models 165
Tool-calling models 260
Largest context window 2M tokens
API endpoint https://api.kilo.ai/api/gateway
API key variable KILO_API_KEY
SDK adapter @ai-sdk/openai-compatible
Provider docs kilo.ai ↗

Why run WorkDaddy agents on Kilo Gateway in 2026

Tool calling, context size, and cost decide how well a provider drives an agent team. Kilo Gateway brings 260 tool-calling models to WorkDaddy — enough to power the full loop of storefront edits, analytics queries, and content production — with 2M tokens of context at the top end for whole-codebase and long-report work. Because WorkDaddy is model-agnostic, you can route heavy reasoning to Kilo Gateway’s strongest model and bulk work to its cheapest, inside one team.

Best Kilo Gateway models for e-commerce agents (2026)

The current flagships from Kilo Gateway in the WorkDaddy catalog, newest first:

  • MiniMax: MiniMax M3 — MiniMax multimodal model for long-context coding, perception, and agent planning (1M context)

  • xAI: Grok Build 0.1 — Grok coding model for agentic engineering, edits, and codebase workflows (256K context)

  • Google: Gemini 3.5 Flash — Fast Gemini model balancing multimodal reasoning, tool use, and cost (1M context)

  • Google: Gemini Flash Latest — Fast Gemini model balancing multimodal reasoning, tool use, and cost (1M context)

  • Perceptron: Perceptron Mk1 — Multimodal reasoning model for visual analysis, planning, and tool use (33K context)

  • Anthropic: Claude Opus 4.7 (Fast) — Flagship Claude model for deep reasoning, coding, and long-horizon agents (1M context)

How to connect Kilo Gateway to WorkDaddy

WorkDaddy talks to Kilo Gateway at api.kilo.ai via the @ai-sdk/openai-compatible adapter. Add your credential (typically KILO_API_KEY) in Settings → Models, pick a default model, and every agent can use it immediately — or add Kilo Gateway as one engine among several and let tasks route to the best fit.

Featured models

Model Context Reasoning Released
MiniMax: MiniMax M3 1M Yes 2026-06-01
xAI: Grok Build 0.1 256K Yes 2026-05-20
Google: Gemini 3.5 Flash 1M Yes 2026-05-19
Google: Gemini Flash Latest 1M Yes 2026-05-19
Perceptron: Perceptron Mk1 33K Yes 2026-05-12
Anthropic: Claude Opus 4.7 (Fast) 1M Yes 2026-05-12

How it works

01

Connect

In WorkDaddy, open Settings → Models, choose Kilo Gateway, and paste your API key (KILO_API_KEY). No key? Start on the managed gateway instead.

02

Put agents to work

Pick MiniMax: MiniMax M3 or any of the 346 available models as your default — per-agent overrides let you match model to task.

03

Review and approve

Agent output stays draft-first regardless of the model: review diffs and approve actions exactly as before.

Frequently asked questions

Does WorkDaddy support Kilo Gateway in 2026?

Yes — Kilo Gateway is a supported LLM provider with 346 models in the WorkDaddy catalog, connected with your own API key via the @ai-sdk/openai-compatible adapter.

How many Kilo Gateway models can I use with WorkDaddy?

346 models are listed for Kilo Gateway, including 186 reasoning models and 165 vision-capable models. The flagship lineup above shows the newest.

What context window do Kilo Gateway models offer?

Up to 2M tokens on the largest model — relevant for whole-repo storefront work and long analytics reports.

Is Kilo Gateway the best LLM provider for e-commerce agents?

It depends on the task mix — Kilo Gateway sits in the Aggregators & Gateways group. WorkDaddy is model-agnostic, so the practical answer in 2026 is to combine providers: route each agent task to whichever model fits best.

Put the team to work on your store

Connect your storefront, analytics, and email stack, set a goal, and let the agents run the work end to end. Start on the free plan with your own model key.