Usage Limits
Last updated: October 7, 2026
Creator Lookup offers API and MCP access so you can use the platform from your own software and AI agents. To keep the service fast and reliable for everyone, all usage is subject to the limits below. These are the "Usage Limits" referenced in Section 4.6.2 of our Terms of Service.
Who can use the API and MCP
API and MCP access requires an active paid plan (including AppSumo plans) or a positive credit balance. Accounts without either can keep using the Creator Lookup web app, but can't make API or MCP requests.
How limits apply
- Per account. Limits are tracked per account, not per key. Every API key, MCP connection, AI chat session, and browser session on your account draws from the same allowance.
- Across every channel. A search counts the same whether it comes from the web app, the API, an MCP client, or Creator Lookup AI chat.
- Separate from credits. Rate limits control how fast you can make requests. Credits cover what certain actions cost. A request must be within your limits and, where applicable, covered by your credits.
- Reset times. Per minute and per hour limits use rolling windows. Daily limits reset at 00:00 UTC.
Current limits
| Action | Free | Paid & AppSumo |
|---|---|---|
| Creator searches, per minute | 20 | 20 |
| Creator searches, per day | 300 | 1,500 |
| Live profile refreshes, per hour | 10 | 60 |
| Live profile refreshes, per day | 20 | 300 |
| Enrichment previews, per day | 50 | 50 |
Creator searches include quick search and full profile search. Live profile refreshes are requests that pull fresh data directly from a social platform instead of our database.
Credit costs
Most actions are included in your plan. A small number of high-volume actions draw from your credit balance once you exceed the free daily tier.
| Action | Free tier (per day) | Cost beyond free tier |
|---|---|---|
| Quick searches | First 100 searches/day | 1 credit per search after 100 |
| Contact unlocks | Included in plan allowance | Per plan or add-on |
| Exports | Included in plan allowance | Per plan or add-on |
The free tier resets daily at 00:00 UTC. Credits are deducted only after your free tier is exhausted for the day. If your credit balance reaches zero, quick searches above 100 will return a 402 Payment Required error until your balance is topped up or the daily tier resets.
Rate limit headers
Responses from limited endpoints include:
| Header | Meaning |
|---|---|
X-RateLimit-Limit | Requests allowed in the current window |
X-RateLimit-Remaining | Requests left in the current window |
X-RateLimit-Reset | Unix timestamp when the current window resets |
Retry-After | Seconds to wait before retrying (on 429 responses) |
When you hit a limit
The API returns 429 Too Many Requests with a JSON body:
{
"error": "rate_limited",
"limit": "searches_per_minute",
"message": "Search limit reached (20 per minute). Retry in 42 seconds.",
"retry_after": 42
}MCP tools return the same information as a readable tool error, so your agent can see the limit and wait before trying again.
Access errors
| Status | Code | Meaning |
|---|---|---|
| 403 | api_access_requires_plan | Your account needs an active plan or credits to use the API or MCP |
| 403 | account_suspended | API and MCP access on this account has been disabled. Contact support. |
Best practices for agents and integrations
- Honor
Retry-After. Back off when you receive a 429 instead of retrying immediately. - Avoid large parallel fan-outs. Run requests sequentially or with modest concurrency.
- Reuse results. Save creators to lists and use your search history instead of rerunning identical searches.
- Cap your loops. Set a maximum number of calls per task so a misbehaving agent can't burn through your daily allowance.
Not allowed
- Creating or using multiple accounts to get around limits
- Sharing API keys or credentials outside your organization
- Calling internal or undocumented endpoints
- Automating the web app (headless browsers, scripted sessions) instead of using the API or MCP
Enforcement
We monitor usage across all channels. If an account exceeds or tries to circumvent these limits, or its usage puts the service at risk, we may throttle requests, disable API and MCP access, or suspend the account. Where practical we'll reach out first, but we may act immediately when usage is abusive.
Need higher limits?
If your use case needs more, email support@creatorlookup.com with what you're building and your expected volume.
Changes
We may adjust these limits as the platform evolves. Changes are posted on this page and reflected in the "Last updated" date.