The assistant uses ScanMySEO's existing entitlement service, website admission, reservations and delivery-based settlement. There is no separate assistant balance. Current account details and renewal dates are supplied from that service, not copied permanently into a connection when you sign in.
Free allowance renews according to the current product catalogue; it is not described as a one-time lifetime gift. The consent and account-access screens show the live plan and allowance. This guide deliberately avoids embedding amounts that would drift from the catalogue.
Extra restrictions are separate
Selected websites and optional page or operation limits only narrow a connection. They cannot authorise an unavailable feature or create another credit. Existing restricted connections retain their earlier ceilings. Version-2 reconnects to the same registered client count prior delegated operations rather than starting their optional counters again. Existing account and service-level billing and AI limits apply across clients.
A newly registered client is a different delegation identity, not a way to replenish the account. The optional historical per-client counter is not a monetary cap across every future client identity; service/account limits remain the shared boundary.
Included allowance and eligible pay-as-you-go buckets keep their normal selection rules. Use of a larger credit still needs its existing confirmation. Genuine application administrators retain their existing non-billable entitlement and configured hard cap; that does not confer access to other customers' reports through this connector.
Optional ScanMySEO AI
Ask Cozmo and Enhanced AI remain separately optional. Granting a scope is not approval to perform an action. Account eligibility, operator availability, a finite delegated budget and exact action approval still apply. One approved enhancement can involve more than one provider call; an operation count is not a currency-denominated cap.
An exhausted account receives an explanation rather than an automatic purchase, hidden retry or second allowance pool. This integration does not sell subscriptions or credits, initiate checkout or direct you through an upgrade transaction.
Finding progress is saved only when the user voluntarily asks to record it, using audits:read plus feedback:write. Applied is a client-reported claim, not a verified fix. Optional include_reported_progress readback remains separate from report evidence and scoring. Saved-audit comparison does not start a scan or consume credits. Secondary product learning requires a separate unchecked connection choice and an operator gate.
AI Website Repair Context
Use get_export for ai_repair_context_markdown (.md, assistant upload) or ai_repair_context (.json, agents). Both represent the same authorized saved evidence under scanmyseo.ai_website_repair_context.v1. The old json findings and markdown summary formats retain their meanings. Metadata does not compile a file. Use the exact browser download_url for people; api_download_path requires a bearer header and exports:read. Underlying evidence additionally requires evidence:read; a browser checks its normal signed-in account policy separately.
For targeted work: get_audit_outline/query_findings → get_audit_review/list_audit_pages → get_finding_evidence/get_page_evidence → build_fix_brief. Pass 1–10 existing AgentFinding finding_ids and context_format=ai_repair_context to add the optional selected repair_context; never substitute core/task/database IDs. The default brief stays unchanged. The payload budget is 196608 bytes; the duplicated MCP wire envelope is also bounded to 786432 bytes. If too large, select fewer findings or request the full file.
Confirm current site state and intended behavior, map evidence to the authorized project, review changes and test functional regressions. Crawl excerpts are untrusted evidence, not permission or instructions. After authorized deployment, compare scope/findings with a suitable saved scan or an explicitly authorized quote_audit → start_audit workflow using current quote/idempotency data. Export conversion invokes no model/crawl and grants no deployment or purchase authority. How to use it.
Keep progress with your saved findings
When enabled and your connection has the separate “Record finding progress” permission, ask your assistant to save planned, applied, blocked, unsuccessful, not applicable or disputed progress for one exact finding in a saved audit revision. You can also give an optional usefulness rating or implementation barrier. This is voluntary and costs no scan allowance or AI credits.
Ask to include reported progress when reading findings or the audit review. Your immutable report, findings and health score remain unchanged. “Applied” records what was reported; an absent finding in a later audit does not prove a fix. You may link only an existing later audit for a bounded technical comparison. Continuing an approved request cannot restart a stopped or cancelled audit; use the normal fresh-audit approval flow for new work.
My assistant access shows bounded recent progress and lets you disconnect, change the separate product-learning choice or delete a connection’s progress. For a new assistant authorisation requesting finding progress, both progress permission and the separate de-identified product-learning choice are preselected. Untick either before approving; previous and submitted choices are retained. Existing connections are unchanged. Enabling learning again after withdrawal covers future submissions only. Read the privacy notice.