No reviews yetBe the first to leave a review for AiFinPay
Maker
📌
Hi Product Hunt! 👋
I'm Dmitry, founder of AiFinPay.
We built AiFinPay because AI agents can already search, analyze, write code, and make decisions—but they still can't pay for APIs, digital products, or services on their own.
AiFinPay provides payment infrastructure for AI agents. Developers can integrate AI-native payments using our SDK and MCP, enabling autonomous agents to pay with crypto across multiple blockchains.
Today we're launching our first public version, and we're looking for feedback from developers, AI builders, and companies building AI products.
What we'd love to hear:
Would you let an AI agent make payments on your behalf?
What use case should we support next?
What would stop you from integrating AiFinPay?
We'll be here all day answering every question. Thanks for checking us out! 🚀
Report
The 98.99/1/0.01 split is clever for creator attribution. One thing that would help adoption though is a built-in spend cap per agent session, so you can safely let an agent call paid providers without worrying about runaway costs if it loops. A simple set_max_per_session(satoshi) on the SDK would close that gap.
Report
💡 Bright idea
Since you're already OpenAI-compatible, adding webhook callbacks for failed or pending transactions would save a lot of polling headaches for agents running in production. Right now there's no clear way for an agent to know if a call settled without re-querying state.
Report
🧐 Good find
finally something that lets agents actually pay without me babysitting the tx. the one-call settle and the fee split routing are exactly the kind of plumbing that has been missing.
The 98.99/1/0.01 split is clever for creator attribution. One thing that would help adoption though is a built-in spend cap per agent session, so you can safely let an agent call paid providers without worrying about runaway costs if it loops. A simple set_max_per_session(satoshi) on the SDK would close that gap.
Since you're already OpenAI-compatible, adding webhook callbacks for failed or pending transactions would save a lot of polling headaches for agents running in production. Right now there's no clear way for an agent to know if a call settled without re-querying state.
finally something that lets agents actually pay without me babysitting the tx. the one-call settle and the fee split routing are exactly the kind of plumbing that has been missing.