The problem AgentPays solves

AgentPays solves the problem of AI agents not being able to pay for tools or APIs on their own.

It lets agents like Claude automatically send crypto payments (via x402) when calling a tool that requires it — no manual setup, no logins. Tools can define their own prices, and payments are enforced directly in the MCP protocol.

Basically: it makes machine-to-machine payments real and automatic.

Challenges I ran into

... a lot ...

Both technologies, MCP and x402, are still in very early stages. MCP supports multiple transport protocols, each of which comes with its own challenges. Even though the protocol is only about 8 months old, the transport methods SSE is already deprecated, while other websites are just beginning to adopt this now "outdated" standard. I will "stick" with SSE until non-sticky solutions (stateless) are working on all use cases

With x402, it's still quite unclear what it might eventually evolve into. I focused on the "exact" scheme because it's the most clearly defined so far. I’ve considered adding support for multiple chains simultaneously, but it’s not fully implemented yet. The complexity grows exponentially when you factor in different wallets, chains, routes, and payment methods.

I’m optimistic that x402 could work as global standard. However, the specification should be more clearly defined. The "exact" scheme is somewhat ambiguous, and there are also inconsistencies within EIP-3009. That was actually the hardest part for me at the beginning—understanding what exactly was meant by "exact".