Skip to main content
Bringing your own keys is necessary when:
  • you want upstream billing on your provider account
  • you need built-in providers beyond OpenAI and Anthropic
  • you’re running custom providers
Your application authenticates with an access key. Store provider keys in app.ngrok.ai and attach them through an access key configuration.

Built-in providers

OpenAI & AnthropicOther built-in providers
Provider account neededOptionalYes
Default credentialsngrok.ai inference (with credits)Provider key required in configuration
What credits pay forProcessing fee; plus model cost with ngrok.ai inferenceProcessing fee only
For OpenAI and Anthropic, create a configuration routing rule with Bring your own API key instead of ngrok when you want to use your provider account.

Custom providers

Custom providers are endpoints you define, such as Ollama, vLLM, or any OpenAI- or Anthropic-compatible API. See Use a model you run yourself. Custom providers require provider keys in the configuration when the upstream needs authentication. See Custom providers.

Setup flow

  1. Add provider keys.
  2. Create an access key configuration with routing rules and scope.
  3. Assign the configuration to an access key.
  4. Send requests with the access key only.

Migrating from endpoint-based setup

If you previously used Traffic Policy on an ngrok endpoint, see Migrating from endpoints.

Guides

Bring your own provider key

Store upstream credentials

Access Key Configurations

Attach keys and set scope

Use a model you run yourself

Self-hosted and third-party endpoints