Expose & document daily Actor publication quota (used / limit / reset time) in API and Console

[myagizmaktav]

Problem

When publishing Actors via the API (PUT /v2/acts/{id} with { "isPublic": true }), the platform enforces a daily limit of 5 publications per rolling 24h window. There is currently no way to see the quota state before hitting it.

The only signal is the error returned after a failed publish attempt:

daily-publication-limit-exceeded — You've reached the daily limit of 5 Actor publications. Try again in 24 hours.

This error does not tell you how many publications remain in the current window, nor when the rolling 24h window resets. This makes it impossible to plan a multi-Actor rollout or automate publishing — the quota can only be discovered by failing.

Request

Surface the publication quota state (and document it):

1. API — a field or endpoint returning { used, limit, resetsAt } for the publication quota (e.g. on the user/account endpoint, or a dedicated GET /v2/acts/publication-quota). At minimum, include resetsAt in the existing daily-publication-limit-exceeded error response, and document the limit + reset semantics in the API reference / publishing docs.
2. Apify Console (dashboard) — show remaining daily publications and the reset timestamp on the Actor publish UI.
3. MCP server — expose the same via a tool/resource (tracked separately in Expose daily Actor publication quota (used / limit / reset time) via API, MCP, and Console apify-mcp-server#1113).

Why

This matters most for scheduled / automated publishing flows, where the current behavior is a silent hard blocker with no visibility into timing. Even just documenting the reset semantics and returning resetsAt in the error response would be a meaningful improvement.

---

Cross-filed from apify/apify-mcp-server#1113 (MCP surface).