> For the complete documentation index, see [llms.txt](https://help.rankability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rankability.com/account-and-settings/understanding-billing-and-credits.md).

# Understanding billing and usage

Rankability's full platform includes every tool and unlimited users. New customers pay $99 per active website each month at the introductory Founding Partner Rate. Existing full-platform customers keep their current price and unlimited client websites; Rankability does not automatically convert them to per-website billing.

Open **Settings → Billing** to see the active contract, website quantity, invoices, and pooled usage. This is the only usage section in the application; `/usage` redirects here.

## What counts as an active website

A client with a connected domain uses one active website slot on a per-website subscription. A client shell without a website does not use a paid slot. Before a new active website exceeds the paid quantity, an organization admin must confirm the Stripe billing change. Stripe shows or applies the applicable proration for the current period.

Grandfathered customers can add, remove, or replace client websites without changing their protected subscription price.

## Pooled usage instead of credits

Full-platform accounts do not manage a credit wallet or action-by-action prices. On-demand activity is pooled across the organization and shown as remaining percentages for rolling 24-hour and 7-day windows. Rankability keeps this indicator out of the way while usage is healthy.

If an on-demand window reaches its limit, new on-demand work pauses with a recovery time. Older activity continuously rolls out of the window, so capacity returns automatically. Work already saved remains available.

## Scheduled work is protected

Routine scheduled tracking and monitoring are recorded separately from on-demand work and are not blocked by the on-demand windows. Provider quotas, request-rate controls, concurrency safeguards, and abuse protections can still apply independently.

## API and MCP

The Agent API and hosted MCP connection use the same full-platform entitlement and pooled usage as the web application. `GET /api/agent/v1/usage` and `get_usage_and_limits` return percentage windows and recovery times. They do not return credit prices for full-platform accounts. Copywriter Core remains a separate product with completed-outcome allowances.

## Change or cancel a subscription

Per-website customers can change paid website quantity from **Settings → Billing**. Quantity cannot be reduced below the number of active websites. Existing protected customers do not use this control.

Use the cancellation controls in Billing to stop renewal. Access continues through the paid period shown there. The Stripe checkout or confirmation summary is authoritative for a new charge, proration, or recurring total.

## Troubleshooting

* **A website cannot be activated** — Check whether an admin needs to add a paid website slot.
* **On-demand work is paused** — Open Billing to see which rolling window reached its limit and when capacity begins returning.
* **Scheduled work did not run** — Check the project schedule, connection health, and provider or queue status; scheduled work does not consume the on-demand window.
* **Your legacy terms look different** — Do not start a new checkout. Existing full-platform subscriptions are protected; contact support with the organization and invoice details.
* **The Stripe total is unexpected** — Do not confirm the change. Compare the active website count and requested quantity, then contact support.

## Related articles

* [Control your usage](/account-and-settings/control-your-usage.md)
* [Connecting Rankability to AI assistants with MCP](/api/mcp-getting-started.md)
* [Troubleshooting common issues](/troubleshooting/troubleshooting-common-issues.md)