Documentation / Event allowances

Event allowances and rate limits

Meridian Platform includes 1,000,000 Attribution Events per calendar month. Events above included volume bill as usage (see pricing). This page describes what producers and operators see — not commercial rates.

Monthly included volume

Each organization has a monthly included Attribution Event count (1M on Meridian Platform; custom on Enterprise). Usage is counted from accepted OASA records on POST /v1/meridian/events (UTC calendar month). Unused included volume does not roll over.

• Alerts at 80% and 100% — response may include a quota_warning; UI and account owners are notified. Ingest continues unless a hard cap is elected.
• Optional hard cap — when elected and usage reaches 100% of the cap, further ingest returns HTTP 429 with error: CAP_EXCEEDED / reason: CAP_EXCEEDED, the ceiling, and Retry-After until the next UTC month. The affected period is flagged incomplete for reports, chargeback, and reconciliation. Events are not silently dropped.

Per-key rate limits

Each ingest API key carries rate_limit_per_minute (and daily request limits). Exceeding the per-minute ceiling returns 429 with Retry-After and X-Meridian-Limit-Type: per_key_rate. That means slow down and retry — it is not a monthly rejection and does not by itself mark a period incomplete.

Recommendation: one ingest key per producer (collector, staging, SDK), not one shared key per customer.

Organization admins create ingest keys in Settings → Ingest keys. Each key allows 600 requests per minute and 100,000 requests per day; see Manage ingest keys.

Producer health

GET /v1/meridian/ingest/health (scope meridian:ingest) returns last-seen time, accepted / duplicate / rejected totals, duplicate rate, and key expiry warnings. Use it to detect silent producers and replay storms.

Retention

Raw agent_events default to 90-day retention. Financial rollups in spend_records follow a 7-year (2555-day) Timescale retention policy. Longer raw retention is a priced option — not an ad-hoc sales exception.

What this is not

OASA (/spec) is an open attribution standard and carries no commercial terms. Limits and allowances are Meridian product policy only.