惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Microsoft Security Blog
Microsoft Security Blog
Jina AI
Jina AI
量子位
博客园 - 叶小钗
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
IT之家
IT之家
S
SegmentFault 最新的问题
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
小众软件
小众软件
Hugging Face - Blog
Hugging Face - Blog
雷峰网
雷峰网
博客园 - 聂微东
美团技术团队
Last Week in AI
Last Week in AI
罗磊的独立博客
酷 壳 – CoolShell
酷 壳 – CoolShell
博客园 - 三生石上(FineUI控件)
WordPress大学
WordPress大学
宝玉的分享
宝玉的分享
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园_首页
V
Visual Studio Blog
大猫的无限游戏
大猫的无限游戏
The Cloudflare Blog

Hacker News - Newest: "LLM"

GitHub - lechmazur/position_bias: A benchmark for testing whether LLM judges keep the same preference when two lightly edited versions of the same story are shown in opposite orders. Flex routing (EU and EFTA) Dark Factories: Retooling for LLM Velocity Ask HN: What would be the impact of a LLM output injection attack? GitHub - Oaklight/llm-rosetta: Production-ready LLM API translation layer for Python — bidirectional conversion between OpenAI, Anthropic & Google formats via hub-and-spoke IR. Optional API gateway. Streaming & non-streaming. Zero core deps. Contributions welcome! GitHub - browser-use/browser-harness: Self-healing browser harness that enables LLMs to complete any task. GitHub - moeen-mahmud/remen: Remen turns thoughts into something you can return to Analyzing 156 LLM Launch Posts on Hacker News ChatGPT vs Gemini vs Claude: The Best LLM Subscription You Should Buy GitHub - salaamalykum/quran-semantic-search: High-density RAG Semantic Search Engine & Quran Corpus (GEO/SEO Architecture) GitHub - NVIDIA/TensorRT-LLM: TensorRT LLM provides users with an easy-to-use Python API to define Large Language Models (LLMs) and supports state-of-the-art optimizations to perform inference efficiently on NVIDIA GPUs. TensorRT LLM also contains components to create Python and C++ runtimes that orchestrate the inference execution in a performant way. The State of LLM Bug Bounties in 2026 Operational Readiness Criteria for Tool-Using LLM Agents Meshcore: Architecture for a Decentralized P2P LLM Inference Network How an LLM becomes more coherent as we train it GitHub - seetrex-ai/laimark GitHub - Jossifresben/BibCrit: AI-assited biblical textual criticism GitHub - wastedcode/memex: File system based wiki, maintained by Claude 99helpers.com GitHub - cliver-project/AITrigram GitHub - unbody-io/adapt: A self-evolving memory layer for AI agents. GitHub - hb20007/awesome-gen-ai-fails: A list of incidents where reliance on generative AI and LLMs resulted in harm to companies, individuals, or society GitHub - nevenkordic/localmind: Run any local LLM with persistent memory and context. CLI agent over Ollama with SQLite-backed hybrid recall. No cloud. Ask HN: What are the machine requirements for a LLM like Llama-3.1-8B? Faster LLM Inference via Sequential Monte Carlo grpo explained: group relative policy optimization for llm finetuning - cgft Stop comparing price per million tokens: the hidden LLM API costs · TensorZero Andrej Karpathy's LLM Wiki Is a Bad Idea GitHub - GG-QandV/mnemostroma: Offline RAM-first cognitive leer/coprocessor for AI agents and robotics. Solves "Context Abandonment" with 20-80ms latency using a dual-thread biomimetic memory architecture (ONNX + SQLite WAL). mempalace/agent at agent · skorotkiewicz/mempalace
GitHub - arifozgun/OpenGem: Free, Open-Source AI API Gate...
ariozgun · 2026-05-28 · via Hacker News - Newest: "LLM"

What Is OpenGem?

OpenGem turns one or more Google accounts into a local, load-balanced Gemini gateway. It exposes the native Gemini API shape and also accepts OpenAI Chat Completions and Anthropic Messages requests, so most SDKs can point at your OpenGem server with only a base URL change.

It is designed for personal, educational and research usage. You run the gateway, connect your own Google accounts, create your own API keys, and monitor usage from the admin console.

Highlights

  • Next.js admin console with a rebuilt setup wizard, dashboard, logs, API keys, docs, settings and chat playground.
  • Native Gemini endpoint: POST /v1beta/models/{model}:generateContent.
  • OpenAI-compatible endpoint: POST /v1/chat/completions and GET /v1/models.
  • Anthropic-compatible endpoint: POST /v1/messages.
  • Multi-account rotation with cooldowns, retries, quota handling and automatic account reactivation.
  • Local SQLite backend using Node.js node:sqlite, plus optional Firebase Firestore.
  • Secure API key store with hashed keys, JWT admin sessions, rate limiting and Helmet headers.
  • Streaming support across Gemini, OpenAI-compatible and Anthropic-compatible surfaces.
  • Function calling, system prompts, tool payloads, image payloads and request logging.
  • No legacy public/ frontend: the UI is now built through Next static export and served from out/.

