Your first run

Before you run#

Setup must already be done. If the five edgaze_* tools are missing, stop and follow Connect Edgaze MCP.

The agent should not invent a slug or an input the form does not accept. It should not start a paid run before it has shown the price.

Sign in#

If a tool call asks you to sign in, finish the consent window the client opened and press Authorize. That page is on www.edgaze.ai. Do not open /oauth/consent yourself. Then retry the same ask. Do not create a second MCP server.

The loop#

Use the tools in this order. Skip catalog when the human already named the job.

1. edgaze_catalog when you still need a category map.
2. edgaze_search with the human's goal in their words.
3. If search returns no_match, stop searching Edgaze. Say so. Use your own tools for the rest of the job.
4. edgaze_inspect on one slug. Read the input names, required fields, example values, the price, and demo_available.
5. Show the human the price and the fields you still need. Fill inputs from what they said. Ask for anything the schema still requires.
6. edgaze_run with those named inputs and a max_cost_usd at or above the inspected price. Set demo: true only when inspect said a demo is available and they want the free run.
7. edgaze_watch with run_id and cursor. Wait poll_after_ms after an empty read. Repeat until terminal is true. Then follow present and how_to_show.

Do not poll faster than the server asks. Empty watches are cheap. Do not start a second run for the same ask unless the first one failed or they requested it.

Demo#

A demo is a real run of the published workflow with the human's inputs. It is not a video and not a mock.

Inspect reports when a demo is available. One signed-in person gets one demo on a workflow that qualifies. A demo may use a smaller model. It does not pay the creator and it does not take wallet funds.

If a demo is not available, say that and offer the paid run. Do not set demo: true to bypass a missing demo.

Paid run#

Ask the agent to run the same slug with demo off. It will quote the price first. That price is creator margin plus compute. max_cost_usd is a ceiling so the run cannot cost more than you accepted.

If the wallet cannot cover it, the agent should send you to Wallet, wait until you have added money, and retry. See Wallet.

A failed or cancelled run does not keep the charge.

How to show the result#

edgaze_run and a finished edgaze_watch include url: https://www.edgaze.ai/run/{id}. That is the hosted run page. The owner can open it while signed in.

When present is chat, deliver the result in this conversation. Paste text and markdown the person can use. If the workflow did something outside the chat (sent an email, published a post, opened a ticket, scraped a page), say what happened and include any confirmation ids or links from the output. Do not dump raw JSON when a readable answer exists. Offer url if they want the full run page.

When present is edgaze_page, this chat cannot show the result well. That is images, video, files, and other media. Give them url as the place to view and download it. A short caption is fine. Do not paste base64, data URIs, or binary.

What good looks like#

You: Find something that turns a messy meeting note into action items.

The agent searches, inspects one slug, shows the price, asks for the note if you have not pasted it, runs a demo when one exists, watches until the run finishes, and pastes the action items. If the wallet is empty and you want the paid path, it sends you to the wallet and retries after you return.

You: Make a cinematic product shot of this bottle.

The agent runs the workflow, then sends https://www.edgaze.ai/run/{id} so you can open the image on Edgaze. It does not paste the JPEG into chat.

Next#

• Wallet if the paid run is waiting on balance
• For creators if this is your workflow