FlowManner
Chat
Sign InGet Started
Flowmanner
Menu
  • Chat
  • Agents
  • Pricing
  • Docs
  • About
Products
  • Workflows
  • Templates
  • Changelog
  • Missions
Resources
  • Blog
  • API Reference
More
  • Careers
  • Contact
  • Security
  • Start
    • Quickstart
    • Your First Mission
    • Your First Eval
  • How-to
    • Connect Your Own Keys (BYOK)
    • Switch Models Per Task
    • Publish a Template
    • Run Evaluations
    • Chat with Artifacts & Previews
    • Automate via the API
    • Webhooks & Triggers
  • Concepts
    • Glossary
    • Execution Model
    • Models & Routing
    • Sandboxes & Previews
    • Memory & Privacy
    • Trust Model
  • Reference
    • Reference · API
      • Authentication
      • Missions & Runs
      • Chat & Sandboxes
      • Blueprints, Graphs & Templates
      • Evaluations & Feedback
      • Marketplace & Community
      • Files & Exports
      • Integrations & Webhooks
      • Agents & Orchestration
      • Auth, Workspaces & Billing
      • Memory & Knowledge
      • Notifications
      • Platform Services
    • Errors
    • Models
    • Limits

Connect Your Own Keys (BYOK)

Add a provider API key, test it, understand what Flowmanner relays — against the real Settings UI.

What you'll accomplish

Your own provider key (DeepSeek, OpenAI, Anthropic, … or any OpenAI-compatible upstream) used for your missions' LLM calls.

Steps

  1. Open Settings → API Keys in the web app. The page shows a key list — not per-provider config files.
  2. Click Add key and pick a provider from the dropdown (12 built-ins, frontend/src/lib/provider-models.ts). For anything else choose OpenAI Compatible (Custom) and enter its base_url.
  3. Paste the key and save. Mark one key as your default if you use several.
  4. Press the key's test button. Testing probes the upstream's GET /models; providers without that endpoint fall back to a universal 1-token completions probe (app/api/v1/api_keys.py, test_key). A green result means Flowmanner reached the provider with this key — it is not a billing check.
  5. Mind the model-id contract: strict upstreams require fully-qualified ids such as deepseek-chat/deepseek-v4-flash; bare names can be rejected with HTTP 400 (see Models).

What Flowmanner sees (privacy truth)

Missions call models through Flowmanner's backend: requests are relayed by our infrastructure. Your keys are stored encrypted at rest, and your prompts are never used for training. If a provider statement claims we "never see your traffic", that would be wrong — relay-honesty is the policy.

Rotate or revoke

Re-add the key entry with the new secret and delete the old one; routes pick up the active key immediately.

Last updated 2026-08-25 (git-derived)

  • What you'll accomplish
  • Steps
  • What Flowmanner sees (privacy truth)
  • Rotate or revoke