Plans, overage, and unit rates

The shape of a bill

Every month you pay the base fee for your tier. On top of that, three counters track the work your account did: search queries your shoppers ran, intelligence operations you triggered from the dashboard, and ingest operations (items created, updated, or deleted). Each counter has an included amount (the commit). Cross the commit on an axis and the extra bills at that tier's unit rate for that axis.

The per-unit rate is the same whether you're inside or outside your commit, so there's no cliff and nothing hidden. Upgrading to the next tier drops all three unit rates in bulk, in exchange for a higher base fee.

Overage on each axis

• Search — Overage is automatic. Shoppers send traffic; you keep serving them.
• Ingest — Overage is automatic. Catalog changes keep flowing.
• Intelligence — Overage is opt-in per merchant. Intelligence ops fire from passive dashboard loads, so silent billing would be a UX trap. Toggle overage on from the billing page if you want these surfaces to keep working past your included ops; otherwise they pause until the next period.

Spending cap

You can set a hard dollar cap on extra usage charges for the current period. Once you've accumulated that much in overage, requests return 429 until the period rolls over or you raise the cap. The base fee always bills regardless.

Keep reading

• Overage rates by tier — the actual per-unit numbers
• How overage works — metering, timing, and what shows on the invoice
• What counts as an intelligence op