Yolfi
Yolfi Agent Kit for AI coding agents: receive crypto, SaaS payment, stablecoin checkout, payment links, payment status checks, webhook verification, and webhook-based access logic to applications through Yolfi
README

Yolfi Agent Kit
AI agent payment integration for crypto checkout. Yolfi Agent Kit is a JSON-first SDK, CLI, Agent Skill, and MCP server that lets AI coding agents add stablecoin checkout, payment links, payment status checks, webhook verification, and webhook-based access logic to applications through Yolfi.
Use @yolfi/agent when Codex, Claude Code, Cursor, OpenClaw, an MCP host, or a custom AI agent can build the product but still needs a reliable payment API to register a Yolfi workspace, create a paylink, configure webhooks, and verify crypto payment status without sending the user through manual dashboard setup.
Website | Agent Kit | Docs | npm | GitHub | Glama | Guide
Languages
Read this package guide in: English, Español, Deutsch, Français, 简体中文, Русский, हिन्दी, Türkçe, 한국어, 日本語.
Why Developers Use It
- Add AI agent payments to SaaS products, games, marketplaces, donation pages, digital downloads, internal tools, and agent-built apps.
- Give coding agents a safe payment workflow: inspect the app, register or reuse a workspace, ask for wallet and price decisions, create paylinks, install checkout, verify webhooks, and check payment status.
- Use one package for MCP crypto payments, JSON CLI automation, JavaScript SDK calls, webhook signature verification, and agent-readable instructions.
- Build with the existing Yolfi API instead of maintaining a second agent-only payment API.
- Help agents discover Yolfi through npm, GitHub, MCP directories,
llms.txt, docs, examples, and integration guides.
Yolfi handles crypto payment infrastructure, hosted checkout, paylinks, public payment invoices, organization settings, settlement wallet configuration, and webhook delivery. Your agent handles project inspection, code changes, user confirmation, and target-app integration.
What It Can Add To An App
- Hosted crypto checkout through Yolfi paylinks.
- One-time payment links for digital products, credits, files, tools, or game items.
- Recurring or subscription-style payment link setup when the Yolfi account supports it.
- Donation and creator-support payment pages.
- Server routes that create public payment invoices from a paylink.
- Payment status polling through Yolfi public payment endpoints.
- Webhook handlers that verify
X-Yolfi-Signature. - Webhook-based entitlement logic that unlocks access only after confirmed payment events.
- Agent workflows for Codex, Claude Code, Cursor, OpenClaw, and custom automation.
Agent Skill
This package includes the Yolfi Payments Skill in SKILL.md. Use it with coding agents when the user asks to add crypto payments, payment links, checkout, subscriptions, donations, paid downloads, paid access, or webhook-based entitlements.
Recommended safe workflow:
inspect app -> check YOLFI_API_KEY -> register if needed -> ask user for wallet and price -> configure organization -> create or reuse paylink -> add checkout -> add webhook verification -> verify status
The skill tells agents what they may do automatically and what they must ask the user to decide. Agents must never invent wallet addresses, prices, plans, currencies, secret storage locations, or destructive paylink actions.
Install
Install in a project:
npm install @yolfi/agent
Or run without installing:
npx -y @yolfi/agent help
Start the stdio MCP server:
npx -y @yolfi/agent mcp
For local development inside this repository:
node packages/yolfi-agent/src/cli.js help
Authentication
Private commands use a Yolfi organization API key:
export YOLFI_API_KEY="yolfi_..."
The CLI and MCP server use Yolfi production API and checkout URLs by default.
If the target app does not already have YOLFI_API_KEY, an agent can register a workspace through the agent registration endpoint:
yolfi auth:agent-register \
--project-name "Space Shop" \
--agent-name "Codex" \
--integration-intent accept_payments \
--ref npm
The returned API key is shown once. Store it in an ignored env file, deployment secret, or secret manager. Do not print the full key in logs, commit it, or write it into README files in the target project.
Quick Start
Check the workspace linked to the API key:
yolfi auth:status
Configure settlement wallets after the user provides wallet addresses:
yolfi settlement:configure --json examples/organization.settlement.json
Configure webhook delivery:
yolfi webhooks:configure \
--url https://example.com/api/yolfi/webhook \
--adapter STRIPE
List existing paylinks before creating duplicates:
yolfi paylinks:list --page 1 --rows 10
Create a one-time payment link:
yolfi paylinks:create --json examples/paylink.one-time.json
Create a public payment invoice from a paylink:
yolfi payments:create --json examples/payment.create.json
Check payment status:
yolfi payments:status --id <paymentId>
Every CLI command prints JSON so agents can parse results without scraping terminal text.
MCP Server For Crypto Payments
Yolfi Agent Kit includes a stdio MCP server in the same npm package:
{
"mcpServers": {
"yolfi-api": {
"command": "npx",
"args": ["-y", "@yolfi/agent", "mcp"],
"env": {
"YOLFI_API_KEY": "..."
}
},
"yolfi-knowledge": {
"command": "npx",
"args": ["-y", "@yolfi/agent", "mcp"]
}
}
}
yolfi_agent_register calls the public agent registration endpoint and does not require YOLFI_API_KEY. Private yolfi-api tools require the API key returned by registration. yolfi-knowledge resources help an agent understand the integration path before a key exists.
Available MCP tools:
yolfi_agent_registeryolfi_auth_statusyolfi_organization_getyolfi_organization_updateyolfi_settlement_configureyolfi_webhooks_configureyolfi_paylinks_createyolfi_paylinks_listyolfi_paylinks_getyolfi_paylinks_disableyolfi_payments_createyolfi_payments_statusyolfi_webhooks_verify
Destructive tools such as yolfi_paylinks_disable must only run after explicit user confirmation.
JSON Workflow For Agents
Agents can write a payload file and pass it to the CLI:
{
"name": "Premium Download",
"description": "One-time access to a digital product.",
"type": "ONE_TIME",
"price": "19",
"currency": "USD",
"collectEmail": true,
"metadata": {
"source": "agent",
"productSlug": "premium-download"
}
}
Then run:
yolfi paylinks:create --json ./paylink.json
Agents should keep the returned paylink ID in env/config for the target app and use Yolfi public payment endpoints for customer-facing checkout and status polling.
Commands
yolfi auth:agent-register --project-name "App" --agent-name "Codex" --integration-intent accept_payments
yolfi auth:status
yolfi organization:update --json organization.json
yolfi settlement:configure --json settlement.json
yolfi webhooks:configure --url https://example.com/api/yolfi/webhook --adapter STRIPE
yolfi paylinks:create --json paylink.json
yolfi paylinks:list --page 1 --rows 10
yolfi paylinks:get --id <paylinkId>
yolfi paylinks:disable --id <paylinkId> --confirm
yolfi payments:create --json payment.json
yolfi payments:status --id <paymentId>
yolfi webhooks:verify --payload payload.json --signature <signature>
yolfi mcp
Endpoint Adapter Matrix
Yolfi Agent Kit does not create a second /api/agent/* API. It maps agent actions to the current Yolfi API:
| Agent action | Backend endpoint | Auth |
|---|---|---|
| Register Yolfi workspace | POST /api/auth/agent/register |
public; no API key required |
| Check account | GET /api/private/organization/current |
bearer API key |
| Configure organization, webhook, settlement wallets | PUT /api/private/organization/current |
bearer API key |
| Get API key status | GET /api/private/organization/api-key |
bearer API key or cookie |
| Create paylink | POST /api/private/paylinks/create |
bearer API key |
| List paylinks | GET /api/private/paylinks |
bearer API key |
| Get paylink | GET /api/private/paylinks/:id |
bearer API key |
| Edit paylink | POST /api/private/paylinks/edit |
bearer API key |
| Disable paylink | POST /api/private/paylinks/disable |
bearer API key plus confirmation |
| Public paylink checkout info | GET /api/public/paylinks/:id |
public |
| Create public payment invoice | POST /api/public/payments |
public |
| Payment status | GET /api/public/payments/:id |
public |
| Merchant transactions | GET /api/private/transactions |
bearer API key |
SDK
import { YolfiClient } from "@yolfi/agent";
const yolfi = new YolfiClient({
apiKey: process.env.YOLFI_API_KEY,
});
const account = await yolfi.authStatus();
const paylink = await yolfi.createPaylink({
name: "Premium Download",
description: "One-time access to a digital product.",
type: "ONE_TIME",
price: "19",
currency: "USD",
collectEmail: true,
metadata: {
source: "agent",
productSlug: "premium-download",
},
});
console.log(account.success);
console.log(paylink.data?.id ?? paylink.id);
Webhook Verification
Yolfi signs webhook payloads with X-Yolfi-Signature. Verify the raw request body before parsing and trusting the event:
import { verifyWebhookSignature } from "@yolfi/agent";
const valid = verifyWebhookSignature(
rawBody,
request.headers["x-yolfi-signature"],
process.env.YOLFI_API_KEY,
);
if (!valid) {
throw new Error("Invalid Yolfi webhook signature");
}
Do not treat a frontend redirect as proof of payment. Use verified webhooks and Yolfi payment status checks.
Use With AI Coding Agents
Yolfi Agent Kit is designed for agentic payment workflows where the user gives a high-level instruction like "add payments", "sell this digital product", "add a donation button", "charge for this game", or "gate this feature behind payment".
- Codex: inspect the repo, add checkout routes/components, configure env vars, and wire verified webhooks into existing entitlement logic.
- Claude Code: use the MCP server and Agent Skill to add payment links, server handlers, and status checks with user approval for wallet and price decisions.
- Cursor: add payment UI and backend handlers while keeping Yolfi keys out of committed source.
- OpenClaw and custom agents: connect product-building workflows to Yolfi through CLI, SDK, MCP tools, and JSON payloads.
Recommended agent path:
auth:status -> organization:get -> paylinks:list -> user approval -> settlement:configure -> webhooks:configure -> paylinks:create -> install checkout -> verify webhook -> payments:status
Agent Recipes
The examples/ folder includes copy-paste workflows and JSON payloads:
examples/codex/add-yolfi-payments.mdexamples/claude-code/add-yolfi-payments.mdexamples/cursor/add-yolfi-payments.mdexamples/paylink.one-time.jsonexamples/paylink.recurring.jsonexamples/organization.settlement.jsonexamples/payment.create.jsonexamples/webhook.stripe-adapter.json
What This Package Is Not
- It is not a separate Yolfi dashboard.
- It is not a wallet provider.
- It is not a second payment API with duplicated business logic.
- It does not invent settlement wallets, product names, prices, currencies, subscriptions, or donation amounts.
- It does not bypass user confirmation for destructive actions.
- It does not store secrets in source code.
- It does not use redirects as payment confirmation.
Current Limits
- The MCP server currently uses stdio transport.
- Webhook signing uses the current Yolfi signature contract. If Yolfi separates webhook secrets from organization API keys later, this package will expose the new secret configuration path.
- Agent registration returns the API key once. Agents must store it in an ignored env file, deployment secret, or secret manager.
- Final payment confirmation should come from verified webhooks and payment status checks, not from UI redirects.
- MCP directory approval is separate from this package. Do not claim official directory approval until a listing is accepted.
Search Phrases This Package Serves
Developers and agent builders often look for:
- AI agent payment integration
- AI coding agent payments
- MCP payment server
- MCP crypto payments
- crypto checkout API for agents
- payment links for AI agents
- stablecoin checkout for apps
- webhook payment verification
- agentic payment workflow
- add crypto payments with Codex, Claude Code, or Cursor
Yolfi Agent Kit is the package entry point for those workflows.
Links
- Yolfi: https://yolfi.com
- Agent Kit page: https://yolfi.com/ai-agent-kit
- Docs: https://docs.yolfi.com/en/agent-kit
- LLM index: https://docs.yolfi.com/llms.txt
- Full LLM context: https://docs.yolfi.com/llms-full.txt
- npm package: https://www.npmjs.com/package/@yolfi/agent
- GitHub repo: https://github.com/yolfinance/yolfi-agent
- Glama MCP listing: https://glama.ai/mcp/servers/yolfinance/yolfi-agent
- Integration guide: https://yolfi.com/blog/ai-agent-payment-integration-api
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.