A
licenseA
qualityB
maintenanceLets AI agents discover, pay for, and call any HTTP API per request using USDC, with gasless nanopayments and no API keys or accounts needed.
5
47 npm
MIT
🍋 LemonCake — Billing & budgets for AI agents
by evidai
Related Servers
Alternatives to 🍋 LemonCake — Billing & budgets for AI agents
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to manage USDC wallets on Solana, allowing them to send payments, create invoices, and access paid APIs within human-defined spending limits. It uses threshold signatures to provide agents with financial autonomy while ensuring secure oversight and transaction approval.36286 npm3Apache 2.0
@arispay/payagent-mcpofficial
AlicenseAqualityAmaintenanceEnables AI agents to call paid APIs and settle HTTP 402 payment challenges with USDC on Base, without private keys ever being involved.796 npmMIT- AlicenseNot gradedqualityBmaintenanceUSDC payments for AI agents on Base. Direct transfers, pre-funded tabs, x402 paywall handling, and service discovery.24 npmMIT
- AlicenseAqualityBmaintenanceProvides pay-per-use tools for AI agents like web screenshots and crypto intelligence using automatic USDC micropayments on the Base network. It simplifies access to premium APIs by handling blockchain transactions automatically when a payment is required.1210 npmMIT
@hpp-io/x402-mcp-bridgeofficial
AlicenseNot gradedqualityAmaintenanceEnables AI agents to autonomously pay for and discover services using HPP USDC.e over the x402 protocol, without API keys or manual signing.93 npmApache 2.0
TDQS
A4.7/5.0
Scored across 6 tools
Disambiguation5/5
Each tool has a clearly distinct role: setup guides onboarding, list_services discovers offerings, call_service executes paid calls, check_balance monitors funds, check_tax handles compliance, and get_service_stats provides marketplace analytics. There is no meaningful overlap or ambiguity between them.
Naming Consistency5/5
Tool names follow a consistent snake_case verb_noun pattern: list_services, call_service, check_balance, check_tax, get_service_stats. Even 'setup' fits as a single-word imperative without breaking the overall stylistic consistency.
Tool Count5/5
Six tools is a well-scoped count for a billing/proxy service: onboarding, discovery, execution, balance checking, tax compliance, and usage stats each earn their place. The server feels neither bloated nor thin.
Completeness4/5
The core lifecycle is well covered: discover services, call them, check balance, and verify tax obligations. Minor gaps exist, such as no explicit transaction-history or budget-configuration tool, but the daily cap and receipt fields mitigate these and the main workflows are complete.
Maintenance
ActivityInactive
ResponsivenessWithin a week