Runtype comes with platform keys, so you can start using popular AI models without adding any provider accounts. If you want dedicated rate limits, direct provider billing, or access to a provider’s full model catalog, you can connect your own keys in Settings.
For a full comparison, see Platform Keys vs. Bring Your Own Key (BYOK).
Every Runtype account includes platform keys for popular models from OpenAI, Anthropic, Google, xAI, and open-source models through Mixlayer. You can start building Flows and Agents right away, with no extra setup.
Adding your own provider keys is optional. It helps when you want dedicated rate limits, direct provider billing, access to the full model catalog, or more headroom for high-volume production workloads.
Runtype supports direct providers such as OpenAI, Anthropic, Google, and xAI; inference providers such as Together.ai, Amazon Bedrock, Vertex AI, and Mixlayer; gateway providers such as Vercel AI Gateway, OpenRouter, Cloudflare Workers AI, and Azure; and any OpenAI-compatible provider via the generic OpenAI-compatible configuration. Models from creators like Mistral, Cohere, AI21, Meta, DeepSeek, and Qwen are accessible through these gateway and inference providers.
You can start either from a model or from a provider.
You can connect multiple providers at once. For example, you might use OpenAI for GPT models and image generation, Anthropic for long-context work, and Google for multimodal use cases, then switch between them across your Flows and Agents.
Each provider has its own setup flow. Use the provider’s dashboard to create the credentials, then add them in Settings → Models under My Providers.
Mixlayer models are already available through platform keys. If you want dedicated access, create a Mixlayer key and add it in Mixlayer → Configure.
Connect any endpoint that speaks the OpenAI API (Groq, Fireworks, Perplexity, Ollama, vLLM, LiteLLM, and more).
/v1/models to list what it serves, then you select the ones to enable./v1/models, enter each model id by hand.OpenAI-compatible endpoints are a BYOK feature, available on the Growth plan and higher. On other plans the OpenAI Compatible provider appears with a lock and an Upgrade to unlock button. See Platform Keys vs. Bring Your Own Key (BYOK).
Keep your API keys private. Do not share them publicly or commit them to version control.
Only enable the models you actively use. This keeps model pickers shorter and easier to scan.
You do not need the dashboard to connect an OpenAI-compatible endpoint. Agents and scripts can do the whole flow — create a key, discover models, and register them — over the API, the MCP server, or the SDK. Every write requires the BYOK entitlement, so on plans without it these calls return 402 with code BYOK_NOT_AVAILABLE. The API key needs the INTEGRATIONS:WRITE scope for provider keys and MODELS:WRITE for model configs.
The flow has three steps: create a generic-openai provider key with the endpoint’s base URL, discover its models (or supply a manual list), then make those models available.
Over MCP, the same flow uses the create_provider_key, discover_provider_models, and sync_provider_models tools. To register a single custom model directly, use create_model_config with provider: "generic-openai" and a base_url.
When you use your own keys, the provider bills you directly. Runtype does not add extra charges on top. Check your provider’s billing dashboard for exact costs.
If a model is available through platform keys, related Flows and Agents can continue using it after you remove your own key. If the model depends only on your key, update the model selection in those Flows or Agents.