Loomal Index vs n8n Workflow Marketplace selling the tools vs selling the templates.
n8n's marketplace sells workflow templates — the automation logic. Loomal sells access to the MCP servers and APIs those workflows call underneath, priced per call via x402. One monetizes the recipe, the other monetizes the ingredients.
The n8n Workflow Marketplace and Loomal both monetize the automation stack, but at different layers. n8n's marketplace trades in templates: pre-built workflow definitions — including ones that use MCP nodes — that you import into your n8n instance and run.
Loomal trades in the layer below: the MCP servers and API endpoints those workflows actually call when they execute. A template is bought once; the tools inside it get called on every run. That difference in shape drives everything in this comparison.
What the n8n marketplace does well
n8n's marketplace gives builders a head start: instead of designing an automation from a blank canvas, you import a pre-built template — the node graph, the logic, the wiring — and adapt it. For common patterns, that compresses hours of workflow design into minutes, and it gives template authors a way to package and distribute their automation expertise.
Templates that include MCP nodes also act as a soft on-ramp to the MCP ecosystem for n8n users who haven't touched the protocol directly.
What a template can't carry
A template is a static artifact. It encodes which services a workflow calls, but it can't supply the access: the buyer still needs credentials, accounts, or payment arrangements for every external tool the template references. And the template author monetizes the design once — they capture nothing from the thousands of executions that follow, and neither does the builder of the underlying tool the template depends on.
There's also no usage-based payment primitive in the template model. If a workflow step needs a paid lookup, the marketplace that sold the template has no mechanism for settling that per-run cost.
What Loomal adds
Loomal monetizes execution, not design. An MCP server or API listed on Loomal carries a per-call price (from $0.01), and the x402 flow settles it inline: the calling agent or workflow gets an HTTP 402 with the price, pays in USDC, settlement lands on Base in about two seconds, and the handler runs after payment clears. Ed25519-signed receipts document every call; there are no chargebacks.
That's the recurring-revenue shape the template model lacks — the tool builder earns on every run, not once at import time. Loomal's fee is 5% on settled transactions, currently waived.
The layers compose
These two markets feed each other. A workflow template that calls Loomal-listed endpoints is more useful, not less — the buyer imports the template and the per-call payments handle tool access without provisioning six API accounts first. And every popular template that references your MCP server is distribution for your Loomal listing: more runs, more paid calls.
Template author, tool builder, and workflow runner are three roles, and only the middle one is Loomal's customer. There's no scenario where listing on Loomal and distributing templates on n8n conflict.
When to use which
Sell on the n8n marketplace when your product is automation design — a polished, reusable workflow. List on Loomal when your product is a capability — a server or endpoint that workflows and agents call repeatedly and should pay for per call. If you've built both a useful MCP server and workflows that showcase it, do both: the template drives adoption, the listing converts adoption into per-call revenue.
FAQ
Is Loomal a replacement for the n8n Workflow Marketplace?
No — they monetize different layers. n8n's marketplace sells workflow templates (the automation logic); Loomal sells per-call access to the MCP servers and APIs that workflows call when they run. A tool builder can benefit from both at once.
Does the n8n marketplace support x402 payments?
The n8n marketplace sells templates, not per-call tool access, so x402 isn't part of its transaction model as we understand it in mid-2026. n8n workflows themselves can call x402-priced endpoints if the executing step completes the payment flow — check n8n's docs for current capabilities.
Can an n8n workflow pay for a Loomal-listed tool per run?
Yes, provided the step making the call can handle the x402 exchange: receive the HTTP 402, pay the listed price in USDC from a wallet, and retry. Settlement on Base takes roughly two seconds, which fits comfortably inside workflow execution.
I sell n8n templates that use my own MCP server. What does Loomal add?
Per-execution revenue. The template sale pays you once; a claimed Loomal listing with x402 pricing pays you every time any workflow or agent calls your server — minimum $0.01 per call, at a price you can change in one field.
Earn on every run.
List the server your workflows depend on and get paid per call.