Plans

• Free : 100 credits / mo · free forever
• Builder : 5,000 credits / mo · $29/mo
• Growth : 25,000 credits / mo · $99/mo
• Business : 100,000 credits / mo · $199/mo

On success, meta.credits_charged shows what was deducted. If the balance is too low you get 402 with insufficient credits before the lookup runs.

No rate limits

Socify does not enforce request-per-minute or concurrency caps. Monthly credits are the only hard quota. Every plan includes all 9 platforms and 40 public endpoints: there is no per-platform unlock.

Upstream platforms can still fail or throttle on their side. Failed or unavailable lookups are not charged. Need more volume? Upgrade the plan or contact support@trysocify.com.

Best practices

• Cache stable data. Profile identity fields change slowly : cache for minutes/hours and only re-fetch when you need freshness.
• Bound your own concurrency. A sensible worker pool keeps your app predictable and avoids burning credits on retries when an upstream is flaky. Unbounded Promise.all over thousands of handles is rarely what you want.
• Respect monthly credits. Watch meta.credits_charged and dashboard usage. Stop or degrade gracefully on 402 instead of hammering.
• Retry only transient failures. Follow the retry strategy. Never retry 400 / 401 / 402 / 404 with the same payload.
• Separate keys by environment. Use distinct keys for prod, staging, and local so a leaked or revoked key does not take everything down.
• Prefer server-side calls. Keep the key off browsers and public clients; proxy through your backend or agent runtime.