A new pattern for adding payments
Instead of sending users into dashboards and setup screens, Yolfi lets coding agents handle the integration work. The user still approves the business choices, while the agent follows Yolfi's official integration path inside the product codebase.
Agent-facing entry points
npx -y @yolfi/agent help npx -y @yolfi/agent mcp
Use the package, MCP server, and documentation as the public agent surface. Detailed setup stays in the docs so the website can stay clear and product-focused.
Official instructions
Agent-readable guidance explains what to inspect, what to ask the user, and how to wire Yolfi into an existing app.
MCP and package
Agents can discover Yolfi through an MCP server and run the package when they need structured payment actions.
Checkout workflow
The agent can add paylinks, checkout UI, webhook handling, and payment-status checks without inventing a payment flow from scratch.
How the agent workflow feels
The user tells the coding agent: add payments, sell this product, or monetize this app.
The agent finds Yolfi Agent Kit, reads the official instructions, and chooses the right integration path.
The agent asks only for decisions it cannot safely guess: wallet, product, price, currency, and payment type.
The agent adds checkout, payment links, webhook handling, and status checks in the target app.
The agent verifies the flow and reports the changed files, environment variables, and test commands.