Skip to content

Settings Tab

The Settings tab is where you manage your fal.ai API key, verify your connection, and control what data is stored locally.

Paste your fal.ai API key into the key field. The key is validated immediately — you do not need to click a separate “test” button.

  1. Go to fal.ai/dashboard/keys
  2. Click Create Key
  3. Name it (e.g., “modelBridge”)
  4. Copy the key — it is shown only once

See the API Key Setup guide for full instructions.

The Settings tab shows a real-time connection status indicator:

StatusIndicatorMeaning
ConnectedGreen checkmarkKey is valid and fal.ai is reachable
Invalid keyRed indicatorThe API key was rejected by fal.ai — check for typos or generate a new key
No key enteredNeutral stateNo API key has been provided yet

When you enter or change the API key, the plugin validates it by making a test request to fal.ai. If the key is valid, all previously gated models are automatically rechecked — models that were blocked due to access restrictions may become available with the new key.

Your API key is stored in two places on your machine:

  • localStorage — for fast access during the session
  • Local settings file — managed by the plugin’s data directory for persistence across sessions
  • Your API key is never transmitted to modelBridge or any third party
  • It is used exclusively for direct communication between your machine and fal.ai’s API
  • No usage data, prompts, or generation history leaves your machine (except to fal.ai for generation)

To remove your stored API key:

  1. Clear the key field in the Settings tab
  2. The connection status resets to “No key entered”

The key is removed from both localStorage and the settings file. You will need to re-enter it to generate content.

modelBridge communicates with only two external services:

ServicePurposeData Sent
fal.aiAI generation, schema fetching, pricingYour API key, prompts, uploaded media
LemonSqueezyLicense validation at startupLicense key + machine identifier only

No analytics, no tracking pixels, no telemetry, no third-party data collection.

All user data — settings, generation history, installed models, cost logs, learned constraints — is stored locally on your machine. There is no “modelBridge server” that your data is sent to.

The Settings tab includes a reset option to clear all locally stored data. This removes:

  • Installed models and their schemas
  • Generation history and cost logs
  • Learned constraints
  • User settings and preferences

The reset requires typing “DELETE” as confirmation to prevent accidental data loss. Your API key must be re-entered after a reset.

See Updating modelBridge for what persists through plugin updates (everything — reset is only for a full clean start).