Is Crispy safe to use?

Crispy applies a default daily cap per action category. A write is blocked when today's count reaches the cap in force. Counters reset at midnight UTC. LinkedIn's User Agreement section 8.2 prohibits bots and other unauthorized automated methods. These controls do not authorize the activity. They do not guarantee against restriction.

• Daily caps. Invitations, messages, posts, engagement, and the other write categories each have a default. The defaults are on the LinkedIn safety page.
• Spacing. Invitations, messages, and other writes wait a few random seconds after the last action on the same account.
• Warm-up. Optional. Crispy does not start it when you connect an account. It runs when you enable it. The auto preset ramps for 14 days and only lowers the cap.
• Business hours. Campaign sends fire inside a send window. The default window is 9:00 to 18:00 in the account's timezone.
• Daily range. You can set a minimum and a maximum per category. Crispy picks a cap inside that range each day.
• Block list. Campaigns skip anyone on your do-not-contact list.
• Account scope. The scopes you can set are full_access, core, and read_only. The names outbound and content are accepted and enforce the same tools as core.

Most read tools have no daily cap. Profile views and searches do, because they are LinkedIn activity.

You can set a lower cap. For invitations, Crispy rejects a cap above 50 per day. For messages, profile views, searches, engagement, and posts, Crispy does not enforce a maximum above the default.