Context Layer

Bring Your Own Key (BYOK)

10-Second Overview

Bring Your Own Key (BYOK) means developers configure provider credentials in the Context Layer console. Context Layer stores provider credentials securely. Developers never send provider API keys during runtime calls. Provider credentials are never sent by developers during runtime calls.

Why BYOK Exists

Context Layer does not require developers to pass provider API keys with execution requests. Provider credentials are configured at the project level in the Context Layer console.

Supported Providers

  • OpenAI-compatible APIs (OpenAI, Grok)
  • Anthropic

Provider Configuration Freeze

Provider configuration is bound at API key generation. Changing provider selection requires generating a new API key.

Operational Guarantees

Provider invocation occurs within the Context Layer runtime boundary. See Execution Authority for enforcement guarantees.

Related Runtime Documentation

Runtime Contract

Documents the Authority Contract and the behavioral guarantees enforced during execution.

Architecture

Defines system-level component boundaries and the Context Layer runtime structure.

System Boundary

Explains the separation of responsibilities between applications, Context Layer, and LLM providers. Describes what Context Layer controls and what lies outside its authority.