Loomal
Loomal is a payments layer for agentic commerce — paywall an API or MCP tool and get paid per call in USDC on Base.
If agents already call your API or MCP tool, Loomal is the shortest path to charging them I've seen: five lines of requirePayment, no API keys to issue, no percentage of your revenue, and USDC landing in a wallet you control. The flat $49/mo Builder (15,000 calls) and $199/mo Business (75,000 calls) tiers mean you buy capacity, not a slice of each sale — unlike Stripe-style gateways built around per-transaction card fees. Go in clear-eyed on two things: Shopify and WooCommerce agentic checkout are still marked coming soon, so store-side selling isn't available today, and your revenue depends on agents actually carrying wallets and speaking x402.
Verified 4d ago · liveness 73/100 · cite: rightaichoice.com/tools/loomal
- Developers with an existing API or MCP tool who want to charge agents per call
- Solo builders testing whether agent traffic converts on the 50-call free tier
- Data and tool providers with sub-cent per-response economics
- Platforms assembling agent marketplaces that need a machine-to-machine rail
- Anyone who needs fiat or credit-card payments from human customers — settlement is USDC on Base only
- Non-developers wanting plug-and-play checkout; integration is code, not a dashboard
- Teams that require self-hosted or on-premise deployment
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Loomal if you need to take card payments from human customers, need chargeback or dispute handling, or need a no-code checkout — its settlements are final USDC on Base and integration is a five-line SDK wrapper, not a dashboard.
Exceeding your included calls isn't free: Builder charges $0.003 per extra call and Business $0.0025, so a traffic spike past 15,000 or 75,000 calls lands on your next invoice.
The published tiers fit small, technical teams: Free at $0 for 50 calls/month, Builder at $49/mo for 15,000 calls, Business at $199/mo for 75,000 calls, then Enterprise at committed volume. That undercuts percentage-of-transaction gateways like Stripe for sub-cent per-call economics, where a card fee would swallow the sale. It's more expensive than rolling your own metering — but you'd still have to build key issuance and a payment rail.
In short
Loomal — Loomal is a payments layer for agentic commerce — paywall an API or MCP tool and get paid per call in USDC on Base. Best for Developers with an existing API or MCP tool who want to charge agents per call, Solo builders testing whether agent traffic converts on the 50-call free tier, Data and tool providers with sub-cent per-response economics. Free to start; paid plans from $49/mo.
What's new in Loomal
Checked 4 days agoAcross the latest 1 update: 1 launch.
What people actually say about Loomal — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
8 mentions across 2 sources (Hacker News, Product Hunt) · researched Jul 3, 2026.
Average across the 2 sources that answered — each source counts once, not each post.
- +Gives AI agents their own crypto-verifiable identity and wallet.
- +Paywalling any HTTP endpoint or MCP tool takes only five lines.
- +Cash settles instantly on Base with signed Ed25519 receipts.
- +Per-call pricing with free tier reduces upfront commitment for experiments.
- +MCP-native so it works with Claude, Cursor, ChatGPT, and LangChain.
- −Email reputation management per agent is not yet isolated.
- −2FA bypass could break TOS of many third-party services.
- −No real-world reliability or uptime data post-launch.
- −Support responsiveness is completely unproven due to lack of feedback.
- −Shopify/WooCommerce integrations are still in development.
- • 25% fee on free tier is high for production testing beyond 50 calls
Viability Score
How well maintained and how widely used is Loomal? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →Key Features
- requirePayment wrapper paywalls any HTTP endpoint in about five lines via @loomal/sdk
- Paywall any MCP tool and charge agents per call
- x402 payment handshake turns HTTP 402 into a real payment rail
- Agents pay per call in USDC, settled on Base in seconds
- Ed25519 signed receipts verifiable offline for provable, auditable revenue
- Per-request pricing from a tenth of a cent up to $1
- No API keys — x402 does auth and payment in one round trip
- Non-custodial project wallet; cash out to any address you control
- HMAC-signed webhooks for payment notifications
- Hosted endpoints — paste JSON or upload a file and Loomal paywalls it at a payable URL
- Hosted MCP server plus CLI for shell and agent workflows
- Activity and audit timeline on paid plans
- Framework support for Express, Hono, Next.js and FastAPI
- Works with any agent that speaks x402 — Claude, GPT, Gemini, LangChain, CrewAI, MCP clients
- Flat monthly plans with no percentage cut of your settlements
About Loomal
Loomal is payments infrastructure for a machine buyer: it lets AI agents pay your API, MCP tool, or hosted file per request instead of you invoicing a human. You wrap an existing HTTP handler with requirePayment from @loomal/sdk — about five lines — set a price per call, and Loomal runs the x402 payment handshake: it returns the 402 challenge, verifies the agent's signed authorization, settles USDC on Base in seconds, and returns an Ed25519 receipt you can verify offline. There are no API keys to issue or rotate, because the protocol does auth and payment in one round trip. Funds land in a non-custodial wallet provisioned for your project, and you cash out to any address you control — Loomal never custodies the money and takes no percentage of settlements. Three ways to sell today: paywall an endpoint or MCP tool you already run (Express, Hono, Next.js, FastAPI are documented), or paste JSON / upload a file and let Loomal host and paywall it at a payable URL. Shopify and WooCommerce agentic checkout are both still marked coming soon. Per-call prices run from a tenth of a cent to a dollar — sub-cent request economics that card networks can't make profitable. Pricing is flat and published: Free at 50 calls/month with no card, Builder at $49/mo for 15,000 calls, Business at $199/mo for 75,000 calls, and Enterprise at custom volume with a floor of $0.0025 per overage call. Overages are $0.003/call on Builder and $0.0025/call on Business, and your service stays live past the cap rather than throttling. It fits developers and data providers who want to charge agent traffic without building billing themselves; it does not fit anyone who needs fiat card payments from human customers, chargeback protection, self-hosted deployment, or a no-code checkout today.
Behind the Verdict
Loomal is betting that the buyer of the next few years is not a human with a card but an agent with a wallet, and it has built the plumbing for exactly that case rather than retrofitting card rails. The strongest part is the mechanics. Wrapping a handler with requirePayment means Loomal runs the whole sequence — 402 challenge, verification of the agent's signed authorization, settlement on Base, receipt — so you don't build a metering service, a key-issuance system, or a reconciliation pipeline. Ed25519 receipts verifiable offline matter more than they sound: they let you prove revenue to an auditor, a marketplace, or a partner without trusting Loomal's dashboard. Non-custody is the other structural strength — payments land in a wallet provisioned for your project, you cash out to any address, and Loomal takes no percentage, which removes the usual platform risk of your processor becoming your landlord. The pricing model is unusually clean for infrastructure. Free at 50 calls/month with no card lets you test whether agent traffic exists at all before paying anything. Builder at $49/mo covers 15,000 calls, Business at $199/mo covers 75,000, and past that you pay $0.003 or $0.0025 per call with no revenue share and no throttling — the docs are explicit that your service stays live past the cap. That is a very different shape from a percentage-of-GMV gateway, and it's the right shape when a single successful API call might earn half a cent. Where it is honestly thin: distribution. Loomal gives you a paywall, not demand — if no agents are hitting your endpoint, a paywall changes nothing except adding a 402 to your responses. Shopify and WooCommerce integrations are labeled coming soon on both the homepage and the ways-to-sell section, so if your monetization lives in a storefront you're waiting. Settlement is USDC on Base only, which is final and therefore has no chargebacks and no dispute process. And "five lines" is true for wrapping a handler but not the same as a no-code product: this is an SDK and a CLI, aimed at someone who reads a route handler comfortably. Compare against the obvious alternatives and the niche becomes clear. Stripe bills humans with cards and takes a per-transaction cut; it was never designed to charge $0.001 to a software process. Standing up your own metering plus Stripe usage billing works, but you still need key issuance and you still can't take a micropayment economically. Loomal's real differentiator is x402 + USDC: anything that speaks the protocol — Claude, GPT, Gemini, LangChain, CrewAI, a plain MCP client — can pay you without you integrating each one, which is the only way per-call agent billing stays manageable as the buyer side fragments. The realistic buyer is a developer or small data/tool provider with existing API or MCP traffic and sub-cent unit economics, or a platform assembling an agent marketplace that needs a machine-to-machine rail. The realistic non-buyer is a merchant who needs human checkout,
Researching Loomal? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Loomal actually fits — and what changes day-one when you adopt it.
You already serve a premium data endpoint on Next.js. You wrap the handler with requirePayment at $0.05 per call using the @loomal/sdk, deploy, and let agents hit it. Payments settle in USDC to the non-custodial wallet Loomal provisions for the project.
Outcome: You start collecting per-call revenue from agent traffic without issuing a single API key or writing a billing service, and you can verify each sale with an offline Ed25519 receipt.
Your per-response price is a fraction of a cent — too small for card processing. You put the endpoint behind Loomal at a tenth of a cent per call and move onto the $49/mo Builder plan once free-tier calls run out.
Outcome: Requests that a card gateway would have lost money on now settle on Base in seconds, and you keep 100% of what agents pay because Loomal takes no percentage of settlements.
You need third-party MCP tools to be payable inside your marketplace. You list tools behind Loomal paywalls so any client that speaks x402 — LangChain, CrewAI, Claude, a plain MCP client — can pay per call.
Outcome: You get a machine-to-machine payment rail without negotiating a separate billing integration per tool, and each sale is auditable through signed receipts.
Use Cases
- Paywall a premium data API so agents pay $0.05 per call in USDC, with no keys to issue.
- Charge agents per call for an MCP tool you already run, keeping 100% of settlements.
- Paste JSON or upload a file and let Loomal host and paywall it at a URL agents can pay.
- Give a LangChain or CrewAI agent a payable endpoint it can hit autonomously without human approval.
- Prove per-call revenue to a partner or auditor using offline-verifiable Ed25519 receipts.
- Sell sub-cent per-response data that card transaction fees would erase.
- Wire HMAC-signed webhooks into your internal systems for payment notifications.
- Add a metered paywall to a FastAPI or Next.js handler without building a billing service.
Models Under the Hood
as of 2026-09-24
Limitations
- Loomal is a payments layer for agentic commerce, not an AI model.
- Integration is code: you wrap a handler with requirePayment via @loomal/sdk, so a non-developer can't set this up from a dashboard.
- Settlement is USDC on Base only, and on-chain settlements are final — there is no chargeback or dispute path.
- The homepage and the ways-to-sell section both label Shopify and WooCommerce agentic checkout as coming soon, so store-side selling isn't available today.
- Your free tier resets monthly at 50 calls, and Builder and Business allowances refresh each billing period with unused calls that do not carry over.
- Revenue depends on agents actually speaking x402 and carrying wallets — Loomal provides the paywall, not the demand.
as of 2026-10-04
Verification history
We have re-verified Loomal 9 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
Showing the 6 most recent of 9 verification passes.
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published Loomal tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Free
$0/mo
Ideal for
Solo builders who want to test whether agent traffic hits their endpoint before paying anything — 50 calls/month, no card required.
What this tier adds
Starting tier: $0 with 50 calls/month, USDC settlement on Base, HMAC webhooks, Ed25519 receipts and cash-out to any wallet.
Builder
$49/mo
Ideal for
An individual developer or small data API with steady but modest agent traffic who needs an audit trail and email support.
What this tier adds
Adds 15,000 calls/month over Free, an activity/audit timeline and email support, with $0.003 per call past the allowance.
Business
$199/mo
Ideal for
A growing API or tool provider pushing enough agent volume that 15,000 calls/month no longer covers it.
What this tier adds
Quintuples the allowance to 75,000 calls/month and drops the overage to $0.0025 per call versus Builder's $0.003.
Enterprise
Custom
Ideal for
Platforms and larger providers with committed call volume that need an SLA, invoice billing and custom integrations.
What this tier adds
Adds committed volume at a negotiated overage (floor $0.0025/call), a 99.9% uptime SLA, invoice billing and dedicated support.
Where the pricing makes sense
The company stage and team size where Loomal's pricing actually pencils out — and where peers do it cheaper.
The published tiers fit small, technical teams: Free at $0 for 50 calls/month, Builder at $49/mo for 15,000 calls, Business at $199/mo for 75,000 calls, then Enterprise at committed volume. That undercuts percentage-of-transaction gateways like Stripe for sub-cent per-call economics, where a card fee would swallow the sale. It's more expensive than rolling your own metering — but you'd still have to build key issuance and a payment rail.
Setup time & first value
How long it actually takes to get something useful out of Loomal — broken out by persona, not the marketing-page minute.
Wrapping an existing Express, Hono, Next.js or FastAPI handler is the fastest path — the documented snippet is one import plus one wrapper, so a developer can be live in minutes once the price is set. Hosting a file or pasted JSON is also quick because Loomal hosts and paywalls it for you. Budget longer if you need to add metering logic around the paywall or wire the HMAC-signed webhooks into
Switching to or from Loomal
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From no monetization at all: wrap your existing handler with requirePayment and set a per-call price — no billing service, key store or invoicing to build.
- ↗To a card-based usage-billing stack like Stripe metered billing: you'd need to add API key issuance and human checkout, since Loomal handles neither.
Integrations
Resources & Guides
Tutorials & Learning
YouTube returned 6 videos for “Loomal”, and we withheld 6: 6 could not be judged, because “Loomal” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Loomal.
Official links
Tools that pair well with Loomal
Common stack mates teams adopt alongside Loomal, with the specific reason each pairing earns its keep.
Brain.Md
A persistent, file-based memory layer for coding agents that lives as a Markdown folder in your repo.
Fly.io
Hardware-isolated Linux VMs called Sprites that checkpoint automatically for AI agents, billed per second of active use.
Vercel
Deploy web apps and AI agents with Git-based CI/CD, a global CDN, sandboxed VMs, and one gateway to hundreds of models.
Featured Head-to-Head Comparisons
Loomal vs Spider Cloud
If you need to feed your AI agent real-time web data or scrape at scale cheaply, Spider Cloud wins with its Rust engine, 99.9% success rate, and $0.03/k pages – plus open-source flexibility. If you're building agents that need to pay for services or get paid themselves (USDC paywalls, identity, 2FA), Loomal is the only API on the market that bundles payments, vault, email, and identity in one call. Choose based on whether your bottleneck is data ingestion or agent monetization.
Loomal vs Temporal Ai
Temporal and Loomal solve completely different problems. Temporal is for building reliable, stateful workflows (AI agents, microservices) that survive failures; Loomal is for giving agents an identity and ability to pay for APIs. If you need crash-proof orchestration, pick Temporal. If you need to monetize agent API calls or give agents a wallet/inbox, pick Loomal.
Loomal vs Presto Voice
If you run a QSR drive-thru chain and want to boost revenue with voice AI, Presto Voice is the clear choice — its upselling engine and 95% automation rate deliver measurable ROI. If you're building AI agents that need to pay for APIs or manage identity, Loomal's freemium developer infrastructure is purpose-built for that. They solve completely different problems: drive-thru operations vs. agentic commerce.
Alternatives to Loomal
View all
Frequently Asked Questions
Categories
Best-of guides
Used Loomal? Help shape our editorial sentiment research.