🔑 What Yearly PRO API access includes
A Yearly PRO plan includes API access for your own Search Atlas account. You can call supported endpoints to run and retrieve SEO work, including site audits, as long as you stay inside your plan quotas and the API terms.
API access is tied to your account. It is meant for your team, your clients, and the products you operate under your brand. It is not an open public service that anyone on the internet can call without authentication.
🏷️ White-label audits of third-party domains
Yes. On Yearly PRO you may audit third-party domains, such as client sites or sales prospects, and present the results with your own branding. A brand name such as Slake is your white-label identity. Search Atlas does not need to appear on the client-facing report or portal when white-label is enabled for your account.
- Keep your API key on your server. Never place it in public website code, a browser app, or a shared document.
- Only send requests for domains you are authorized to review for a client or prospect.
- Show results inside your own app, portal, or report. Do not republish Search Atlas as an unauthenticated public API.
- White-label changes how results are branded. It does not raise quotas or remove plan limits.
If you want to resell raw API access to other businesses, contact the team before launch. Standard PRO white-label covers your branded delivery, not an open API offered to the general public.
📊 How quotas and credits are used
Each audit, crawl, or monitored project draws from the quota shown on your plan usage page. Credits are counted when the work runs, not when you later view or export the report.
- Consumed: starting a site audit or crawl, adding a domain that is actively monitored, and any other metered API action listed for that endpoint.
- Not consumed again: opening an existing report, applying your white-label logo, or downloading results that were already generated.
- Refreshed: recurring quotas reset on your Yearly PRO billing cycle. Unused units do not roll over unless your plan page says they do.
Check Plan and usage in the platform before a large batch of third-party audits. The usage page is the source of truth for remaining credits.
📦 What archiving does to credits
Archiving a project stops future monitoring and scheduled work for that domain. It does not refund credits already used by a completed audit or crawl.
- Completed work stays consumed.
- Archived projects no longer draw the next monitoring cycle.
- You can usually restore an archived project later, and monitoring will count against quota again from that point.
- Archive does not reset your Yearly PRO allowance early.
Archive projects you no longer check so active slots stay available. Do not archive and restore the same domain to try to recover spent credits. That usage is not returned.
🤖 Why Perplexity AI visibility is limited
The Perplexity AI visibility source has been retired. A limitation on a PRO account is expected. It is not a failed payment, a yearly-versus-monthly difference, or a white-label restriction.
- New Perplexity checks are no longer available on PRO.
- Any older Perplexity results may remain viewable only where they were already collected.
- Other AI visibility and SEO modules on your plan are unchanged.
Use the AI visibility tools that are still listed as active in your account. Ignore Perplexity metrics when you scope a Slake-branded audit so clients are not promised a retired data source.
✅ How to avoid quota surprises
- Confirm Yearly PRO API and white-label are active under plan settings.
- Store the API key server-side and restrict who can generate audits.
- Estimate domains before a batch, then compare with remaining credits.
- Archive finished prospect audits so they do not keep monitoring.
- Tell clients that Perplexity visibility is retired and exclude it from branded reports.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.