sending-limits-from-vendor-docslisted

# Limits come from the docs, not from your head Before a limit, pause, cap or threshold goes into code, read the provider's documentation, read how two or three market tools handle the same question, and check your own numbers. A rule with neither an external source nor your own measurement does not ship. Write the source in a comment next to the constant. ## Why One of our rules about stopping a profile after a platform refusal was invented from common sense. It sounded reasonable and it cost one client's sender a week of silence, because it measured our own single daily attempt rather than the platform's behavior. Ten minutes in the provider's docs answered the same question with a number. For example, the Unipile docs put a free LinkedIn account at about five personalized invitations a month and about 150 invitations a week without a note. That one line explained refusals we had been guessing about. ## How to apply 1. Write down the question in plain words: how many, how often, what to do on this error. 2. Open the provider's limits page (for LinkedIn via an API: Unipile Provider Limits or your provider's equivalent) and copy the relevant numbers with the link. 3. Open the methodology of two or three tools that solve the same problem (for example HeyReach, Linked Helper, Expandi) and note where they agree. 4. Pull your own measurement: sends, refusals, accept rate for the same profile type over a real period. 5. If the docs and your data disagree, name the gap and pick