Launched this week
PayWeave
Per-call payments + auto-discovery for any API
3 followers
Per-call payments + auto-discovery for any API
3 followers
Drop-in payments and instant discovery for any API, function, or file. AI agents find you and pay automatically. checkout, no invoices, no manual listings. Built on MPP, the open protocol for agent commerce.
Hey Product Hunt 👋, I'm Shiva, building PayWeave with my co-founder Kapil.
AI agents are calling APIs autonomously, but every payment rail still assumes a human at a checkout. PayWeave is the drop-in payment + discovery layer for the agent economy. Add per-call pricing in a minute, and your endpoints become discoverable, payable, and refundable, automatically.
Four ways to monetize
🧩 Apps: one-line SDK for Express, Hono, Fastify, Next.js, Astro
🛡 Gateways: reverse-proxy any existing API, zero code changes
⚡ Functions: serverless TypeScript handlers with built-in pricing
📁 Files: sell datasets, models, documents per-download
Discovery, built-in
Auto-listed on the public marketplace and exposed via MCP server (Claude, Cursor) and llms.txt. Agents find your endpoints by name, see the price, and pay.
Already shipped
- Automatic 402 challenge + retry, multi-currency (USDC.e, pathUSD)
- Real-time stablecoin settlement to your wallet
- Dynamic per-call pricing
- Refunds: single and batched
- On-chain referral splits via ?ref=WALLET (0.5% default, up to 10%)
- Analytics: revenue, payers, latency, CSV export
- Three ways to invoke: TypeScript SDK, mppx CLI, Tempo wallet
Pricing
Free tier covers everything end-to-end with a 2% platform fee.
What's next (transparent roadmap on the site): Solana + Base, workspace teams, custom domains, prepaid credits, streaming endpoints, marketplace reviews, OpenAPI 3.1 generation.
MONETIZATION SURFACES
🧩 Apps, SDK middleware
You import a one-line middleware in your Express/Hono/Fastify/Next.js/Astro app. Any route you wrap requires payment; PayWeave handles the 402 handshake, signs the receipt, records the payment, and lets the request through. Best for new APIs you're building.
🛡 Gateways, reverse proxy
You point PayWeave at an existing API URL (yours or someone else's), set a price per route, and PayWeave proxies every call, charges first, forwards second. Zero code changes to the upstream. Best for legacy APIs you can't or don't want to touch.
⚡ Functions, serverless handlers
You paste a TypeScript function into the dashboard, set a price, and PayWeave deploys it on a sandboxed runtime with built-in pricing, secrets management, and metering. Best when you don't want to host anything yourself.
📁 Files, paid downloads
Upload a dataset, model, or document. PayWeave issues a paywalled download URL. Each download is a paid request. Best for data sellers, model creators, and digital-good shops.
DISCOVERY, HOW AI AGENTS FIND YOU ?
Public marketplace
Every endpoint you publish on PayWeave is automatically listed at a public marketplace URL with price, schema, and example invocation. No SEO, no manual submission.
MCP server
PayWeave exposes a Model Context Protocol server at /mcp. Claude Desktop, Cursor, and any MCP-compatible agent can list, search, and call your endpoints by name without you writing integration code per agent.
llms.txt
A workspace-scoped llms.txt file describes all your endpoints in a format LLMs are trained to read. Drop the URL into any agent's system prompt and it knows what you sell.
PAYMENT MECHANICS
Automatic 402 challenge + retry
The MPP/x402 protocol uses HTTP 402 to challenge unpaid requests. The agent's client signs the challenge, retries, and the call goes through. PayWeave runs the entire dance so you don't have to think about it.
Multi-currency (USDC.e, pathUSD)
Each 402 response can offer multiple stablecoin options. Agents pick the one they hold, so you don't lose a sale because someone has the "wrong" token.
Real-time stablecoin settlement
The moment the on-chain payment confirms, the funds are in your wallet. No daily payout cycles, no holding periods.
Dynamic per-call pricing
The price isn't fixed at publish time. You can compute it at request time (e.g., charge by token count, image size, or compute cost) and pass the amount to PayWeave just before responding.
OPERATIONS
Refunds, single + batched
Refund a single transaction with a reason, or queue a batch refund and execute them in one on-chain transaction (saves gas and time).
On-chain referral splits
Anyone who shares your endpoint with ?ref=THEIR_WALLET automatically earns a configurable percentage of every payment, split in the same on-chain transaction. No claiming, no payouts. Default 0.5%, max 10%.
Analytics
Revenue over time, unique payers, latency, error rates, per-endpoint breakdown. CSV export for accounting.