9routerSelf-hosted gateway pointing any AI coding CLI (Claude Code, Codex, Cursor, Cline) at 40+ providers, with subscription→cheap→free auto-fallback and tool_result compression for 20-40% token savings.
Why switchBoth are self-hosted OpenAI-compatible gateways that multiplex providers with automatic fallback for coding CLIs. 9router optimizes paid usage (subscription→cheap→free routing, token compression); FreeLLMAPI exists purely to stack and stay under 18 providers' free-tier caps.
Full comparison → free-claude-codeProvider-backed proxy that runs Claude Code, Codex or Pi on 25 cloud and local providers — fcc-* launchers, local Admin UI with validation, per-tier model routing, IDE/Discord/Telegram hookups.
Why switchSame slot — run coding CLIs on non-Anthropic providers for free — different philosophy: FCC is launcher + Admin UI where you pick and validate one provider (with per-tier overrides); FreeLLMAPI stacks 18 providers' free tiers behind a router with automatic failover and quota tracking.
Full comparison → litellmOpen-source AI gateway: call 100+ LLM providers in OpenAI format via a Python SDK or self-hosted proxy — with cost tracking, virtual keys, guardrails, load balancing and logging.
Why switchBoth expose many providers behind one OpenAI-compatible /v1 endpoint; freellmapi stacks free tiers, LiteLLM targets production apps and teams.
Full comparison → LynkrSelf-hosted LLM gateway wrapping Claude Code, Cursor or Codex with zero code changes — strips unused tools, compresses JSON tool results ~88%, semantic-caches, tier-routes easy work to local models.
Why switchSame slot — a local proxy in front of Claude Code/Codex to cut LLM spend. lynkr's lever is compression, semantic caching and tier-routing of paid traffic; FreeLLMAPI's is routing everything to free-tier quota across providers.
Full comparison →