pull down to refresh

Interesting, but the readme is shy on details. Does it charge per call or per time? Both REST and WS? Suggested use cases?
Thanks for pointing that out! I'll add more details to the README.
It charges per unique call. You'll need to implement a database to invalidate macaroons after each use or based on time. Currently, it supports REST APIs only; WebSocket (WS) support is not yet implemented.
Real-world use cases can be: AI & LLM APIs – Charge per request for AI model inferences, ensuring pay-per-use monetization. Weather & Financial APIs – Monetize access to premium weather forecasts, stock prices, or crypto market data. Self-hosted SaaS Tools – Implement per-request billing for services like file conversion, image processing, or data enrichment. Decentralized VPNs & Proxies – Charge users for bandwidth consumption on privacy-preserving networks.
reply