Node.js Engineer – Secure AI API Proxy

PLEASE READ COMPLETELY
PLEASE READ COMPLETELY
PLEASE READ COMPLETELY

Node.js Engineer – Secure AI API Proxy (Bring-Your-Own-Key, Usage Limits, bolt.diy Integration)

I am looking for a backend engineer to build a secure AI API proxy that sits between an AI app builder (bolt.diy) and AI model providers (OpenAI and Anthropic).

The goal is to:
• Use my own API keys
• Prevent keys from ever being exposed to users or clients
• Enforce per-user usage limits
• Track usage and estimated costs
• Safely allow multiple internal users (helpers) to use the system

This is an internal tool, not a SaaS product and not a frontend-heavy project.

⸻

What the System Must Do
• Accept AI requests from bolt.diy
• Authenticate the requesting user
• Enforce:
• Daily and/or monthly token limits
• Rate limits
• Forward requests to OpenAI or Anthropic
• Log:
• User ID
• Model used
• Tokens consumed
• Estimated cost
• Return only the AI response (no keys, no metadata leakage)

bolt.diy must communicate only with this proxy, never directly with OpenAI or Anthropic.

⸻

Required Features
• Node.js backend (Express or Fastify)
• Bring-your-own-key architecture (keys stored only as environment variables)
• Per-user quotas
• Rate limiting
• Usage logging
• Provider-agnostic design (OpenAI first, Anthropic supported)
• Clear setup and usage documentation

⸻
If you have read and understand project and can do the job use the phrase “I know bolt” and bid YOUR price don’t ask me budget must understand bolt.diy

Explicit Non-Requirements
• No frontend UI required
• No payment processing
• No public user signup
• No AI training
• No proprietary or locked frameworks

⸻

Deliverables
1. Working API proxy server
2. Environment-based API key configuration
3. User quota system (config or database-based)
4. Usage logging (database or structured logs)
5. Instructions to connect bolt.diy to the proxy
6. Clean README with setup steps

No API keys should ever be committed to the repository.

⸻

Preferred Tech Stack (Flexible)
• Node.js
• Express or Fastify
• Redis (rate limits and counters)
• SQLite or Postgres (usage logs)

Alternative stacks are acceptable if clearly justified.