mirror of
https://github.com/AJaySi/ALwrity.git
synced 2026-04-25 17:05:56 +03:00
[PR #236] [MERGED] Implement usage-based subscription and monitoring #271
Labels
No labels
AI Content Agents
AI Content Strategy
AI Content planning
AI Marketing Tools
AI SEO
AI personalization
AI writer
ALwrity Copi-lot
Alwrity web search
Anthropic
DeepSeek
Gemini AI
Integration
LLM
OnBoarding
OnBoarding
RAG knowledgebase Memory
bug
documentation
enhancement
good first issue
help wanted
invalid
openai
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ALwrity#271
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/AJaySi/ALwrity/pull/236
Author: @AJaySi
Created: 9/4/2025
Status: ✅ Merged
Merged: 9/12/2025
Merged by: @AJaySi
Base:
main← Head:cursor/implement-usage-based-subscription-and-monitoring-0179📝 Commits (7)
e0a6150Add comprehensive usage-based subscription system with API trackingb156298Merge branch 'main' into cursor/implement-usage-based-subscription-and-monitoring-01791b65a94ALwrity LinkedIn Writer: Billing Dashboard: Compact View, Billing Overview, System Health Indicator, Cost Breakdown, Usage Trends, Usage Alerts, Comprehensive API Breakdownc0a3662Added blog writer implementation - WIP2ae0c4aAI Blog Writer - Implement modular architecture with research, outline, and core services1d04d64Merge main into cursor/implement-usage-based-subscription-and-monitoring-0179c63148eAdd comprehensive Stage 3 Content Generation implementation plan📊 Changes
140 files changed (+20468 additions, -191 deletions)
View changed files
➕
backend/BILLING_SYSTEM_INTEGRATION.md(+256 -0)➕
backend/SUBSCRIPTION_SYSTEM_README.md(+372 -0)➕
backend/api/blog_writer/__init__.py(+2 -0)➕
backend/api/blog_writer/router.py(+359 -0)➕
backend/api/subscription_api.py(+414 -0)📝
backend/app.py(+13 -0)📝
backend/middleware/monitoring_middleware.py(+249 -9)➖
backend/models/__pycache__/linkedin_models.cpython-313.pyc(+0 -0)➕
backend/models/blog_models.py(+149 -0)➕
backend/models/subscription_models.py(+316 -0)➕
backend/research_analysis_20250911_173832.json(+84 -0)➕
backend/research_analysis_20250911_174238.json(+206 -0)➕
backend/scripts/create_billing_tables.py(+217 -0)➕
backend/scripts/create_subscription_tables.py(+206 -0)➕
backend/services/blog_writer/README.md(+151 -0)➕
backend/services/blog_writer/blog_service.py(+11 -0)➕
backend/services/blog_writer/core/__init__.py(+11 -0)➕
backend/services/blog_writer/core/blog_writer_service.py(+233 -0)➕
backend/services/blog_writer/outline/__init__.py(+21 -0)➕
backend/services/blog_writer/outline/outline_generator.py(+351 -0)...and 80 more files
📄 Description
Implement a usage-based subscription system with API call monitoring, cost tracking, and usage limits to enable billing and control consumption.
This PR introduces a foundational usage-based subscription model, integrating real-time API call monitoring, cost calculation, and limit enforcement directly into the application's middleware. This enables the platform to accurately track user consumption of external APIs (like Gemini, OpenAI, etc.), apply subscription-based caps, and provide detailed billing statistics for the new business model.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.