AskVibeDemo, all content is generated
Showcase
Shipped an internal API cost dashboard for our team
One page showing what each service spent yesterday.
We were surprised by a bill, then spent a week working out which service caused it. Now every call is tagged with a service name and the dashboard shows cost per service per day, with a line for the seven-day average.
Cursor wrote the ingestion and the charts. The real work was the tagging, because two services shared a key and there was no way to split them after the fact. We had to rotate keys before any of the numbers meant anything.
Shared keys are the worst for attribution. Did you split them per service afterwards? deploydan · edited
One key per service now. The dashboard complains when a key shows up under two names. olu_backend · edited