
Releases · KBlip - The Signal Feed for the AI/LLM World
Track AI and LLM news and model launches from 100+ sources.
jonam21 · HN
KBlip – turns AI/LLM news across 100 sources into daily digest threads
The full gallery
Tech stack
20 projects

Track AI and LLM news and model launches from 100+ sources.
jonam21 · HN
KBlip – turns AI/LLM news across 100 sources into daily digest threads

Route AI API calls to different models based on budget, stability, or performance needs.
@RunPei83973 · X
Claude Code users: Did you know API routing can significantly reduce AI costs? We built VIAPI to test different AI routes: Budget → lower cost Stable → production Pro → high availability

OpenAI-compatible API for running open-weight LLMs and video models.
bingus-bongo · HN
Use GLM-5.3 in Cursor today via tokengo API

Upload your data to fine-tune custom language models with cryptographic deletion proofs.
@MBrew26730 · X
Dataset cleaning + fine tuning + continual learning at

Unified API gateway for auditing token consumption and analyzing AI API costs across multiple providers.
@amiuchat · X
我做了一个桌面工具:Token Switch。 给 Codex / Claude Code / OpenCode 重度用户统一管理 Provider、模型、Token、Base URL、连通测试和消耗统计。 多个 Agent,一个 Token 工作台。欢迎试用,也欢迎吐槽你最烦的配置问题。

AI gateway service providing OpenAI and Anthropic-compatible endpoints for developers
@jembatanaicom · X
Building JembatanAI — Claude, GPT, DeepSeek, GLM & MiniMax behind one developer-focused gateway. Unlimited from ~$2 and credit from ~$0.23. Crypto accepted.

Route requests to Claude, GPT, or GLM through one API key with free daily credits.
@Awais_209 · X
Claude Opus 4.8, GPT-5.5 & GLM-5.2 for free. Get $25/day in credits. No trial or waitlist. One API key works with Claude Code, Cline, Cursor, Roo & OpenAI-compatible tools. Try it: #FreeTier #ClaudeAPI #CodingTools @AgentRouter_0

Use one OpenAI-compatible key to access DeepSeek, Qwen, Claude, GPT, Gemini and more with failover.
u/stelkey_com · Reddit
I built an OpenAI-compatible API gateway because switching models kept breaking my integrations I’m the maker of Stelkey. I kept hitting the same annoying problem: a tool works with one provider, then a model change means touching endpoints, auth, request formats, usage tracking, and the rest of the plumbing. So I built Stelkey as one OpenAI-compatible surface for the models and clients I already use. The goal is deliberately boring: point an existing OpenAI-compatible client or SDK at on