Skip to main content

Connect Factory Droid in one click →

The guided connect page mints your key and generates the customModels block for exactly the models you pick.
Everything below is the manual equivalent. Droid reads custom models from ~/.factory/settings.json (Factory’s BYOK reference). Add the gateway as customModels entries with provider: "generic-chat-completion-api" — the gateway’s OpenAI chat-completions surface serves every gateway model, streaming and tool calls included:
Export your key (Droid expands ${VAR} references in apiKey at parse time, so the settings file never holds the secret):
Headless runs work the same way — droid exec -m "custom:gpt-5.4-mini" "..." routes through the gateway with no extra setup.
Claude models can also use Droid’s native Anthropic dialect. Set "provider": "anthropic" with "baseUrl": "https://api.aireserve.com" (host root — no /v1); Droid then calls the gateway’s /v1/messages surface, and prompt caching works as it does first-party. The generic-chat-completion-api entries above work for Claude models too, so this is optional.

​
Enterprise rollout

Factory’s enterprise plans distribute org-managed settings to every Droid seat. Publish the AI Reserve models as org-defined customModels and pin modelPolicy so members cannot add models that bypass the gateway:
allowCustomModels: false disables personal BYOK while org-defined entries keep working (org-level keys are locked — projects and users can add to them but never override them), and allowedBaseUrls limits custom-model traffic to the gateway. Each member exports their own AIRESERVE_API_KEY, so usage is metered per person.