Getting Started

Platform keys vs. bring your own key (BYOK)

Use Runtype platform keys or connect your own provider credentials to run AI models. Platform keys are included with every plan. Bring your own key (BYOK) gives you dedicated provider limits, direct provider billing, and access to additional supported models.

Platform keys

Platform keys are Runtype-managed API credentials that are included with every plan. They are available when you sign up, so you can start building Flows and Agents without creating provider accounts or adding provider configuration.

Platform keys fit these use cases:

  • No provider setup: Create Flows and Agents without setting up provider accounts.
  • Runtype usage tracking: Review platform-key spend in Runtype.
  • Prototyping: Explore the platform and build demos with curated models.
  • Fewer external accounts: Use models through Runtype without creating individual provider accounts.

Platform key details

Use these facts to choose platform keys:

  • Plan access: Every Runtype plan includes platform keys for a curated selection of models from providers such as OpenAI, Anthropic, Google, xAI, Vercel, and Mixlayer. See Available AI models for the supported models.
  • Execution limits: Runtype does not cap Flow executions by plan. A per-second rate limit, spend cap, or exhausted credit can pause executions. The dashboard shows executions run today, but that count is not a daily allowance.
  • Provider-native search: OpenAI Web Search, Anthropic Web Search, and xAI search carry a small per-invocation fee on top of token costs when you use platform keys. Connect your own provider credential to pay the provider directly. See Built-in tools.
  • Response time: Platform keys use shared Runtype capacity, so provider throttling can affect response times during peak usage.

Bring your own key (BYOK)

BYOK lets you connect provider credentials to Runtype. Supported connections include OpenAI, Anthropic, Google, xAI, Mixlayer, Vercel AI Gateway, Tinfoil, Amazon Bedrock, Vertex AI, Vertex AI (Claude), and OpenAI-compatible endpoints. OpenAI-compatible endpoints include Groq, Fireworks, and self-hosted vLLM servers. You can use API keys, service-account credentials, or AWS credentials, depending on the provider. BYOK gives you dedicated provider limits, access to supported provider models, and direct provider billing.

BYOK is available on the Team plan and higher. If the dashboard asks for a payment method, open Settings > Billing and add one before you continue.

Choose BYOK

BYOK fits these use cases:

  • Dedicated provider limits: Use the quota of the provider account associated with the credential.
  • Direct provider billing: Pay the provider directly and review costs in the provider dashboard.
  • Provider model access: Connect a provider credential to use the models that Runtype supports from that provider.
  • Internal requirements: Maintain a direct provider relationship for your organization.

Set up BYOK

To add a provider connection, follow these steps:

  1. On the Settings > Models page, select the Providers tab.
  2. Find your provider and click Configure.
  3. If you need credentials, sign in to the provider dashboard and create them.
  4. Enter the required credentials, name the connection, and save it.

After you save a connection, it appears in the provider settings. Select the connection when you configure a model. Saving or rotating an organization connection does not change runtime custody until an organization admin selects organization authority.

Use organization connections

Organization connections use separate storage and authority steps:

  • Store the connection: In an organization, these providers use shared connections: OpenAI, Anthropic, Google, xAI, Mixlayer, and Vercel AI Gateway. The list also includes Tinfoil, Amazon Bedrock, Vertex AI, Vertex AI (Claude), and OpenAI-compatible endpoints. Organization admins can save, rotate, revoke, and delete them.
  • Select the authority: Select Use for the organization to make the connection the provider-wide authority for every teammate and detached execution.
  • Choose platform custody: OpenAI, Anthropic, Google, xAI, Mixlayer, and Vercel AI Gateway also support Platform Key authority. Tinfoil, Amazon Bedrock, Vertex AI, Vertex AI (Claude), and OpenAI-compatible endpoints are BYOK only.
  • Track ownership: Runtype records the acting member for audit, but the credential belongs to the organization.

Providers that have not moved to organization connections remain scoped to the member who created the credential. The credential remains member-scoped until the dashboard identifies it as an organization connection. Individual Flows and Agents do not need updates after you select organization authority because the selection applies per provider.

You can use platform keys and BYOK at the same time. For example, use your OpenAI credential for production Flows and platform keys for Anthropic models that you are testing.

Compare platform keys and BYOK

Use the following table to compare the two options:

CategoryPlatform keysBYOK
SetupAvailable when you sign upAdd and save a provider credential
Rate limitsShared Runtype capacityDedicated provider limits
Model accessCurated selection of supported modelsSupported models from your provider
BillingRuntype tracks platform-key spendThe provider bills you directly
Best forStarting and prototypingProduction workloads, provider limits, and direct billing
Plan availabilityAll plansTeam plan and higher

Move from platform keys to BYOK

To move an organization provider from platform custody to BYOK, follow these steps:

  1. Add and save a provider credential.
  2. Select Use for the organization when you want every teammate and detached execution to use that connection.
  3. Keep your Flows and Agents unchanged. Authority applies per migrated provider.
  4. To return to Runtype-managed custody, select Platform Key before you revoke or delete the last required BYOK connection. This option applies to OpenAI, Anthropic, Google, xAI, Mixlayer, and Vercel AI Gateway.
  5. For Tinfoil, Amazon Bedrock, Vertex AI, Vertex AI (Claude), or an OpenAI-compatible endpoint, select a replacement organization connection before you remove the selected connection.
  6. Rotate the selected connection to preserve its authority.
  7. Before you revoke or delete the selected connection, select another valid authority. The provider can become unavailable until an organization admin selects one.

When organization BYOK is required, Runtype does not silently substitute a platform credential if the selected connection is unavailable.

Providers that remain member-scoped retain their documented compatibility behavior. See Connecting AI model providers for provider-specific setup instructions.

Next steps

Continue with these guides: