Yolfi Agent Kit is an AI agent payment integration toolkit launched by Yolfi, used for crypto checkout scenarios. It is a JSON-first SDK, CLI, Agent Skill, and MCP server that enables AI coding agents to add stablecoin checkout, payment links, payment status queries, Webhook verification, and Webhook-based access logic to applications through Yolfi.
[Purpose] Developers can use it for SaaS products, games, marketplaces, donation pages, digital downloads, internal tools, and agent-built applications to add AI agent payment capabilities. It gives coding agents a secure payment workflow: inspect the application, authorize or reuse a workspace, ask about wallet and pricing decisions, create a paylink, install checkout, verify Webhooks, and check payment status.
[Main Capabilities]
- Provide hosted crypto checkout through Yolfi paylink.
- Create one-time payment links for digital products, credits, files, tools, or game items.
- Set up recurring or subscription-style payment links when supported by the Yolfi account.
- Donation and creator support payment pages.
- Server-side routes that create public payment invoices from a paylink.
- Poll payment status through Yolfi public payment endpoints.
- Webhook handlers that verify X-Yolfi-Signature.
- Webhook-based authorization logic that unlocks access only after a payment event is confirmed.
- Agent workflows for Codex, Claude Code, Cursor, OpenClaw, and custom automation.
[Usage] The package includes the Yolfi Payments Skill in SKILL.md. Installation is done within the project, or it can be run directly without installation; a stdio MCP server can be started. For local development, the recommended process is to open a browser for authorization and store the generated yolfi_agent_* credentials in ~/.yolfi/config.json. The configuration directory and files are created with 0700 and 0600 permissions in supported environments, and the configuration directory can be overridden via YOLFI_CONFIG_HOME. Explicit credentials remain valid and take precedence over stored credentials. The CLI and local MCP server also support registering new Yolfi users via email confirmation: the first call creates a pending registration, sends a confirmation link to allowners and stores a protected check-in token locally; after the owner opens the link and runs the same command again, the second call checks the pending registration, stores the one-time yolfi_agent_* credentials in the protected local configuration, and removes the full credentials from CLI/MCP output. This command is only for registration; if the email already has a Yolfi account, OAuth or local browser setup should be used.
CLI command examples include: checking the workspace associated with the API key; configuring the settlement wallet after the user provides a wallet address; configuring one or more Webhook endpoints (delivery, retries, and signing keys are each independent, and the CLI stores each created/rotated key in the protected local Yolfi configuration, printing only masked metadata); listing existing paylinks to avoid creating duplicates; creating a one-time payment link; creating a public payment invoice from a paylink; checking payment status. Each CLI command outputs JSON for easy parsing by agents.
The MCP server provides a production streamable HTTP endpoint and a local stdio server. Available MCP tools include: yolfi_agent_setup_start, yolfi_agent_checkin, yolfi_agent_register, yolfi_auth_status, yolfi_organization_get, yolfi_organization_update, yolfi_settlement_configure, yolfi_webhooks_configure, yolfi_webhooks_list, yolfi_webhooks_update, yolfi_webhooks_rotate_secret, yolfi_webhooks_delete, yolfi_paylinks_create, yolfi_paylinks_list, yolfi_paylinks_get, yolfi_paylinks_disable, yolfi_payments_create, yolfi_payments_status, yolfi_webhooks_verify. The Webhook create/rotate tools store the one-time signing key in the protected local Yolfi configuration and never expose it through the CLI stdout or MCP records return plaintext. Destructive tools (such as yolfi_paylinks_disable) must only be run after explicit user confirmation.
The agent can write payload files and pass them to the CLI, should save the returned paylink ID in the target application's environment variables/config, and use Yolfi's public payment endpoints for customer-facing checkout and status polling. For webhook verification, Yolfi uses X-Yolfi-Signature to sign webhook payloads, and the raw request body should be verified before parsing and trusting events; do not treat frontend redirects as payment proof, and instead use verified webhooks and Yolfi payment status checks.
[Working with AI coding agents] This toolkit is designed for agentic payment workflows, where users give high-level instructions such as "add payments", "sell this digital product", "add a donate button", "charge for this game", or "put a feature behind payment". Codex can inspect the repository, add checkout routes/components, configure environment variables, and connect verified webhooks to existing authorization logic; Claude Code can use the MCP server and Agent Skill to add payment links, server-side handlers, and status checks, while wallet and pricing decisions require user approval; Cursor can add payment UI and backend handlers while avoiding committing Yolfi keys to source code; OpenClaw and custom agents can connect to product-building workflows through the CLI, SDK, MCP tools, and JSON payloads. The examples/ folder contains copy-pasteable workflows and JSON payload examples.
[Limitations] It is not a standalone Yolfi dashboard, not a wallet provider, and not a second payment API with duplicated business logic. It will not invent settlement wallets, product names, prices, currencies, subscriptions, or donation amounts on its own; will not bypass user confirmation for destructive operations; will not store keys in source code; and will not use redirects as payment confirmation. ChatGPT web version can only use remote MCP endpoints via plugins and cannot launch local stdio packages. Each webhook endpoint has its own signing secret, and the organization API key is never used as a signing secret. Browser settings return agent credentials only once upon successful sign-in. Final payment confirmation should come from verified webhooks and payment status checks. MCP directory approval and thispackage are independent of each other; do not claim official directory approval before the listing is accepted.
Official website:https://yolfi.com Agent Kit page:https://yolfi.com/ai-agent-kit Documentation: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 repository: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
