Sell runs of your open-source tool

How it works

Apply as a seller: send your photo ID and phone number for review.

Set up payouts on the Payouts page: a listing can't go to review until they are set up.

Connect your tool: a webhook your tool answers (your own API, or a workflow you run in n8n, Make or Zapier), or an MCP server.

Create a listing: the inputs a buyer fills in, what a run returns, and your price.

Each paid run: MeshGigs sends your webhook a signed request with the buyer's inputs (an MCP server gets one tool call). Your tool sends the result back, and the buyer sees it on MeshGigs.

Choose how buyers pay

Choose how buyers pay for your tool: On demand (per run), a subscription, or Buy agents (a one-time license and the files you choose to deliver). Sellers outside Australia can sell on-demand listings only.

What stays yours

You keep ownership of your tool: its source code, model weights, prompt templates and training data (Provider Agreement §8.1). MeshGigs gets a license to list your tool and route runs to it and, beyond storing and delivering the files you upload for a Buy agents listing, no rights to your source code or model weights (§8.2). Unless your listing says otherwise, the buyer owns what a run produces for them (§8.3). You set your own price.

Fees

MeshGigs takes a commission from each payment. On an on-demand run and on the first payment of a subscription, the commission is 15% of the payment after an allowance for card processing (1.7% of the payment plus 0.30), with a minimum of 0.50. On a payment of 25.00 the commission is 3.64. On later subscription payments and on Buy agents purchases it is 15% of the payment. The Provider Agreement §5 has the full rule.

How you're paid

Sellers in Australia are paid through Stripe Connect. Sellers in other countries are paid to a bank account in their own name through Airwallex, after a clearing period; the countries open are shown when you set up payouts. The Provider Agreement §3 and §6 have the details.

What your tool has to do

Answer each request within your listing's time limit. A webhook checks each request's signature and refuses any request that fails the check (Provider Agreement §11). Send the result back as JSON of up to 1 MB. Files go back as https links you host. Keep a buyer's inputs only as long as the run and a reasonable support window after it need them (§11). An MCP server gets one tool call per run and must answer within 40 seconds.

Start from a ready n8n workflow

If you run n8n on your own server, import our starter workflow. It answers MeshGigs at once, checks each request's signature and sends the result back; you put your own steps in the middle.

Licenses

List only what you have the right to sell runs of (Provider Agreement §2). If your tool uses a model, dataset or library whose license doesn't allow commercial use, it can't be sold here.

Questions sellers ask

Do I have to host my tool?

Yes. MeshGigs doesn't run sellers' code today: your tool runs on your own server, or on a cloud you choose, and MeshGigs sends it each run.

Do buyers get my code?

Not on On demand or subscription listings: buyers get each run's result. A Buy agents listing delivers the files you choose, under the license type you pick.

Can a run use the buyer's own accounts?

No. A run works only from what the buyer types or uploads.

Can I sell someone else's open-source project?

Only if you have the rights to (Provider Agreement §2), and only on a listing that says honestly what it is.

What can't be sold?

Anything the Terms of Service don't allow (§14), and regulated advice you aren't licensed to give (Provider Agreement §10).

Is each listing reviewed?

Yes, before it goes live.

Is there a fee to list?

No. MeshGigs takes only the commission on payments.

Which countries can sell?

Sellers in any country MeshGigs pays out to. Outside Australia, on-demand listings only.