EdgazeEdgaze Docs
Builder
Home
Overview of all Edgaze documentation.
Builder Overview
A complete beginner-friendly guide to the Edgaze builder system, including Workflow Studio, Prompt Studio, Templates, and API Vault.
Workflow Studio
A complete Workflow Studio guide covering the canvas, builder flow, and every node available in Edgaze.
Prompt Studio
Learn how to create reusable prompt products in Edgaze, from placeholders and testing to publishing and monetization.
Templates
Learn how Edgaze templates work, how guided setup flows create editable workflows, and how to start from outcomes instead of raw nodes.
API Vault
Learn how the Edgaze API Vault stores provider keys, how nodes use vault-backed access, and how to set up reliable provider execution.
Resources
Changelog ✨
Product updates, platform changes, and notable improvements.
Privacy Policy
How Edgaze collects, uses, and handles information.
Terms of Service
The core platform terms that govern access to Edgaze, including product usage, publishing, platform limitations, and legal responsibilities.
Creator Terms
The terms that apply to creators who publish and monetize products on Edgaze, including payouts, responsibilities, and marketplace conduct.
Acceptable Use Policy
Rules governing permitted and prohibited use of the Edgaze platform.
DMCA and Intellectual Property Takedown Policy
Procedure for reporting copyright and intellectual property infringement on Edgaze.
Community Guidelines
Legally framed standards governing conduct, content, comments, and participation on the Edgaze platform.
Payments Overview
A beginner-friendly guide to how customers pay, how creators earn, and how money moves through Edgaze.
Payout System
Learn how the Edgaze payout system works, including sell now onboard later, creator eligibility, and the role Stripe plays in payout release.
Marketplace Fees
How Edgaze marketplace fees are calculated and applied
Creator Earnings
Learn how creator earnings are attributed, what 80/20 means in practice, and how to think about sales, balances, refunds, and payout readiness.
Workflow Run Policy
Hosted runs, consumption rules, and options after runs are used
Infrastructure Cost Estimation
Learn how infrastructure cost guidance works in Edgaze publishing and why it is there to help creators price responsibly.
Refund Policy
Our refund policy for workflow and prompt purchases
Chargeback Policy
How Edgaze and creators handle payment disputes and chargebacks
Creator Subscription Policy
Edgaze Plus subscription benefits and terms for creators
Pricing Limits
Minimum and maximum price rules for prompts and workflows
Fraud and Abuse Policy
How Edgaze prevents and responds to fraud and abuse
Content Disclaimer
Important disclosures regarding content available on the Edgaze platform.
Platform Status and Beta Disclaimer
Important disclosures regarding the beta status of the Edgaze platform.
Security and Responsible Disclosure
Guidelines for reporting security vulnerabilities and bugs affecting the Edgaze platform.
Creator Guidelines
Standards and rules for creators publishing content on the Edgaze platform.

API Vault

Learn how the Edgaze API Vault stores provider keys, how nodes use vault-backed access, and how to set up reliable provider execution.

API Vault

API Vault is the secure key management layer for Edgaze.

It lets you connect provider accounts such as OpenAI, Anthropic, and Google so your workflows and prompts can run using vault-backed credentials instead of pasted secrets spread across your products.

On This Page

  • What API Vault is
  • Why it exists
  • Where it appears in the product
  • How vault-backed runs work
  • What creators should expect
  • Best practices

What API Vault Is

Security Layer

API Vault keeps provider credentials centralised instead of scattered across products.

Execution Layer

API Vault also helps the runtime know which provider path should be used for a given node.

API Vault is the place where Edgaze stores your provider API keys securely and makes them available to the nodes that need them during execution.

This system exists for two reasons:

  • security
  • reliability

It is better than asking creators to paste secrets repeatedly into product configuration.

Why API Vault Matters

Reliability

Provider-backed execution is much easier to reason about when the key source is predictable.

Maintainability

Key rotation and troubleshooting become simpler when secrets live in one controlled place.

Without a vault system, creators run into the same problems again and again:

  • secrets copied into too many places
  • confusion about which provider a node needs
  • workflows that fail because the right key is missing
  • painful maintenance when keys rotate

API Vault fixes that by centralising the provider connection point.

Where API Vault Appears

You will see API Vault in places such as:

  • the Inspector when a selected node needs a provider key
  • runtime surfaces when a run depends on user-provided provider access
  • account or settings surfaces where keys are managed directly

Inside Workflow Studio, the vault section should appear alongside the node configuration flow, not detached from it.

Inspector Context

In the builder, vault controls should feel like part of the node setup flow rather than a separate unrelated system.

How Vault-Backed Execution Works

The logic is simple:

  1. A node declares which provider it needs.
  2. Edgaze checks whether the required vault key is available.
  3. If the key exists, the run can proceed using that provider-backed access.
  4. If the key is missing, Edgaze prompts for the missing connection path instead of silently failing.

This makes provider requirements easier to understand at both build time and run time.

Missing Key Behavior

If a required key is not available, the user should get a clear path to fixing the provider connection instead of a vague failure.

Which Providers Matter Most

The main vault-backed providers are typically:

  • OpenAI
  • Anthropic
  • Google

The exact provider required depends on the model family selected in the node configuration.

Provider Matching

The selected model should always be aligned with the connected provider path.

What A Creator Should Know

When you configure a model-driven node:

  • pick the right model for the job
  • confirm the matching provider is connected in API Vault
  • test the workflow using the same provider path you expect customers or your own account to use

Do not wait until publish time to learn that the wrong provider is connected.

Test Early

It is better to validate provider access during build and test than after listing a product.

Example

If a workflow uses an Anthropic model in an LLM block, the node should resolve against an Anthropic vault key.

If a workflow uses a Google model for image or text generation, it should resolve against the matching Google vault key.

The vault is there to keep that mapping predictable.

Anthropic Example

An Anthropic model should resolve through an Anthropic vault key.

Google Example

A Google model should resolve through the matching Google vault key.

Best Practices

  • Keep vault keys centralised.
  • Do not paste secrets into loose notes or unrelated node fields.
  • Match the provider to the actual selected model.
  • Re-test after changing provider configuration.
  • Document provider expectations in published products when relevant.

Operational Habit

Treat vault setup as part of product quality, not as an afterthought.

Common Misunderstanding

API Vault does not change what your workflow does. It changes how the workflow gets authorised to run.

That means it is infrastructure for execution, not product logic.

What To Read Next

  • Workflow Studio
  • Templates
  • Payments Overview
On this page
On This PageWhat API Vault IsSecurity LayerExecution LayerWhy API Vault MattersReliabilityMaintainabilityWhere API Vault AppearsInspector ContextHow Vault-Backed Execution WorksMissing Key BehaviorWhich Providers Matter MostProvider MatchingWhat A Creator Should KnowTest EarlyExampleAnthropic ExampleGoogle ExampleBest PracticesOperational HabitCommon MisunderstandingWhat To Read Next
© 2026 Edge Platforms, Inc. All rights reserved.