The full gallery
Tech stack
30 projects
Backend platform providing auth, storage, database, and LLM APIs (Claude, OpenAI, Gemini) via a single JavaScript library.
ent101 · HN
The Safe, Production-Ready Backend for AI-Generated Apps
Monitor Anthropic and OpenAI API calls with per-request token usage, costs, and session trees.
u/Prestige_pvp · Reddit
Simple AI Token Profiler / Debugger We made a simple profiler to help optimize AI token spend. Generally speaking anytime you want to optimize your app, whether it's for memory or otherwise you typically start with a profiler. There are a ton of MiTM Gateways but there aren't many true profilers, so I thought I'd make one. https://profiler.getrekon.com/ Let me know what you think :) submitted by /u/Prestige_pvp to r/SideProject [link] [comments]
Pay-per-use API marketplace offering 47 endpoints for OCR, translation, image generation, and LLM chat.
13639366668 · HN
Pay-per-call MCP server with 47 AI endpoints, micropayments via x402
Connect 1000+ SaaS providers to AI agents via SDK, CLI, MCP, HTTP, or OpenAPI.
oomol-lab · GitHub
open-connector Open-source auth gateway connecting 1000+ SaaS providers to AI agents through SDK, CLI, MCP, HTTP, and OpenAPI.
Unified API layer to integrate your website with multiple AI systems.
@rofarkas · X
Secure GitHub pull requests with hardware authentication and OTP verification.
jallmann · HN
> want without a PR process that requires hardware authentication or proof of presence Just curious, what do you use for this? I built OTP Guard [1] a few years ago for exactly this problem, although I haven't seen any alternatives in the space. Does GitHub have something built-in now? The original framing was more "local malware compromising your GitHub account" ... it never occurred to me that the malware could be a LLM. I really should update the page. [1] https://otpguard.com
Add authentication to your app with passkeys, SSO, and MFA via MonoCloud's developer platform.
roguetink · Product Hunt
MonoCloud for Startups One identity layer for your customers, APIs, and agents
One unified API to access 200+ AI models including Claude, GPT, and Gemini with auto-failover.
@MixRoute_ai · X
Get a free API key with email to access 500+ Hugging Face models.
@pengsonal · X
500+ Hugging Face models through a single free API no credit card just an email signup 😳 launched on July 3 as a unified gateway for Hugging Face models one API key one endpoint 500+ models what you get for $0: • 500+ open-source models through an OpenAI-compatible API • no separate API keys for different providers • works with Cursor, Claude Code, Hermes, OpenCode, and anything that supports a custom base URL • email signup only setup takes about 2 minutes: 1. Go to 2. Sign up with your email 3. Generate an API key 4. Set your base URL to 5. Choose any model from the catalog and start building a few things worth knowing: • is a third-party gateway, not an official Hugging Face product • the free tier is rate-limited, but the exact limits haven't been published yet • i wouldn't build production apps that depend entirely on a free aggregator what i like is the simplicity instead
Mask personal data and reduce AI token costs by processing data locally before sending to Claude, ChatGPT, Gemini, or other APIs.
@AI_303030 · X
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 工作台。欢迎试用，也欢迎吐槽你最烦的配置问题。
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
