Account / Usage, history & metrics

Usage, history & metrics

The dashboard gives you three views into your generation activity. All of them concern metadata: the rendered PDF itself is never stored.

Usage

The usage view shows your current month's generations against your plan's quota: used, limit, and remaining, plus a few trailing months for context. The period is a calendar month in UTC (shown as 2026-06).

This counter is the single source of truth: it is the same number that enforces limit_exceeded and the same number you see, written in the same transaction as each successful render, so the display can never drift from reality. Failed calls do not increment it.

History

Generation history lists every call with:

• Status (success or error) and, on failures, an actionable message.
• The template and the version number that served the request.
• The render duration in milliseconds.
• When it happened.

You can filter by status and by template to find what you are after, and open any entry for its detail.

Request-payload storage (opt-in)

By default, the data you send is not retained, only the fact that a generation happened. You can opt an individual template into storing its request payloads, which is useful for debugging a tricky template. When enabled, the stored payload appears on the generation's detail view (and only there, never in another user's data). Leave it off for anything sensitive.

Metrics

The metrics view aggregates a recent window:

• Totals — total generations, successes, errors, and the error rate.
• Top templates — your most-used templates by volume.
• Recurring errors — failures grouped by pattern rather than by exact message, so a systemic issue (for example a template that frequently misses a required variable) surfaces as one bucket instead of being scattered across many near-identical messages.

Use this to spot a template that needs attention before it affects more documents.

Retention

Generation metadata is kept for a window that depends on your plan, then removed by a daily purge:

When a record is purged, any opted-in request payload goes with it. Again, the PDF was never stored in the first place, so retention is purely about how long the metadata (and any payload you chose to keep) remains visible. Longer retention is one reason to move up a plan.