In MCP, Search Atlas quota is only consumed when an action produces work. Understanding which actions consume credits — and which do not — helps you control usage and avoid unexpected costs.
🧠 Core Principle
Quota is charged when work is produced.
- If an action creates, generates, or submits something, it consumes quota.
- If an action only retrieves or displays data, it does not consume quota.
⚙️ How to Think About Usage
- Ask your AI assistant to perform an action.
- Determine the type of action: is it generating or creating something, or just reading existing data?
- If the action produces output, quota is consumed.
- If the action is read-only, no quota is consumed.
📊 Actions That DO Consume Credits
These actions produce work inside Search Atlas:
- AI content generation
- Running audits or crawls
- Creating campaigns (SEO, PPC, PR)
- Submitting data to external systems (indexing, citations, outreach)
📊 Actions That DO NOT Consume Credits
These actions are read-only or use existing data:
- Viewing reports or dashboards
- Retrieving backlinks or keyword data
- Reviewing previously generated content
- Publishing already-created content
🔁 Side-by-Side Examples
- Read-only — "Show me my backlinks": uses AI tokens, does not consume Search Atlas quota.
- Generate content — "Write an SEO article": uses AI tokens, consumes Search Atlas quota.
- Publish existing work — "Publish this article": uses AI tokens, does not consume additional quota.
⚠️ Important Notes
- Tokens are always consumed for interaction with the AI assistant.
- Quota is only consumed when work is produced.
- MCP does not bypass plan limits or pricing rules.
By understanding which actions consume credits and which do not, you can use MCP more efficiently. Focus on when work is actually being created, and you'll be able to predict and manage your Search Atlas usage with confidence.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.