VCU Consumption Limits for API Keys

Introduce configurable limits on VCU consumption per API key to enable controlled usage. This is essential for VCU rentals, resale, subscription models, and quota management while preventing overuse and abuse.

Proposed Features:

Users should be able to set custom VCU limits per API key, with the following options:

1. Total Limit (Refillable/Renewable)

   • A fixed maximum VCU allocation per key, manually or automatically refillable.

   • Use Case: Renting out VCU with refill options.

2. Daily Limit

   • A hard cap on VCU usage per day to prevent overconsumption.

   • Use Case: Subscription plans where users get X VCU per day.

3. Time-Based Allocation (Rolling or Fixed Window)

   • A set VCU limit over a defined period (weekly, monthly, etc.).

   • Fixed Window: Resets at the start of each cycle (e.g., “10,000 VCU/month”).

   • Rolling Window: Applies a limit over any continuous period (e.g., “10,000 VCU over 30 days”).

   • Use Case: Monthly subscription tiers with more flexible usage patterns.

4. One-Time Use & Expiration

   • A single-use VCU allocation that expires when depleted.

   • Use Case: Selling one-time VCU packages.

5. Per-Request Limit

   • A cap on the VCU usage per individual API call to prevent single-call overuse.

   • Use Case: Protects against excessive batch-processing requests.

6. Rate Limiting (VCU per Time Interval)

   • Restrict usage to a maximum VCU per minute/hour to prevent sudden spikes.

   • Use Case: Prevents a user from burning an entire daily quota in minutes.

7. Grace Period / Temporary Overages

   • An optional soft limit where users can slightly exceed their quota before getting fully blocked.

   • Use Case: Prevents disruptions for legit users who slightly overconsume.

Why This Matters:

• Enables VCU rentals and resale with precise quota control.

• Prevents accidental or malicious overuse.

• Supports subscription-style access models.

• Provides budget control and cost predictability.

• Ensures a clean and scalable way to manage VCU distribution.

Implementation Considerations:

• Limits should be configurable via the dashboard and API.

• Admins should have usage tracking & alerts when quotas are close to being hit.

This feature would enhance VCU-based services and expand monetization options, benefiting both Venice and its users.