We built an MCP server where your AI agent pays for its own API calls

Hey Product Hunt 👋

We're launching Weftly tomorrow and I wanted to share something that happened during development that I haven't been able to stop thinking about.

I was testing our Claude Code plugin. I had a video file on my laptop. I typed:

"Find me the best clips from this recording."

That was it. That was the whole interaction.

What happened next was invisible to me. And that's exactly the point. Claude called our MCP server. Weftly returned a payment challenge. Claude called mppx to sign it against my wallet. Claude retried the tool call with the payment credential. Weftly started processing. Claude polled for status. When it was done, Claude handed me ranked clip candidates with timestamps, scores, and transcript text.

I didn't approve a payment. I didn't open a dashboard. I didn't switch windows. I didn't copy an API key or click a checkout link. I just asked for clips and got clips.

This is what agent-native payments actually feel like.

We built Weftly on MPP, Machine Payments Protocol, an open standard from Stripe and Tempo. The way it works: when Claude calls a paid Weftly tool without a payment credential, the server returns a payment_required challenge. Claude knows to sign that challenge with mppx against your USDC wallet on Tempo. Claude retries with the credential. The tool proceeds.

No checkout redirect. No human approving each call. No API key that someone has to provision and rotate. The payment is the auth. The agent settles up on your behalf, and you watch the work get done.

What Weftly does with that payment:

→ Transcribes your audio or video to word-level JSON (the format that makes transcript-driven editing possible)
→ Finds your best clip candidates ranked by score, with hooks, timestamps, and full text
→ Cuts horizontal or 9:16 vertical clips ready for TikTok, Reels, and Shorts
→ Returns presigned download links, valid for 24 hours

All from a single conversation. No windows switching. No separate app.

We also open-sourced five free Claude Code editing skills — remove filler words, identify and cut intro clips, write blog posts from transcripts. Free, MIT licensed, forkable. The skills are what I actually use to edit video now. The Weftly API is the layer underneath them.

Launching at midnight tonight. Would love to hear from anyone else building in the MCP + agent payments space — this feels like the beginning of something and I want to compare notes.

One question for the PH community: what would you use autonomous agent payments for if the plumbing already existed? Genuinely curious what use cases people see beyond media and postproduction.