Workflow Studio

Workflow Studio is the visual editor for products that buyers can run. A workflow can be one model block or a connected process with inputs, tools, logic, and a final output. This page gets one working end to end; the Block reference is authoritative for individual block settings.

The shortest useful workflow#

Start with three blocks:

1. Input asks the buyer for a topic or source text.
2. LLM Chat turns that input into the requested result.
3. Output publishes the value buyers should receive.

Connect them from left to right. A connection carries the upstream block's output into the downstream block. Keep the first version small enough that every connection has an obvious purpose.

Build it#

Open Workflow Studio, create a workflow, and add the three blocks.

In Input, use a clear buyer-facing name such as topic. Mark it required when the workflow cannot work without it.

In LLM Chat, write instructions that reference the connected input. Choose a model based on quality, latency, and provider setup. The current default comes from the catalog: gpt-5.6-terra. The model picker is the source of truth for currently callable alternatives.

In Output, choose the value from LLM Chat and give it a plain name such as article or summary. Only Output blocks become the buyer's final result.

Use the Studio without losing context#

The left library is for finding blocks and templates. Its category rail uses icons to keep the canvas wide; hover or focus an icon to see its category name. Search filters both blocks and templates.

Select a block to configure it in the Inspector. The Inspector is tied to that exact block, so switching between two blocks of the same type does not carry unfinished field values across. Saving, Saved, and Error show whether the current draft reached storage.

Connections describe data flow, not execution decoration. Start at an output port and finish at a compatible input port. If a connection is rejected, use the message beside the attempted connection to fix the type, occupied input, direction, or cycle.

On a narrow screen, the Inspector becomes a bottom sheet so the graph remains visible. Hidden Studio layers are removed from keyboard and screen-reader navigation while a modal editor is open.

Repeat a transformation without cluttering the main graph#

Use Loop when the buyer supplies a list and each item needs the same work. The Loop card has one array input, one collected-results output, and a real preview of its internal workflow.

Open Edit loop workflow to work with the same library, canvas, connections, and Inspector inside the Loop. Saving returns you to the main graph; internal blocks stay inside the Loop and cannot be dragged out accidentally.

See Loop for result selection, iteration limits, cost, empty arrays, and failure behavior.

Test the buyer path#

Select Test run, enter realistic input, and run the workflow. Check all of these before publishing:

• The form asks only for information the workflow actually uses.
• Every block completes in the expected order.
• The Output block contains the complete buyer result.
• Errors explain what the creator or buyer needs to change.
• No provider key, token, or internal configuration appears in output or logs.

Builder test runs are not billed. Provider-key requirements still need to be valid for the execution mode you select.

For Loop workflows, test with a short list first. Confirm that every item produces one result in the same order, then test an empty list and your promised maximum size.

Choose provider credentials#

Publishing offers three listing-level modes:

• Edgaze hosted: Edgaze supplies provider credentials and applicable hosted compute is included in the displayed run price.
• Creator-connected: the creator's encrypted Vault keys run the listing. The creator needs active Plus and every required provider key. Provider usage bills the creator directly.
• Buyer brings keys: each runner needs active Plus and the required Vault keys. Provider usage bills the buyer directly.

The publish screen derives required providers from the graph. A non-hosted listing never silently falls back to Edgaze credentials. If a required creator key is removed, the listing becomes unavailable until it is repaired.

Read API Vault and BYOK billing before choosing a non-hosted mode.

Price and publish#

Free workflows have no creator margin. For a paid workflow, set a per-run creator margin between $0.05 and $50.00. The buyer sees one displayed price containing the creator margin plus applicable hosted compute. Creators receive 80% of their margin, not 80% of the full displayed price.

Before publishing, confirm:

• The title and description say what the buyer gets.
• Required setup and providers are disclosed.
• The thumbnail and demos represent normal results.
• The input envelope covers the promised use case.
• The failure and cancellation expectations are accurate.

Publishing creates an immutable workflow version. Later edits create a new version when the executable graph or pinned execution contract changes.

Remix rules#

A creator may allow an original workflow to be remixed as one sealed Remixed Workflow block. A valid remix has one sealed parent and a meaningful change around it. A remix cannot itself be remixed, so composition depth is one. The publish screen rejects a remix of a remix before it becomes a listing.

Read Remix and composed workflows and the Remixed Workflow block for exact inputs and failure behavior.

Where to go next#

• Input and form blocks
• LLM Chat
• Output
• HTTP Request
• Condition
• Loop
• Composer
• Templates