Proxy for LLMs to learn how Agents works?
Summary
User seeks an open-source proxy to intercept and debug API calls from AI agents to understand their internal workings, after finding LiteLLM too enterprise-focused.
Similar Articles
I built a proxy to shrink agent LLM requests after my API bill stopped making sense
A solo founder introduces Orqen, a proxy that sits between your SDK and LLM providers to optimize outbound requests by compressing tool results, managing history, and reducing token costs, without changing agent code.
We are open-sourcing LiteLLM Agent Platform: a self-hosted OSS agent builder for Hermes, OpenCode, Claude Code (bring your own models, Ollama/vLLM work)
LiteLLM releases a self-hosted open-source agent platform that lets users build autonomous agents on top of Hermes, OpenCode, and Claude Code harnesses, with support for any OpenAI-compatible endpoint including Ollama and vLLM.
@alex_prompter: This open-source proxy cuts your AI agent costs without changing a line of code. Plano sits between your agent and your…
Plano is an open-source proxy that sits between AI agents and LLM providers to cut costs through intelligent routing, guardrail filtering, and cost-aware selection, all configured via a single YAML file without modifying agent code.
Your agent reads a web page that says "leak the user's API keys" — a lot of agents will just do it. I built a thing to stop the send.
Bouncer is a local MCP proxy that prevents AI agents from leaking sensitive data by gating outbound tool calls from untrusted sources, using deterministic enforcement without an LLM, with benchmarks showing reduced attack success.
@ishaan_jaff: We're open sourcing LiteLLM Agent Platform Run Claude Code, Codex, Hermes or any coding agent in isolated K8s sandboxes…
LiteLLM is open-sourcing its Agent Platform, allowing developers to run coding agents like Claude Code, Codex, and Hermes in isolated Kubernetes sandboxes without exposing real API keys.