Yolfi AI Agent Kit

Let your AI agent build the payment flow

Describe what you sell. Codex, ChatGPT, Claude, Cursor, or another agent can connect to Yolfi, create or reuse payment links, implement checkout and verified webhooks, then test the flow — with you approving account access and business decisions.

Browser-approved access
Scoped agent credentials
Non-custodial by design
Tell your agentYolfi MCP

“Add crypto payments to this app with Yolfi. Reuse existing payment links, wire verified webhooks, and test the checkout.”

The agent can

Inspect your Yolfi workspace and project
Create or reuse payment links
Implement checkout and verified webhooks
Run tests and report every change

One prompt. A complete payment path.

Give the agent the business goal. Yolfi provides the payment tools and product guidance while the agent works inside your app.

SaaS and memberships

Create recurring payment links and wire access logic to confirmed payment events.

Digital products and paid access

Sell files, tools, credits, or gated content with one-time checkout and verified fulfillment.

Games and marketplaces

Add item, credit, or order payments with references your backend can reconcile.

Donations and creator support

Launch a hosted payment page and track confirmed contributions without holding customer funds.

Start with your agent

Choose the client you use. Hosted clients open OAuth in a browser; local-only clients can use the package setup flow.

Choose an AI agent

Codex

Open full setup
codex mcp add yolfi --url https://app.yolfi.com/mcp
codex mcp login yolfi

Once connected, ask the agent to run yolfi_auth_status, inspect the organization, and list existing payment links before changing anything.

Choose how your agent connects

Use Yolfi cloud MCP when your agent supports browser OAuth. Use the local package when it can run commands. Both paths expose the same payment tools.

MCP

Hosted MCP server

A remote MCP endpoint for compatible clients. Authentication happens through Yolfi OAuth in the browser.

https://app.yolfi.com/mcpCLI / MCP

Local setup and stdio MCP

Start browser setup, save a scoped local credential, and run the MCP server through the package.

npx -y @yolfi/agentnpm

Official npm package

CLI commands, local MCP transport, setup, check-in, and agent-readable resources in one package.

@yolfi/agentGitHub

Source and examples

Review the package source, integration examples, MCP metadata, and agent instructions.

yolfinance/yolfi-agent

Your approval stays in the loop

The agent gets a dedicated connection, not your password or wallet keys. Choose the authorization path that matches where it runs.

Hosted MCP + OAuth

For clients with remote MCP support. The client opens Yolfi in a browser; the user signs in or creates an account and approves access. The agent receives a scoped token, never the password.

Local browser setup

For agents that can run terminal commands. Setup prints a one-time browser URL; after approval, check-in stores the agent credential locally and MCP runs over stdio.

API key for CI

For headless jobs, CI, and server automation. Create and revoke keys manually, keep them in environment variables, and avoid them for interactive agent sessions.

Connection status belongs in the agent. A public MCP endpoint being reachable does not mean your agent is authenticated. After OAuth, ask the agent to run yolfi_auth_status.

From account context to production-ready checkout

Yolfi provides product guidance and structured payment actions. Your coding agent combines them with your codebase and verifies the result.

Inspect before changing

Read organization state, settlement configuration, existing payment links, and official integration guidance first.

Use structured MCP tools

Check authentication, create or reuse payment links, and work with payment configuration through explicit tools.

Implement the product flow

Add checkout UI, payment-status handling, webhook verification, environment variables, and tests in the target app.

What happens after you ask

The user asks the agent to add payments or monetize a product.

The agent connects to Yolfi through hosted MCP or the local package.

A Yolfi browser page handles sign-in or registration and asks the user to approve access.

The agent inspects the workspace and asks only for business decisions it cannot safely infer.

The agent implements and verifies the integration, then reports changes, configuration, and tests.

Works across agent surfaces

Use the same Yolfi account and tools through the connection method supported by each client.

CodexRemote MCP with browser OAuth, plus local MCP and CLI options.
ChatGPTCustom app connection to the hosted MCP server with OAuth.
ClaudeCustom connector to hosted MCP with browser authorization.
Claude CodeRemote HTTP MCP, local stdio MCP, or CLI setup from the terminal.
CursorRemote or local MCP configuration while Cursor edits the app.
OpenClawLocal package setup and stdio MCP for a shell-capable agent.
HermesRemote OAuth MCP or the local package flow.
Other MCP hostAny compatible MCP host can use the remote URL or local stdio server.

Simple pricing for
all businesses

1%

Questions before you connect an agent

What the agent can access, what you still approve, and which connection works where.

Give your agent a safe way to ship payments

Choose an agent, approve access in Yolfi, and let it turn your payment requirements into a tested checkout flow.