This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
AI agents loop, retry and resend growing context, and the bill shows up weeks later. Silvanexum meters every LLM call across OpenAI, Anthropic and Gemini (streaming included), ties cost to the customer, agent and trace behind it, and blocks calls before they break a budget. Plug in by swapping one base URL, or use SDK-only mode so prompts and keys never leave your servers. Python and TypeScript SDKs, an MCP server and an NVIDIA NeMo Relay plugin.
Hey Product Hunt 👋 I'm Rana, the solo engineer behind Silvanexum.
I built it after watching AI agents do something normal APIs never do: decide on their own how much to spend. A retry loop, a context that keeps growing, a tool that returns junk, and a task that should cost cents costs dollars. Provider dashboards only tell you per API key, after the fact.
Silvanexum sits in front of (or beside) your LLM calls and:
• meters every call across OpenAI, Anthropic and Gemini, streaming included
• attributes cost to the customer, agent and trace that caused it
• blocks a call before it runs when a budget is spent
Two ways in: swap one base URL (gateway), or SDK-only mode where your prompts and provider keys never leave your servers.
What I'd love feedback on:
How do you track AI cost per customer today, if at all?
Would you rather cap spend per customer, per agent, or both?
Gateway or SDK-only: which would you actually let into production?
No comment highlights available yet. Please check back later!
About Silvanexum on Product Hunt
“Hard budgets that stop runaway AI agent spend”
Silvanexum was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #236 on the daily leaderboard. AI agents loop, retry and resend growing context, and the bill shows up weeks later. Silvanexum meters every LLM call across OpenAI, Anthropic and Gemini (streaming included), ties cost to the customer, agent and trace behind it, and blocks calls before they break a budget. Plug in by swapping one base URL, or use SDK-only mode so prompts and keys never leave your servers. Python and TypeScript SDKs, an MCP server and an NVIDIA NeMo Relay plugin.
Silvanexum was featured in Developer Tools (523.2k followers), Artificial Intelligence (483.9k followers) and SDK (881 followers) on Product Hunt. Together, these topics include over 234k products, making this a competitive space to launch in.
Who hunted Silvanexum?
Silvanexum was hunted by Rana Reebaal. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Silvanexum stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Hey Product Hunt 👋 I'm Rana, the solo engineer behind Silvanexum.
I built it after watching AI agents do something normal APIs never do: decide on their own how much to spend. A retry loop, a context that keeps growing, a tool that returns junk, and a task that should cost cents costs dollars. Provider dashboards only tell you per API key, after the fact.
Silvanexum sits in front of (or beside) your LLM calls and:
• meters every call across OpenAI, Anthropic and Gemini, streaming included
• attributes cost to the customer, agent and trace that caused it
• blocks a call before it runs when a budget is spent
Two ways in: swap one base URL (gateway), or SDK-only mode where your prompts and provider keys never leave your servers.
What I'd love feedback on:
How do you track AI cost per customer today, if at all?
Would you rather cap spend per customer, per agent, or both?
Gateway or SDK-only: which would you actually let into production?
I'll be here all day answering questions.