API Vault#

API Vault keeps your model provider keys in one secure place. Workflows and prompts use those keys at run time instead of pasting secrets into individual blocks.

Why it matters#

Without a central vault, keys end up copied everywhere, nodes fail for the wrong reason, and rotation becomes painful. Vault gives you one connection point per provider and makes requirements visible while you build and while customers run.

Where you see it#

Vault appears when a block needs a provider key: in the inspector during build, in settings where keys are managed, and at run time when a missing key blocks execution.

In Workflow Studio, treat vault setup as part of configuring the block, not a separate chore.

How runs use vault keys#

Each model block expects a matching provider. Edgaze checks whether that key exists before the run proceeds. If it is missing, you get a clear path to connect the provider instead of a vague failure.

The main providers today are OpenAI, Anthropic, and Google. The model you pick in the inspector should match the key you connect in vault.

What creators should do#

Pick the model for the job, connect the matching provider in vault, and test using the same path you expect at publish time.

Do not discover a missing key on launch day.

BYOK and billing#

When you bring your own key on eligible plans, provider token cost bills to your account. Edgaze charges a small orchestration fee on the run instead of full hosted compute in the displayed price. See BYOK.

Good habits#

• Keep keys only in vault.
• Match provider to model.
• Re-test after you rotate a key.
• Say in your listing when buyers need their own provider access.

What to read next#

• Workflow Studio
• Templates
• BYOK