Loomal

Monetize any MCP server in 5 minutes with no % skim.

Payments

Developer Tools

Artificial Intelligence

Visit WebsiteSee on Product Hunt

Building an agent-to-agent transactional layer that skips the traditional, high-friction credit card rail is massive for the evolving AI ecosystem. Integrating this directly into the Model Context Protocol (MCP) server framework makes a ton of sense if we want autonomous systems to seamlessly trade resources.

Handling deterministic paywalls for non-deterministic AI queries while keeping latency low is a tough infrastructure challenge. Settling microtransactions in seconds via USDC without percentage cuts changes the economics completely. Congrats on the launch!

The “no % skim” angle is nice, but the trust bit seems harder than billing. If I’m exposing an MCP server to paying users, I’d want clear rate limits/logs before pricing. Do you support usage caps per buyer yet?

@dannyheng I like where this is going but I'm not convinced the market exists yet. x402 volume is still tiny, most agents are still in beta, and asking developers to believe agents will pay for their tools feels early. That said, if it does happen, the team that owns the discovery layer when it does is going to own the whole thing. So the real question isn't "will agents pay now?" it's "will Loomal be THE place agents look when they do start paying?" How are you planning to own that position before the giants move in?

Trying to build an AI agent platform for enterprise procurement and this solves exactly one problem that's been driving me nuts: how do you let agents call third-party APIs without embedding credentials everywhere? If an agent can just... pay for a data enrichment service and the transaction is logged and signed, that's a completely different security model than what we're doing now (which is basically controlled chaos). Curious if anyone else building agent platforms sees this the same way — is credential management the thing you're actually worried about, or is it something else?

The no-percentage-skim line is the interesting one to me, because take rate is the thing that quietly decides whether a marketplace is worth building on. If Loomal isn't skimming a percentage, what's the actual model, flat fee per server or per call, or a subscription on the seller side? I ask because "no skim" usually means the cost moved somewhere else, and where it lands changes who can afford to sell. Rooting for less-extractive rails here.

I shipped a Paddle integration last week, so the "zero revenue share" pitch lands — but let me push on the part MoRs actually earn their cut for.

I didn't pay a merchant-of-record for card processing; I paid them to take on global tax (VAT/GST by jurisdiction) and chargeback liability. If an agent in Germany pays me USDC for an API call, the VAT obligation doesn't vanish just because there's no card — it just becomes mine. So how do you think about tax/compliance for sellers? Is it "you're on your own, that's the price of 0%", or is something planned? Genuinely the first thing I'd have to answer before switching — not a gotcha. (And to be fair: no chargebacks is a real win, and ~2s settlement is a bigger one than people realize if you've ever waited on a payout.)

The discovery angle is what actually stuck with me, though. I run a JVM thread-dump analyzer with a REST API, and "an agent debugging a prod incident buys one analysis" is a use case I hadn't considered until reading this. How does the Index work — does the agent read a schema/description, or is it more structured than that?

The 100%-revenue, no-percentage-cut model is a bold stance in a space where everyone takes a slice. Agent-to-agent payments settling in ~2 seconds via USDC is genuinely the kind of infrastructure the agent economy needs before it can scale. The Loomal Index is a smart addition too — a discovery layer means sellers aren't just adding a paywall, they're getting distribution. Quick question: how do you handle disputes or refunds when the buyer is an autonomous agent? Congrats on shipping!

Congrats on the launch! The no-skim pricing is a bold wedge — flat plans instead of a % cut flips the usual marketplace model. Question: how does discovery work on the Loomal Index? Is there any ranking/curation, or is it first-come?

Congrats on the launch! If one agent gets compromised, can you shut down just its identity, or does it affect the whole account?

Congrats Danny and team! As someone who builds internal skills and MCP servers, “one line of code and keep 100%” is the first monetization pitch in this space that doesn’t feel like a tax. One thing I haven’t seen asked: what happens when the paid call delivers garbage? No chargebacks in USDC, so if my agent pays a listed API and gets back an empty or wrong result, is there any refund or dispute path, or is the on-chain review history the only protection? That answer decides whether I’d let my agents spend real money on the Index.

curious how versioning works on the seller side. if I list a paid MCP tool and later change its input/output schema, do agents that already paid for the old contract get a grace period, or is there just one live version and everyone gets the new behavior immediately whether their integration expects it or not

@dannyheng Everyone's asking about payments, but the part I don't get is discovery. Say I list my API on the Index today — how does an agent actually find it? Is there something agents query programmatically, or are we still waiting for a human to paste a URL into a prompt?

I am fairly new to this concept. I own www.CasterHQ.com and am wondering if AI Agents only shop for digital products or if companies are using or training their "purchasing" to shop for phsyical goods as well like for what I sell? Would this be a beneficial service for my website as well? The description on the service is slightly confusing for me, is there a more simplified explanation on if this is beneficial to ever e-commerce store or only specific types. Thank you so much.

Congrats on the launch! This is incredibly cool. I'm building my own personal agents as a hobby (openclaw calendar trackers, productivity managers etc.) and always thought the next step is agents having their own wallet and being able to transact with each other.

One particular hobby project I'm working on now is an android headunit agent that reads your car OBD data and keeps logs and alerts you when critical codes appear. It'd be so cool if the agent could schedule mechanic appointments and even pre pay for them according to the specific fault code that appears. Definitely will experiment with the SDK

Congrats on the launch! This is incredibly cool. I'm building my own personal agents as a hobby (openclaw calendar trackers, productivity managers etc.) and always thought the next step is agents having their own wallet and being able to transact with each other.

One particular hobby project I'm working on now is an android headunit agent that reads your car OBD data and keeps logs and alerts you when critical codes appear. It'd be so cool if the agent could schedule mechanic appointments and even pre pay for them according to the specific fault code that appears. Definitely will experiment with the SDK!

for sellers who aren't crypto native, is the wallet setup actually 5 minute thing too, or is that the part that quietly takes longer than the sdk integration itself.