Billing and capacity
Two different models, and which one you are on
| Plan allowance | Units | |
|---|---|---|
| Who | business and both modes | api mode |
| Shape | a monthly pool that resets | a balance that depletes |
| Running out | 429 until the period rolls over |
429 until you buy more |
| Alerts | 80% and 100% | none on the allowance, because there is none |
GET /v1/usage tells you which you are on without guessing:
monthly_included_sends of 0 means units.
Plan allowances, as they stand
| Plan | Sends per minute | Included sends per month |
|---|---|---|
| Free | 1 | 3,000 |
| Founder | 10 | 10,000 |
| Essentials | 10 | 15,000 |
| Starter | 10 | 30,000 |
| Essentials Plus | 10 | 35,000 |
| Pro | 60 | 300,000 |
| Scale | 300 | 3,000,000 |
| api mode | 120 | unit-based |
Read your own from GET /v1/usage rather than this table.
These are the catalogue defaults and the catalogue is editable.
Units
Bought in packets and spent per send. The balance and its next expiry are on
the billing endpoint as send_units_balance and send_units_next_expiry.
Units expire. That is the part worth building around: a balance is not a
permanent credit, and send_units_next_expiry is the date to watch rather
than discovering a drop after it happens.
AI features have their own separate balance, which depletes independently.
Getting more capacity
In rough order of how quickly each takes effect:
Buy units. Immediate, and the right answer for a one-off spike. It raises the volume you can send, not the per-minute cap.
Upgrade the plan. Raises both the monthly allowance and the per-minute cap, and takes effect on the plan change rather than at the next period.
Ask. Caps are per workspace and are not immutable. If your traffic is legitimate and the shape of it does not fit a listed tier, say what you expect to send and when. That is a better conversation than discovering a cap during a launch. support@lockally.com.
What will not get you more capacity
A second API key. Caps are per workspace.
A second workspace for the same business, which is the same thing with more steps and reads as cap evasion.
Retrying harder. If the 429 came from a reputation throttle rather than
your plan, no amount of capacity helps, because the cap was lowered on
purpose. GET /v1/reputation says which it is.
Test sends are free
Nothing sent with an lk_test_ key counts against the allowance, units, the
per-minute cap, warm-up or reputation. Build and test as much as you like.