---
title: Sell to Humans and Agents
description: How one published workflow reaches marketplace buyers, REST API callers, and upcoming MCP agent tools.
source: https://www.edgaze.ai/docs/sell-everywhere
section: resources
---
# Sell to Humans and Agents

> How one published workflow reaches marketplace buyers, REST API callers, and upcoming MCP agent tools.

**Audience: Creators who want one workflow product available across every Edgaze surface.**

**Outcome: Publish once in Workflow Studio and sell the same execution through the marketplace and API without rebuilding the graph.**

## Overview

When you publish a workflow on Edgaze, you are not shipping a one-off chat prompt. You publish a product with a product page, a pinned version, a displayed per-run price, and an execution graph Edgaze runs for every buyer.

That same published product is available through:

- the **marketplace** for human buyers who discover and run it on the product page;
- the **REST API** for applications and backends that create runs programmatically; and
- **MCP** tool calling for AI agents (coming soon - the same workflow product will be invocable as a tool without a separate graph).

You do not maintain separate products per channel. Marketplace, API, and (when available) agent invocations execute the published workflow version under the same pricing and run rules.

## Marketplace

Buyers find your workflow on the [marketplace](/marketplace), open its product page, provide inputs within your published envelope, and run it. Each successful run charges the displayed per-run price and credits your creator share of margin. See [Publish and Price](/docs/billing/publish-and-price) and [Run a Workflow](/docs/billing/run-a-workflow).

Marketplace buyers also see your free demo path when demos are enabled. Demos never bill and never create earnings. See [Free Demos](/docs/free-demos).

## REST API

Developers with an API key can discover runnable workflows and create runs against the same published versions. API runs use the same funding rules (bundle first, then wallet) and the same displayed price for that version. See:

- [API Quickstart](/docs/api/quickstart)
- [Create a run](/docs/api/create-run)
- [API billing](/docs/billing/api-runs)

Your workflow does not need a second “API edition.” Publishing for marketplace access and enabling API access operate on the same product identity.

## MCP (coming soon)

MCP tool calling will let an AI agent invoke your published workflow as a tool. The homepage and developer platform describe this as upcoming. Until MCP ships, do not document agent tool endpoints as live. When it launches, agents will call the same published workflow product - not a fork of your graph.

## What stays the same across channels

- **Version pinning:** Buyers and API callers run a specific published version with its pinned price.
- **Input envelope:** Oversized inputs are rejected before charge.
- **Billing:** Successful runs charge the displayed price; failed or cancelled runs do not charge margin. Demo and builder test runs are never billed.
- **Earnings:** You earn 80% of margin on successful paid runs, regardless of whether the buyer came from the marketplace or the API.

## What you do in Edgaze

1. Build and test in [Workflow Studio](/builder).
2. Publish with margin, envelope, and product page assets.
3. Share the product page or Edgaze code for humans; developers use the API with a key from [Developer](/developer/keys).

## Related docs

- [Workflow Studio](/docs/builder/workflow-studio)
- [Edgaze Code](/docs/edgaze-code)
- [API overview](/docs/api)
- [Creator Earnings Guide](/docs/billing/creator-earnings-guide)
- [Managed Execution](/docs/managed-execution)

## Start building

Open [Workflow Studio](/builder) and publish a workflow you can sell on the marketplace and call from the API.