RedCrown.aiRedCrown.ai Docs Open the app

Connect providers

Bring your own provider keys so runs use your accounts and rates.

1. Provider API keys

RedCrown stores your keys encrypted at rest and resolves them per run. Keys are scoped to your workspace and never shared across workspaces.

UI

Go to Connect (/connect). Choose a provider from the list, paste your API key, and click Save. The key is stored encrypted and is never shown again after saving.

CLI

Set the provider API key as an environment variable in your shell before running redcrown eval. Keys never leave your machine during a local eval.

export OPENAI_API_KEY=sk-...
redcrown eval task.json

See the CLI reference for the full list of accepted environment variable names per provider.

MCP

Call list_models with no arguments to see which providers are currently connected for your workspace:

{}

The response lists every available model grouped by provider. A provider that appears here has a connected key.

2. AWS Bedrock

Bedrock requires an AWS access key, secret, and region. RedCrown stores the three fields as an encrypted credential blob.

UI

Go to Connect (/connect). Select AWS Bedrock, then enter your Access key ID, Secret access key, and Region (for example, us-east-1). Click Save.

CLI

The standard AWS environment and credential chain applies. Set the environment variables or configure a profile with the AWS CLI before running redcrown eval:

export AWS_ACCESS_KEY_ID=AKIA...
export AWS_SECRET_ACCESS_KEY=...
export AWS_DEFAULT_REGION=us-east-1
redcrown eval task.json
MCP

Not available via MCP. Connect Bedrock in the app.

3. A custom endpoint

A custom HTTP endpoint lets you register any authenticated API that follows an OpenAI-compatible or plain request/response shape as a candidate model.

UI

Go to Connect (/connect). Select Custom endpoint and fill in the Base URL, the Auth header (for example, Authorization: Bearer ...), and the Body style (openai or raw). Click Save.

CLI

Set REDCROWN_CUSTOM_HTTP to a JSON object with the connection details to run a custom_http candidate locally:

export REDCROWN_CUSTOM_HTTP='{"base_url":"https://my-model.example.com","auth_header":"Bearer my-token","body_style":"openai"}'
redcrown eval task.json
MCP

Not available via MCP. Use the UI or the CLI environment variable above.

Last verified .