Billing and quota

Quota behavior matches the running code: a hard monthly destination-delivery cap, warning headers, and no overage invoices.

What counts

A billable destination delivery is an initial delivery created for one endpoint after an ingest or replay. One API message can create zero, one, or many destination deliveries. Test and live environments have separate counters.

Automatic retries are free and do not increment the meter.
Replay creates new billable destination deliveries for current subscribers.
Endpoint count is a separate cap at create time (3 / 100 / 1,000 by plan).

At the cap

Developer 10,000 / Launch 500,000 / Scale 3,000,000 destination deliveries per UTC month. When a requested fan-out would exceed the limit, ingest or replay returns HTTP 429 with code: plan_limit_deliveries. Already-accepted deliveries continue. There is no metered overage.

No surprise invoices

Outemit does not bill extra for going over the included deliveries. It rejects new fan-out instead. That is the current product, not a hidden spend limit.

70 / 90 / 100%

Ingest responses include X-Outemit-Quota-Used and, once you cross a threshold, X-Outemit-Quota-Warning with value 70, 90, or 100. Dashboard Settings → Billing shows used versus limit for the current Test/Live toggle.

Spend limits

There are no metered overage invoices. Operators may set a lower monthly delivery cap per org with Worker var OUTEMIT_ORG_MESSAGE_CAPS (JSON map of org id → integer). Ingest still returns HTTP 429 at that effective cap. Cancel and refund webhooks map the workspace back to Free limits. Operator notes: docs/ops/QUOTA.md. See also pricing.