A
licenseA
qualityA
maintenanceLive LLM API pricing: current token prices, model comparisons, cheapest-model lookups, and The LLM Price Index for 150+ models across 20+ providers, re-verified daily. No API key required.
5
1
MIT
Gonka Network Pricing
by bystray
Related Servers
Alternatives to Gonka Network Pricing
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceCompare AI inference pricing across 9 providers in real time. Routing recommendations, spend tracking, and budget alerts for AI agents.72 npmMIT
- FlicenseNot gradedqualityCmaintenanceCheapestInference — unlimited flat-rate API for frontier open-source LLMs-
- AlicenseAqualityDmaintenanceGlobal price benchmarking for AI inference across 2,600+ SKUs from 47 vendors. Query live pricing, market indexes, and model specs via 8 tools. Free tier available.878 npmMIT
- FlicenseAqualityNot gradedmaintenanceCompute price oracle for AI agents. Compare inference pricing across OpenAI, Anthropic, and DePIN providers like Hyperbolic. Get routing recommendations that save up to 80% on compute costs.5-
- AlicenseAqualityAmaintenanceDaily-verified LLM API pricing dataset (44+ models, CN & global) with a hosted MCP server for live price queries and token cost estimation.2CC BY-4.0
TDQS
B3.1/5.0
Scored across 17 tools
Disambiguation3/5
Tools are split into two distinct domains (pricing/comparison and documentation graph), causing ambiguity. Within the pricing domain, tools like calculate_savings, compare_providers, get_pricing, and suggest_model_for_task overlap significantly in purpose. The graph tools are more distinct but the overall set lacks clear separation of concerns.
Naming Consistency3/5
Most tools follow snake_case naming, but verb usage is inconsistent: imperatives (calculate, compare, get, suggest, register, read, list, query) mix with noun phrases (shortest_path, graph_stats, god_nodes). The naming is not chaotic but lacks a strong, uniform pattern.
Tool Count2/5
17 tools is excessive for a single server, especially when they cover two largely unrelated domains. The pricing-related tools (8) and documentation graph tools (9) each warrant their own server, leading to a heavy, bloated surface that confuses the server's core purpose.
Completeness3/5
Each sub-domain is reasonably complete: pricing covers comparison, savings, signup, and model suggestions; documentation graph covers querying, reading, and traversing. However, the server lacks integration between these domains, and the overall purpose is unclear, making it feel incomplete as a unified service.
Maintenance
ActivitySlowing
ResponsivenessNo issues