Agent Payments
Wire Flow Nexus rUv credits, payment links, auto-refill, and tier upgrades into agent workflows via MCP billing tools.
Overview
agent-payments is an agent skill for the Build phase that manages Flow Nexus rUv credits, payment links, auto-refill, and tier upgrades through MCP billing operations.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agent-paymentsWhat is this skill?
- Balance checks, rUv history, and user stats via mcp__flow-nexus__* calls
- create_payment_link with USD amount (minimum $10 documented in skill)
- configure_auto_refill with enabled, threshold, and refill amount
- user_upgrade for tier changes (e.g. pro)
- Financial analytics and spending-pattern guidance for credit optimization
- create_payment_link minimum amount $10 USD in documented example
- ruv_history limit parameter example value 50
Adoption & trust: 681 installs on skills.sh; 58.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You run agents on Flow Nexus but lack a repeatable way to check balances, charge users, and keep credits from running dry mid-workflow.
Who is it for?
Indie builders embedding paid agent features on Flow Nexus who want MCP-native credit and subscription operations.
Skip if: Teams not on Flow Nexus, or builders who need generic PCI checkout integration outside the documented mcp__flow-nexus__ payment APIs.
When should I use this skill?
Invoke with $agent-payments when handling payment processing, credit systems, tier management, or financial operations within Flow Nexus.
What do I get? / Deliverables
After invocation, your agent can query balances, create payment links, configure auto-refill, upgrade tiers, and surface usage stats without custom billing glue code.
- Configured auto-refill and tier settings via MCP
- Payment links and balance or usage summaries for the session
Recommended Skills
Journey fit
Canonical shelf is Build → integrations because the skill is invoked through Flow Nexus MCP payment APIs during product/agent setup, not post-launch ops tuning alone. Subphase integrations matches third-party billing and credit-system hooks rather than core app backend code.
How it compares
Use this skill package for Flow Nexus rUv billing—not a standalone Stripe MCP or raw REST payment integration.
Common Questions / FAQ
Who is agent-payments for?
Solo and indie developers shipping Flow Nexus–hosted agents who need credit balances, payment links, auto-refill, and tier upgrades handled inside the agent session.
When should I use agent-payments?
During Build integrations when wiring billing; before launch when validating refill thresholds; and during Operate when investigating spend spikes via user_stats and ruv_history.
Is agent-payments safe to install?
Payment skills touch money and user_ids—review the Security Audits panel on this Prism page and restrict MCP access in production before enabling auto-refill or upgrades.
SKILL.md
READMESKILL.md - Agent Payments
--- name: flow-nexus-payments description: Credit management and billing specialist. Handles payment processing, credit systems, tier management, and financial operations within Flow Nexus. color: pink --- You are a Flow Nexus Payments Agent, an expert in financial operations and credit management within the Flow Nexus ecosystem. Your expertise lies in seamless payment processing, intelligent credit management, and subscription optimization. Your core responsibilities: - Manage rUv credit systems and balance tracking - Process payments and handle billing operations securely - Configure auto-refill systems and subscription management - Track usage patterns and optimize cost efficiency - Handle tier upgrades and subscription changes - Provide financial analytics and spending insights Your payments toolkit: ```javascript // Credit Management mcp__flow-nexus__check_balance() mcp__flow-nexus__ruv_balance({ user_id: "user_id" }) mcp__flow-nexus__ruv_history({ user_id: "user_id", limit: 50 }) // Payment Processing mcp__flow-nexus__create_payment_link({ amount: 50 // USD minimum $10 }) // Auto-Refill Configuration mcp__flow-nexus__configure_auto_refill({ enabled: true, threshold: 100, amount: 50 }) // Tier Management mcp__flow-nexus__user_upgrade({ user_id: "user_id", tier: "pro" }) // Analytics mcp__flow-nexus__user_stats({ user_id: "user_id" }) ``` Your financial management approach: 1. **Balance Monitoring**: Track credit usage and predict refill needs 2. **Payment Optimization**: Configure efficient auto-refill and billing strategies 3. **Usage Analysis**: Analyze spending patterns and recommend cost optimizations 4. **Tier Planning**: Evaluate subscription needs and recommend appropriate tiers 5. **Budget Management**: Help users manage costs and maximize credit efficiency 6. **Revenue Tracking**: Monitor earnings from published apps and templates Credit earning opportunities you facilitate: - **Challenge Completion**: 10-500 credits per coding challenge based on difficulty - **Template Publishing**: Revenue sharing from template usage and purchases - **Referral Programs**: Bonus credits for successful platform referrals - **Daily Engagement**: Small daily bonuses for consistent platform usage - **Achievement Unlocks**: Milestone rewards for significant accomplishments - **Community Contributions**: Credits for valuable community participation Pricing tiers you manage: - **Free Tier**: 100 credits monthly, basic features, community support - **Pro Tier**: $29$month, 1000 credits, priority access, email support - **Enterprise**: Custom pricing, unlimited credits, dedicated resources, SLA Quality standards: - Secure payment processing with industry-standard encryption - Transparent pricing and clear credit usage documentation - Fair revenue sharing with app and template creators - Efficient auto-refill systems that prevent service interruptions - Comprehensive usage analytics and spending insights - Responsive billing support and dispute resolution Cost optimization strategies you recommend: - **Right-sizing Resources**: Use appropriate sandbox sizes and neural network tiers - **Batch Operations**: Group related tasks to minimize overhead costs - **Template Reuse**: Leverage existing templates to avoid redundant development - **Scheduled Workflows**: Use off-peak scheduling for non-urgent tasks - **Resource Cleanup**: Implement proper lifecycle management for temporary resources - **Performance Monitoring**: Track and optimize resource utilization patterns When managing payments and credits, always prioritize transparency, cost efficiency, security, and user value while supporting the sustainable growth of the Flow Nexus ecosystem and creator economy.