Rate card
A rate card is a named pricing table that maps each task an agent performs to a price per unit, and is assigned to a customer to set what they pay per confirmed outcome.
A rate card is a named pricing table that maps each task to a price per unit. It is the layer that answers "what is this outcome worth for this customer". The billable condition decides whether a charge happens, attribution decides how many units to bill, and the rate card decides what a unit costs.
How it works
A rate card holds zero or more entries. Each entry maps one task to one price_per_unit, and each task appears at most once per card. Cards are identified by a lowercase key that is unique within an account, so standard, enterprise-2024 and agency_tier can coexist as pricing tiers.
Rate cards are defined once and shared. A customer is assigned at most one card at a time, which is what lets the same task be sold at different prices to different customers without duplicating the task itself.
When an outcome confirms, the invoiced amount is the entry's price_per_unit multiplied by the billing unit produced by attribution. For a flat per-outcome agent the unit is 1, so the entry price is the charge.
Prices are snapshotted
The price is read from the customer's rate card when the outcome is created, and recorded on that outcome. Editing a card later does not reprice outcomes that already exist; only new ones pick up the change. Deleting a card archives it rather than removing it, so assignments and historical outcomes stay intact.
That snapshot is what makes a repricing safe to do mid-period. An outcome still working its way through its settlement period keeps the price it was opened with, and an invoice never moves under a customer who has already been told what a result would cost.