Quick Start

Requirements

  • Node.js 22.5.0 or newer
  • npm
  • At least one Google account
  • Optional: Firebase project, only if you choose Firestore instead of local SQLite

Install And Run

git clone https://github.com/arifozgun/OpenGem.git
cd OpenGem
npm install
npm run build
npm start

Open http://localhost:3050.

On a fresh install, OpenGem redirects to /setup where you choose the database backend and create the admin account. After setup, sign in, connect Google accounts, then create an API key from the dashboard.

For development:

npm run dev

The default server bind is 127.0.0.1:3050. Use HOST=0.0.0.0 only when you intentionally expose the process behind your own network controls.

API Usage

All endpoints accept the same OpenGem API keys.

Authorization: Bearer sk-your-api-key
x-goog-api-key: sk-your-api-key
x-api-key: sk-your-api-key
?key=sk-your-api-key

Optional account-affinity headers keep multi-turn agent tasks on the same upstream Google account while still failing over on quota or rate-limit errors:

x-opengem-session-id: stable-session-or-thread-id
x-opengem-task-id: stable-task-id
x-opengem-affinity: off

Gemini

curl -X POST "http://localhost:3050/v1beta/models/gemini-3.1-pro-preview:generateContent?key=sk-your-api-key" \
  -H "Content-Type: application/json" \
  -d '{"contents":[{"parts":[{"text":"Hello from OpenGem"}]}]}'
import { GoogleGenAI } from "@google/genai";

const ai = new GoogleGenAI({
  apiKey: "sk-your-api-key",
  baseUrl: "http://localhost:3050",
});

const response = await ai.models.generateContent({
  model: "gemini-3.1-pro-preview",
  contents: "Explain OpenGem in one paragraph.",
});

console.log(response.text);

OpenAI Compatible

import OpenAI from "openai";

const client = new OpenAI({
  apiKey: "sk-your-api-key",
  baseURL: "http://localhost:3050/v1",
});

const response = await client.chat.completions.create({
  model: "gpt-4o",
  messages: [{ role: "user", content: "Hello!" }],
});

console.log(response.choices[0].message.content);

Anthropic Compatible

import Anthropic from "@anthropic-ai/sdk";

const client = new Anthropic({
  apiKey: "sk-your-api-key",
  baseURL: "http://localhost:3050",
});

const response = await client.messages.create({
  model: "claude-3-5-sonnet-latest",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Write a short haiku." }],
});

console.log(response.content);

Admin Console

The dashboard includes:

  • Overview: request totals, success rate, active accounts and token usage.
  • Accounts: connect Google accounts, reactivate cooled-down accounts and remove accounts.
  • API Keys: create, copy-once and revoke gateway keys.
  • Request Logs: inspect prompt, response, model, fallback and token metadata.
  • Documentation: endpoint quick reference and an API playground.
  • Chat: authenticated Gemini chat with streamed responses and thinking sections.
  • Settings: database backend switching, credential rotation and privacy mode.

Configuration

OpenGem stores runtime configuration in config.json after setup. Local data lives in data/db.sqlite when SQLite is selected. Both are ignored by git.

Useful environment variables:

PORT=3050
HOST=127.0.0.1
CORS_ORIGIN=https://your-domain.example

When using Firebase, paste the Web app config in the setup wizard or in Settings when switching backends.

Build Output

The backend is still Express + TypeScript, while the UI is a static Next.js export.

npm run build:server  # compiles src/ to dist/
npm run build:web     # exports app/ to out/
npm run build         # runs both

npm start serves API routes and the built Next UI from the same port.

Project Structure

OpenGem/
├── app/                    # Next.js admin console and setup wizard
│   ├── assets/             # UI images/icons imported by Next
│   ├── setup/              # Setup wizard route
│   └── opengem-console.jsx # Dashboard application
├── components/ui/          # shadcn-style UI primitives
├── lib/                    # Frontend utilities
├── src/
│   ├── controllers/        # Gemini, OpenAI and Anthropic handlers
│   ├── middleware/         # Admin auth middleware
│   └── services/           # Config, database, OAuth, streaming, retry logic
├── dist/                   # Compiled backend output
├── out/                    # Next static export output
├── data/                   # Local SQLite data, ignored by git
├── config.json             # Runtime config, ignored by git
├── app.js                  # Production entry for Passenger/cPanel
└── package.json

Security Notes

  • Keep config.json, .env and data/ private.
  • Place production deployments behind nginx, Cloudflare or another trusted reverse proxy.
  • Keep the Node process bound to loopback unless you know why it must be exposed.
  • Regenerate API keys after switching database backends; raw key material is intentionally not recoverable.

Star History

Star History Chart

License

MIT. See LICENSE.