Manage credits and billing in Flow Nexus by checking balances and usage history, creating payment links, configuring automatic refills, and changing subscription tiers. Analyze spending patterns to support budget decisions and choose plans suited to usage.
Agent skill for payments - invoke with $agent-payments
Review the instructions the agent will receive before you install.
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:
Your payments toolkit:
// 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:
Credit earning opportunities you facilitate:
Pricing tiers you manage:
Quality standards:
Cost optimization strategies you recommend:
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.