What changed in Apiarium after developers started using it
A few weeks ago I wrote about why I built Apiarium after OpenRouter solved one problem for me and I still had four more. The comments on that post ended up shaping a good chunk of what I actually built next, so this is the "here's what changed" follow-up. The interesting part isn't really the features. It's where they came from. Almost everything below started with someone telling me something…
Apiarium has undergone significant changes since its inception, driven by the needs and feedback of its users. The most notable shift is the introduction of multiple API keys per account, allowing developers to track usage more accurately without having to share a single key for all applications. This feature includes the ability to name keys, revoke them individually, and tag each request with the key that generated it.
Credits are still shared across the account, but keys provide visibility into usage, which was previously limited to a single shared key.
In response to user inquiries, the dashboard has been revamped to offer a clearer view of credit consumption. Users can now filter usage by key, model, and endpoint, and export data to CSV for more detailed analysis. The old dashboard, which only showed a decreasing number, has been replaced with a more comprehensive overview that includes Overview, Usage, API Keys, and Billing sections.
The new system allows users to break down usage by model and endpoint, providing insights into which parts of their applications are consuming the most credits.
Another significant change is the pricing structure, which has been adjusted to reflect the actual cost of different models more accurately. This update aims to prevent situations where cheaper models were being billed at the same rate as more expensive ones. Additionally, there is now no fixed monthly minimum, allowing users to start with a pay-as-you-go option starting at €5 and only committing to a plan if they decide to scale up. This flexibility ensures that users can begin using Apiarium without any long-term commitments.
Looking ahead, Apiarium is open to suggestions for further improvements. The team encourages users to share their most pressing issues or features they wish existed, as continued development is driven by user feedback. This collaborative approach ensures that Apiarium evolves in a way that directly addresses the needs of its developer community.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
