Recost shows you exactly what code is burning money before your API bill explodes. It maps cost to endpoints, flags waste like duplicate calls and bad loops, and simulates scale impact. With AST analysis and runtime tracking, you don’t just track spend, you control it before it gets out of hand.
Top comment
Comment highlights
This is a great idea especially for startups! I turned my attention recently to using codex and the aws cli to be able to figure out how much new infra is going to cost. Can Recost tell you how much staged changes are roughy going to cost before deploying them?
I like being able to centralize all the costs in an API, and not having to go to multiple places to monitor.
Hey that's cool. I'm on a tight budget and use API's all the time, but you can't always set a maximum usage thus I have to monitor manually all the time. This can bring it all into one place right.
“At a hackathon, a team shipped a feature making ~200 concurrent API requests. It worked perfectly… until their API key got revoked. No visibility. No warning. Just everything shutting off.”
How do you prevent this? I.e do you see response codes and that I am getting 429 or whatever and warn, or is it strictly the telemetry of the number of concurrent events?
Finally, a tool that stops a quick bug fix from accidentally costing more than my monthly rent!
Hey Product Hunt! 👋
We’re the team behind Recost.
We built this after watching teams unknowingly blow through API budgets.
At a hackathon, a team shipped a feature making ~200 concurrent API requests. It worked perfectly… until their API key got revoked. No visibility. No warning. Just everything shutting off.
Recost gives you a cost intelligence layer for your APIs, so you can see and control cost before it becomes a problem.
What Recost does
🔍 Static analysis (VS Code extension)
Detects API calls across your codebase
Maps endpoints to files, functions, and features
Surfaces cost risks before runtime
💸 Cost attribution
Cost per endpoint, provider, and feature
See what’s actually driving spend
⚡ Runtime tracking (Python SDK)
Live request volume, latency, and cost
Real-time sync to dashboard
🚨 Waste detection
Duplicate calls, loops, polling issues
Suggestions to reduce cost
📈 Forecasting
Simulate scale and estimate feature cost
Catch worst-case scenarios early
🌐 Dashboard
Unified view of API usage and cost
Trends and drilldowns
What’s coming next
MCP integration for API graph + cost intelligence
Built-in AI for better detection and estimation
Team pricing plans
Why we built this
Every part of engineering has visibility.
Logs. Metrics. Errors.
API cost doesn’t.
Recost makes cost visible at the same level as your code.
Free plan
6 projects
2 API keys
50 scans/day
100 endpoints/project
Live monitoring + analytics
We’re building fast and want real feedback.
We’re also building this in the open, feel free to check it out or contribute on GitHub(https://github.com/recost-dev).
Where do API costs feel the most unpredictable right now?