REFRACTODocumentationBack to website ↗
Get started

Plans and usage

Find current prices, included quantities and workspace capabilities.

Refracto guideRead Markdown ↗

The public pricing page describes the content plans for Individuals, Companies, Publishers and Governments. The Developer page describes API access separately.

Use the current catalogue

Prices, included quantities and additional-unit charges come from the plan catalogue used by the website. Read that catalogue on the pricing page instead of treating copied figures in a guide as current.

Monthly and yearly prices describe different billing choices. Check the actual amount, billing period and applicable terms before confirming a purchase. A sandbox checkout is a test environment and does not establish that live billing is available.

Plan fees and extra usage

The plan fee stays in a monthly or yearly subscription. New self-service workspaces pay for usage beyond their included quantities from prepaid credit; buyers do not choose an invoice payment mode during checkout. Authorised staff can manage an exception from Admin. An unsettled extra-usage period must be reconciled before staff change its payment mode.

The checkout summary shows the catalogue plan price. An eligible promotion and the final amount are confirmed before payment; promotions apply to the plan fee, not extra usage or credit top-ups.

Workspace capabilities

A plan can govern content quantities, media, source options, archive access, Feed limits and MCP usage. Your workspace's enabled capabilities and permissions determine what you can actually do.

Do not interpret a visible catalogue feature as a guarantee that it is enabled in your workspace. Features labelled coming soon remain unavailable until their release is confirmed.

Limits and request budgets

An API or MCP limit may apply independently of the generation allowance. Read the current response headers and tenant context where provided. A rate-limit response is not a request to create another key or change tenants.

If the expected capability is absent, ask the workspace operator to check the configuration. See troubleshooting.

Next guideFeed API integration ↗