Loomal Index vs Make.com the marketplace vs the workflow canvas.
Make.com is a visual platform where humans design automations by wiring apps together. Loomal Index is a marketplace where the MCP servers and APIs those automations call can be discovered — and paid for per call by the agents executing them. Different layers of the same stack.
Make.com (formerly Integromat) and Loomal aren't fighting over the same job, even though both live in the automation conversation. Make is where a person designs the logic — a node-based canvas connecting apps, APIs, and conditions into a scenario.
Loomal is where the capabilities those scenarios depend on get listed, discovered, and priced. As workflows shift from human-designed scenarios toward agent-executed tasks, the question of how the executing agent finds and pays for a tool mid-run is exactly the gap Loomal fills.
What Make.com does well
Make.com gives non-developers and developers alike a visual way to build real automation: drag nodes onto a canvas, connect apps and APIs, add conditional logic, and run scenarios on schedules or triggers. Its strength is making integration work legible — you can see the data flow, debug a step visually, and ship automation without writing a service.
For human-designed, human-maintained workflows across SaaS tools, that model is mature and proven.
What a workflow platform doesn't solve
A canvas assumes the builder already knows which services to wire in and has accounts or API keys for each. It's not a discovery surface for the broader MCP ecosystem, and it has no answer for usage-based payment between the workflow and a third-party tool — every connection rides on credentials and billing relationships the human set up beforehand.
That assumption gets strained when the 'builder' is an AI agent. An agent composing its own task plan can't sign up for six SaaS accounts first; it needs tools it can find programmatically and pay for at call time.
What Loomal adds
Loomal Index is the supply side: a marketplace of MCP servers and API endpoints with machine-readable listings and, on claimed listings, x402 pricing. An agent — or an automation step — that calls a Loomal-listed endpoint gets an HTTP 402 with the price, pays in USDC on Base with roughly two-second settlement, and the call executes once payment clears. No account creation, no API key provisioning, no chargebacks; each payment carries an Ed25519-signed receipt.
For tool builders, this is the channel Make doesn't offer: list once, set a per-call price from $0.01, and any agent or workflow runtime that speaks x402 becomes a paying caller.
Where they meet
The interesting overlap is a workflow that consumes paid tools. An automation needing, say, a specialized data lookup can call a Loomal-listed endpoint and settle the cost per execution rather than maintaining yet another subscription for a service used twelve times a month. Pay-per-use pricing matches the bursty, per-run shape of automation traffic better than seat-based plans do.
So the relationship is supply and demand: Make-style platforms orchestrate; Loomal lists and prices what gets orchestrated.
When to use which
Use Make.com when a human is designing and maintaining the automation and the integrations are mainstream SaaS apps. Use Loomal when you need to discover MCP servers and APIs across the ecosystem, when your automation should pay per call instead of holding subscriptions, or when you've built a tool and want workflows and agents to pay you for using it. One is the canvas, the other is the catalog — there's nothing to choose between.
FAQ
Is Loomal a replacement for Make.com?
No. Make.com is a visual platform where humans build automation scenarios; Loomal is a marketplace for the MCP servers and APIs that automations and agents call, with x402 pay-per-call payments. They sit at different layers — orchestration versus tool supply.
Does Make.com support x402 payments?
Make.com's model is built on pre-configured app connections with credentials and accounts the user sets up. As of mid-2026 we're not aware of native x402 support — check Make.com's own documentation for the latest, since automation platforms add integrations frequently.
Can an automation pay for a Loomal-listed API per call?
Yes, if the step making the request can complete the x402 flow — respond to the HTTP 402, pay in USDC from an agent wallet, then retry. Settlement on Base takes about two seconds, so per-run payment fits inside normal workflow execution time.
I built an MCP server — should I list it on Loomal if my users use Make?
Yes. Listing on Loomal doesn't require exclusivity and adds a revenue channel Make doesn't provide: agents and workflows discover your server and pay per call at a price you set, minimum $0.01. Loomal's fee is 5% on settled transactions, currently waived.
List what workflows call.
Put your MCP server or API where agents find it and pay per call.