Documentation
Monitor Usage
Track request volume, quota consumption, and reset timing for Milkey MCP traffic.
Milkey records authenticated MCP requests against your account so you can see usage in the dashboard and predict when a plan upgrade, key rotation, or workload split will be needed.
What counts
- MCP requests made with a valid Milkey API key count toward your monthly request usage.
- The count is tied to the authenticated account behind that key.
- Usage is tracked against the current billing period, not as a rolling 30-day quota.
Dashboard signals
The dashboard is the main place to monitor Milkey usage. The current product surface is designed to answer three operational questions:
- How many requests have I used this period?
- What does daily request volume look like over the last 30 days?
- Which skills are being used most often?
Monthly quotas
Free
500 requests / month
Best for evaluation and light personal usage.
Pro
5,000 requests / month
Good for a single daily coding workflow.
Builder
25,000 requests / month
Good for heavier individual or small-team usage.
Scale
100,000 requests / month
Built for high-volume agent loops.
Reset timing
Milkey usage normally resets at the start of the next calendar month in UTC.
Why UTC matters
If your team is spread across time zones, the request reset will not align with local midnight everywhere. During billing migrations or cutovers, Milkey may also start a new billing period from a later reset timestamp, and the dashboard/API period start reflects that effective boundary. Treat the returned period start as the source of truth for quota planning and alerting.