Pricing that scales
with every market

Choose Growth for teams managing up to five apps, Pro for growing portfolios of up to 10 apps, and Scale for larger portfolios of up to 25 apps. Choose Enterprise when you need a tailored rollout. Use the package finder for a starting point, or talk to us about your app and market mix.

Credits track how much work the Agent does for you, on a flat scale: researching a country costs 2 credits, and everything else costs 1. That covers a metadata suggestion for a locale, an AI screenshot, a screenshot localization, an in-app event or product-page pass, and an AI review reply. An Agent chat message costs 2 credits, because chat is priced by the model behind it and the one model we run today is the most capable one. So one app across 10 countries with a screenshot set is roughly 20 credits of research plus one per draft and image. Connecting an app, opening a storefront locale, reading your data, editing drafts, and publishing to the store are never charged, and research already cached is free.

Unused credits roll over. Each month's plan credits stay usable for about two months from the day they land, and we always spend the batch closest to expiring first. If you run out, only the credit-metered operation is refused and your draft stays in place; Spek never retries it automatically. Owners and admins can review Growth, Pro, or Scale in Billing. You can always connect an app, read your data, edit drafts, and publish.

Spek reads the live listing, researches each selected storefront in its own language and with its own market data, then drafts metadata and keyword changes in one review inbox. Accepted keywords are tracked daily so you can follow rank and visibility storefront by storefront.

Spek supports iOS apps on the App Store and Android apps on Google Play, with keyword research, localization, publishing, and ranking analytics. App Store workflows also include screenshot redesigns, custom product pages, and in-app event drafts through App Store Connect.

No. Spek connects with an App Store Connect API key—never a login, browser session, or stored cookie. Each workspace uses its own credentials, encrypted at rest and decrypted in memory only to sign official API requests.

Yes. Workspaces support owner, admin, editor, and viewer roles. Owners, admins, and editors can make changes; viewers stay read-only, so teammates can follow the work without receiving publishing access.

Annual pricing is 20% lower than the monthly option. The comparison shows the monthly equivalent so plans are easy to compare; the annual option is billed yearly.

Start with the apps and markets you will actively review, then consider the research and AI work you expect to request. A focused set of markets is easier to assess than running every possible locale without a reviewer. Check the current allowance and balance in your workspace, and distinguish new metered work from reading existing data or editing a saved draft. Your workload can change as the team expands its app portfolio, so use the plan comparison and in-product billing details to review the package that fits your current process.

A subscription belongs to a specific workspace, alongside its connected apps, members and credit balance. When you manage several teams or clients, check the workspace before reviewing billing or changing a plan. Membership in another workspace does not merge its subscription or store credentials with yours. This separation helps agencies keep client access and commercial responsibilities clear. Use the selected workspace's Billing page for its current package and payment information rather than assuming a plan shown in one account context applies everywhere.

Workspace owners and admins manage billing. Editors and viewers can inspect the package, status and balance without receiving permission to change payment details or cancel the subscription. Store publishing permissions are a separate part of the product, so a billing role should not be treated as proof that a particular provider action will succeed. If your team needs a plan change, have the responsible owner or admin review the exact package, cycle and confirmation details in the correct workspace.

Check the connected app count, target allowance, billing cycle and the amount and timing shown in the confirmation flow. Plan changes can take effect at different points in the paid period, and a lower app allowance must accommodate the workspace's current usage. The actual plan-change preview is the place to review the proposed charge and effective date. A saved selection or browser redirect is not itself confirmation that the subscription changed, so check the resulting Billing state after completing the requested flow.

Spek's data API is arranged through the team around the integration you need. Describe the datasets, stores, markets, request volume and delivery requirements when you contact us. A workspace plan supplies the app and research allowance shown for the product; it should not be read as an undocumented API quota, service agreement or set of publishing endpoints. Discussing the two scopes separately helps your team choose the product workflow and data access that match the application or reporting system you intend to build.

Existing drafts and available data remain part of the workspace; a refused credit-metered operation is not the same as deleting completed work. Read the operation's status and the current billing information to understand why it could not proceed. Spek does not automatically retry refused research after a payment, so review the intended request again when the balance allows it. Preparing more proposals, editing an existing draft and publishing an approved change are distinct activities, and the credit rules should be read for the activity you are actually requesting.