Credit costs reference

Compare current Rankability outcome allowances with legacy full-platform credit rates and the multipliers used by research, tracking, audit, and crawler actions.

Rankability uses completed-outcome allowances on current plans and credits on existing full-platform plans. Other full-platform tools can multiply a credit rate by keywords, platforms, locations, pages, competitors, or targets.

Use this page to understand the usage shown before an action. Confirm that you are in the intended organization and workspace, then use Settings → Billing to identify whether the account has outcome allowances or a shared credit balance.

Copywriter usage by contract

Action	Current Rankability plans	Existing full-platform plans
Research and brief only	0 outcome units	0 credits
Completed new content asset	1 content-asset unit	750 credits
Completed existing-content optimization	1 optimization unit	400 credits
Successful requested full-document rewrite	1 rewrite unit	250 credits
Quick mode outcome	1 optimization unit	400 credits
Automatic fact enrichment, retries, and repairs	0 additional units	0 additional credits
Autopilot completed content asset	1 content-asset unit	750 credits
Manual editing, export, and publishing	0	0

Copywriter usage is outcome-based under both contracts. Research depth and selected platforms change the evidence gathered, not the completed-outcome amount. Current-plan allowances reset monthly and do not roll over. Full-platform credits follow the balance and rollover behavior described in Understanding billing, allowances, and credits.

The current in-app Create workflow does not expose Quick mode as a new-project option. The rate remains listed for existing projects and supported automation paths that can still produce that outcome.

Existing full-platform accounts can also encounter guided-plan, First Win, or other legacy credit actions. Use the cost displayed by that account rather than applying those rates to a current Rankability allowance.

Research

Action	Credits
Keyword research	500
Deep trending, Reddit, YouTube, or ecommerce research	750
Batch analysis	75 per keyword
Domain explorer	600
Gap analysis	750 per competitor
GSC import	1,500
Domain history	400
AI keyword filter	200
On-demand rank check	10

Track

Tracking charges per keyword, per platform, per scan. Local Pack charges 10 credits per grid point, then multiplies across the tracked keywords and locations included in the run. See Supported tracking platforms for the current platform table and grid examples. Citation analysis costs 75 credits per newly analyzed page.

Serena and brand

Action	Credits
Chat	Free
URL import	75 per page
Google Reviews import	10
Deep research	100
Contradiction scan	25 per source
Brand voice autofill	100
Brand voice extraction	300

Audit, Promote, and other tools

Action	Credits
Page audit	150
Site audit crawl	1 per 5 pages
Audit keyword identification	25 per page when AI identification is needed
Log audit	200
Batch URL analysis	10 per URL
Backlink list	10 per live page load
Backlink CSV export	75
Prospector discovery	2,000
Prospect enrichment	100 per target
Report generation	500
Prospect scan	200
Serena verified link fix	5 per verified fix

Public crawler API

Action	Credits
Scrape	10 per successfully fetched page
Crawl	10 per successfully crawled page
Extract	50 per successful extraction

Charging rules

Copywriter's usage above is fixed by completed outcome. For other full-platform tools, locations, keywords, pages, competitors, targets, and other units can multiply the total. Use the estimate in the product or API response as the final pre-run reference. Success-only actions release reservations when they fail before their charge point; Autopilot consumes its outcome after a usable draft exists, even if a later finishing step needs attention.

Estimate a run

1. Configure the action without starting it.

2. Review every count that can multiply the base rate, especially platforms and locations in Track, pages in audits and crawler jobs, and competitors in gap analysis.

3. Compare the displayed total with the matching remaining allowance or available credit balance.

4. Start the run only after the scope and total are correct.

5. After completion, open the billing transaction to confirm the operation, description, and final amount.

A reservation can temporarily reduce available usage while work is active. The final usage record may appear only after the operation reaches its charge point. A retry can become a separate metered run, so check the original status before starting another copy.

Limits and unavailable states

• A listed base rate does not guarantee that a feature is enabled for every account or that every input is eligible.

• Cached or complimentary behavior applies only when Rankability labels the specific action that way.

• API and MCP callers should resolve the active contract with GET /api/agent/v1/usage or get_usage_and_limits; do not infer it from an account name or hard-code this table as billing logic.

• Plan allowances and public pricing can change independently of legacy per-action credit rates. See Understanding billing, allowances, and credits for resets, balances, rollover, and plan behavior.

If the charge is unexpected

Do not repeat the action immediately. Record the organization, client, operation, displayed estimate, transaction description, and time. First compare the configured units with Supported tracking platforms or the relevant workflow guide. If the transaction still does not match the approved scope, contact support with those details.