Skip to main content
Glama

Related Servers

Alternatives to promptspend

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Which AI model to use and what it costs: LiteLLM's price catalogue with every price change since 2023 and Arena ratings by task. Tools to find and compare models, estimate a job's cost and time, show price history and pick local or cloud; no API keys needed.
      11
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A local-first, multi-provider cost meter for LLM usage, exposed as MCP tools. Captures every call into a local SQLite ledger and lets any coding agent query spend, compare providers, and get recommendations — no cloud, no account. First-class support for Chinese providers (Qwen, DeepSeek) alongside Anthropic and OpenAI.
      7
      53 PyPI
      6
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Live 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.
      4
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to rank model variants and hunt down API offers for a specific task, estimate real billed cost, audit n8n/Make automations for overpay, missing fallbacks and deprecated models, and plan or run evaluation and canary suites on the user's own examples. It also supports price comparison, custom reseller channels with measured per-call cost, and non-LLM capabilities such as web search and speech-to-text.
      AGPL 3.0

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool occupies a clearly distinct step: get_price is a single-model lookup, estimate_cost computes workload cost across models, and find_cheaper ranks alternatives by capability-adjusted cost. Descriptions even cross-reference each other (get_price points to estimate_cost), eliminating misselection risk.

    Naming Consistency5/5

    All three names follow a consistent snake_case verb_noun pattern (get_price, estimate_cost, find_cheaper) with verbs matching the action performed.

    Tool Count4/5

    Three tools is on the thin side but each earns its place in a narrow pricing/costing domain. A discovery or comparison helper might round it out, but nothing feels redundant.

    Completeness4/5

    The core lifecycle—look up a price, cost a workload, find cheaper equivalents—is covered, including edge cases like disputed sources, unknown models, caching and long-context tiers. Minor gap: no way to list or browse available models, so agents rely on fuzzy matching in get_price.

    Maintenance

    ActivityActive
    ResponsivenessResponsive