Skip to content

Conversation

@jfrench9
Copy link
Member

@jfrench9 jfrench9 commented Nov 9, 2025

Summary

This PR introduces a complete organization management system with comprehensive billing capabilities, transforming the client from user-centric to organization-centric operations. The changes include new API endpoints for organization CRUD operations, member management, usage tracking, and enhanced billing functionality.

Key Accomplishments

🏢 Organization Management

  • New Organization APIs: Complete CRUD operations for organizations including create, read, update, and list operations
  • Organization Member Management: Full member lifecycle with invite, list, remove, and role update capabilities
  • Organization Graph Management: Dedicated endpoints for managing graphs within organizational contexts
  • User-Organization Relationships: New endpoints to list organizations associated with users

💳 Enhanced Billing System

  • Organization-Scoped Billing: Migrated all billing operations to organization-level scope
  • Comprehensive Billing APIs: Added organization billing customer management, subscription handling, and invoice operations
  • Payment Management: Enhanced checkout session creation and payment method updates
  • Usage Analytics: New organization usage tracking and limits management

📊 Usage & Analytics

  • Organization Usage Tracking: Detailed usage analytics with daily trends and graph-specific metrics
  • Limits Management: Organization-level resource limits and current usage monitoring
  • Service Offerings: Enhanced service offerings with improved response models

🔧 Data Models & Types

  • New Model Architecture: 20+ new data models supporting organization operations
  • Enhanced Response Models: Comprehensive response structures for all new endpoints
  • Role-Based Access: New organization role and type definitions
  • Billing Models: Updated billing and checkout response models

Breaking Changes

⚠️ API Structure Changes: Several billing endpoints have been renamed with "org_" prefixes to reflect organization-scoped operations:

  • cancel_subscriptioncancel_org_subscription
  • get_subscriptionget_org_subscription
  • list_invoiceslist_org_invoices
  • get_billing_customer → moved to org context
  • User-specific limits endpoints migrated to organization context

⚠️ Model Restructuring: Some existing models have been refactored or relocated to support the new organization-centric architecture.

Testing Notes

  • All new endpoints should be tested with proper organization context
  • Verify role-based access controls for organization member operations
  • Test billing operations within organization scope
  • Validate usage analytics and limits functionality
  • Confirm backward compatibility for existing non-organization endpoints

Infrastructure Considerations

  • Database schema may need updates to support organization relationships
  • Authentication middleware should handle organization-scoped permissions
  • Rate limiting may need adjustment for organization-level operations
  • Consider caching strategies for frequently accessed organization data
  • Monitor API performance with the increased number of available endpoints

Files Changed: 57 files across API endpoints, data models, and core infrastructure
Version: Released as v0.2.11


🤖 Generated with Claude Code

Branch Info:

  • Source: feature/billing-api
  • Target: main
  • Type: feature

Co-Authored-By: Claude noreply@anthropic.com

This commit updates the documentation for user registration and billing-related API endpoints. Key changes include:
- Expanded descriptions for user registration, emphasizing the automatic creation of personal organizations and security controls.
- Clarified the billing process in the create checkout session endpoint, specifying that it is intended for organization owners and detailing the flow of creating a graph with payment methods.
- Removed deprecated billing endpoints and models to streamline the API.

These enhancements aim to improve clarity and usability for developers interacting with the API.
@jfrench9 jfrench9 merged commit babaec6 into main Nov 9, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants