Search documentation
Jump to any section of the Crispy docs
Concepts
How Crispy works
The three ideas worth understanding before you build: what each key can do, how to drive multiple LinkedIn profiles, and the limits that keep your account safe.
Permission scopes
Each API key or connected account has a permission scope that controls which tools are available. Set the scope when generating an API key or connecting an account.
| Scope | Description |
|---|---|
core (default) | Default for all accounts. Covers the full daily loop: messaging, outbound, content, campaigns, lists, and intelligence. |
full_access | All 166 tools. For power users and builders who need webhooks, API key management, warm-up controls, advanced analytics, and raw LinkedIn API access. |
Choosing a scope
Most users should stay on core. Upgrade to full_access only when you need advanced infrastructure tooling.
| Use case | Scope |
|---|---|
| Daily outreach, content, campaigns, inbox | core |
| Webhooks, API key management, warm-up, raw API | full_access |
| Give to a client or contractor | core |
| Agency workspace, power builder | full_access |
All new accounts start on core. Self-upgrade to full_access any time via update_account_settings or from the dashboard.
Multi-account
Connect multiple LinkedIn profiles and operate on any of them from a single API key.
- Connect multiple LinkedIn profiles from your dashboard
- Use
get_accountto list all connected accounts and their IDs - Pass
account_idon any tool call to choose which profile to use - Omit
account_idto use the default account (the one linked to the API key)
Scope enforcement
Each connected account has its own scope. When you target a different account with account_id, Crispy enforces that account's scope, not your API key's. A full_access key cannot bypass a core account's restrictions.
Per-account limits
Safety limits are tracked per LinkedIn account, not per API key. Each connected profile gets its own daily limits. Use get_account to check remaining capacity across accounts.
LinkedIn safety limits
Crispy enforces daily limits per action type to protect your LinkedIn account from restrictions. These reset at midnight UTC. Check remaining capacity via the crispy://account/usage resource.
| Action | Daily limit | Tools |
|---|---|---|
| Search | 300 / day | search_people, search_companies, search_posts |
| Profile views | 250 / day | get_profile |
| Messages | 150 / day | send_message, send_inmail, send_voice_message, forward_message |
| Engagement | 100 / day | react_to_post, comment_on_post |
| Invitations | 15 / day | send_invitation |
| Posts | 10 / day | create_post |
These are the main categories. A few lower-volume actions (follows, endorsements, profile edits, raw API calls) are capped too, check crispy://account/usage for your live remaining capacity per category. Read-only tools (get_connections, list_posts, get_feed, etc.) have no safety limit. Hitting a limit returns a 429; see error codes.