Get paid for your
Five lines on top of any HTTP tool, and you get paid per call. Identity, Mail, Vault, and Calendar live in the same project.
Free during launch · 0.5% fee thereafter · No card · No KYC up to $100
// One import, one wrapper. The SDK does the two-call x402 flow.
import { requirePayment } from "@loomal/sdk/paywall/express";
app.get(
"/api/search",
requirePayment({ amount: "0.01" }),
(req, res) => res.json({ results: [/* ... */] }),
);Open source: nodejs-sdk · python-sdk · cli · mcp
Today, your tool can't
pay, communicate, or do anything a person does.
An AI agent can call your API. It can't charge a cent, hold a key, read mail, or pass a 2FA prompt. Every real-world action falls back to a human. Loomal closes the gap.
Stripe doesn't fit
30¢ + 2.9% per charge, days to integrate, KYC + Connect for marketplaces. Built for cards, not per-call API billing.
Agents have no wallet
An AI agent can call your API but it can't pay you. Without a wallet, there's no way to settle a payment challenge or sign a charge.
Receipts don't exist
When an agent pays, who authorized it? Stripe webhooks aren't an audit trail. There's no on-chain proof of who paid for what.
Agents can't read mail
Receipts, confirmations, magic links, password resets, replies — they all land in a human inbox. Agents can't read them, can't reply, can't act on them.
Secrets sit in clipboards
Agents can't safely hold a password, API key, or card number. So they end up pasted into prompts and chat logs — leaking with every replay.
2FA hands it back to you
Every login asks for a code from your authenticator. Agents can't read your phone, so they stop, ping you, and wait. Automation breaks at the 2FA step.
DIY stack → Loomal Pay
Don't build payment
plumbing.
Stripe Connect, KYC onboarding, invoicing, webhook idempotency, cash-out rails. That's weeks of plumbing before your tool earns its first dollar. Loomal Pay collapses it into a five-line middleware and a project wallet provisioned on signup.
DIY stack
5+ moving partsStripe Connect
KYC · payouts · platform fees
KYC onboarding
state-by-state · ongoing review
Invoicing + receipts
line items · taxes · refunds
Webhook handlers
idempotency · retries · backoff
Cash-out logic
bank rails · 1099s · holds
Loomal Pay
Five-line middleware
Express · Hono · FastAPI · MCP · curl
Project wallet
auto-provisioned on signup
Verify + settle
Base mainnet · seconds · per-call
Signed receipts
+ newEd25519 · verifiable on-chain
Cash-out endpoint
+ newwithdraw to any wallet
The Loomal
Project Stack.
Loomal Pay is the wedge. Identity, Mail, Vault, 2FA, and Calendar live in the same project. One signup, one API key, one audit timeline.
What people charge for
with Loomal Pay.
Five lines of middleware, per-call USDC, no Stripe Connect. Real shapes people are shipping today.
Paid MCP server
Charge AI agents for each tool invocation. Drop the middleware on any tool registration; agents pay before the call returns.
Paid extraction API
PDF parsing, table extraction, OCR. Agent posts a document, your handler returns structured JSON, payment settles per-call.
Paid search API
Index search, web search, vector search. Per-query pricing makes high-volume agent traffic actually viable.
Buyer-side x402
Agent pays for someone else's API. Loomal provisions a smart contract wallet, handles signing, and retries on 402. No private key custody.
Payment audit trail
Every settle is Ed25519-signed and on-chain verifiable. Hand the receipt to your accountant or a regulator. It holds up.
Per-call API metering
Replace seat-based pricing with per-call. Five lines on top of any existing API and revenue follows usage, not subscription.
FINRA · 2024 · fine
$1.1B
in fines for communication attribution failures. Money attribution is next.
When AI agents start moving real money, the same problem gets 10x bigger. Loomal Pay signs every settle with Ed25519 and writes it on-chain. Every payment proves who authorized it. Forever.
See how Loomal Pay receipts workFinance
FINRA · SEC · SOX
Healthcare
HIPAA · Part 11
Legal
FRCP · FRE 502
Defense
CMMC · NIST 800-171
Insurance
UCSPA · RESPA
Every payment traces back
to the agent that authorized it.
Human > Org > Project > Payment. Every settle is Ed25519-signed by Loomal and verifiable on-chain. Revoke a project key and every downstream payment stops. No dangling wallets. No reconciliation scripts.
Human
ops@novaworks.io
Org
novaworks
Identity
sales-agent-x8k2m
Action
email / vault / totp
Ed25519-signed receipts
Every settled payment returns a receipt signed by Loomal's facilitator key. Buyers and sellers verify who paid what and when. No need to trust Loomal.
On-chain proof
Every settle writes a USDC transfer to Base mainnet. The basescan link is the receipt. It is the audit trail.
Instant revocation
Revoke a project key and every paywall, every wallet, every cash-out call stops downstream instantly. No dangling credentials.
Audit-ready timeline
Every challenge, settle, refund, cash-out, and webhook is logged with project ID, timestamp, and signing context. The trail compliance teams actually ask for.
Works with
every framework.
REST API plus a native MCP server. If it speaks HTTP, it works.
Get started
30 seconds to
first paid call.
Sign up. Copy the snippet. Get paid. Identity, Mail, Vault, and Calendar live on the same project.
// One import, one wrapper. The SDK does the two-call x402 flow.
import { requirePayment } from "@loomal/sdk/paywall/express";
app.get(
"/api/search",
requirePayment({ amount: "0.01" }),
(req, res) => res.json({ results: [/* ... */] }),
);