HuggingFace isn't just another LLM router — it's a platform helmdeck barely uses
The 2026-06-10 empirical work surfaced something I've been avoiding: OpenRouter's shared :free pool isn't a reliable foundation for sustained Tier C agentic work. Three of five Phase 1 models hit upstream rate limits today — Google AI Studio 429'd google/gemma-4-26b-a4b-it:free; "Venice"-attributed 429s caught meta-llama/llama-3.3-70b-instruct:free and qwen/qwen3-coder:free within minutes of each other.
PR #489 shipped the obvious next move: alternative routing via HuggingFace Inference Providers. Multi-provider YAML schema, first HF template profile, routing setup walkthrough, CI validation gate. External contributors with HF infrastructure can now ship per-model profiles bypassing the OpenRouter shared pool. That's good.
But it also reframes a much bigger question: why is helmdeck treating HuggingFace as just another router?