Overview
Spek supports App Store and Google Play apps. After activating your workspace, connect your store account and choose the apps you want Spek to work on. The API-key walkthrough below covers App Store Connect.
New accounts stay inside onboarding: choose a workspace plan, complete Stripe-hosted Checkout, and the store steps open after the paid invoice is confirmed. Visiting Pricing before signup is optional.
Nothing you do here changes your listing. Connecting an account lets Spek read it; every change it later proposes waits for you.
Before you start
For the App Store steps below, you need an App Store Connect account you can create an API key in. That usually means an Account Holder or Admin, because those are the roles that can reach the Integrations area of Users and Access.
The two setup steps
App Store Connect setup is two steps, and the wizard walks you through them in order.
Connect your store account
The form asks for three things: Issuer ID, Key ID and Private key (.p8). Spek signs its own requests with these and never asks for an Apple ID or a password. Full walkthrough in connect App Store Connect.
All three values come from one page in App Store Connect. Pick your app
Spek reads the app catalog your key can see and you choose one from it. There is nothing to type in by hand.
What happens next
With an app connected, set the agent up and start a run. That means choosing markets and adding relevant competitors for your app.
The first run pulls fresh research for every market you selected, so it takes longer than later ones. Nothing it produces touches your listing until you accept it and then publish.
Common questions
Do I need to be the Account Holder?
No, but you need a role that can reach Users and Access in App Store Connect, which usually means Account Holder or Admin. The key itself only needs App Manager access.
The person creating the credential and the role assigned to the key have different responsibilities. Follow the App Store Connect guide for the intended account, then confirm the app is visible through that connection. Never substitute another developer account's key just to get past a missing setup control.
What happens to my listing while I set this up?
Nothing. Spek reads your listing and drafts against a copy. Publishing is a separate action you take later, from the editor.
What should I prepare before starting the first review?
Have access to the correct workspace and store account, know which app you want to work on, and choose a small number of markets your team can review carefully. For the App Store Connect steps in this guide, the connection uses an API key belonging to that developer account. It also helps to know your app's main audience, important brand wording and a few relevant competitors. You do not need a finished keyword plan beforehand: the first Agent run prepares research and proposals that you can evaluate against this product context.
Should I connect every app and market immediately?
Begin with an app whose listing and audience you understand. A focused first review makes it easier to check proposals, learn where accepted drafts appear and understand what publishing sends. You can add more apps within your plan allowance and change market choices later. Expanding the scope also expands the amount of wording and market context somebody needs to review. For an agency, confirm the client workspace before connecting its account, rather than using the first workspace that happens to be open.
What if checkout returns but store setup has not opened?
Workspace activation depends on the confirmed payment state, not only on returning from the checkout page. Look at the status shown in onboarding before starting another purchase. If it remains unresolved, contact Spek with the account email, approximate time and the message on screen. Never send card details or a store private key in that report. A workspace invitation follows its own join flow, so joining an existing team should not be confused with purchasing a separate workspace subscription.
How do I know the first run is ready for my attention?
Return to the Agent page and inspect the displayed run state and the proposals available for each market. Review the actual field changes before accepting them. Then open the Editor for the same app and locale to check the saved draft as a complete listing, including wording that the Agent did not change. Publishing remains a later action. If a run shows a failure or needs attention, use its visible status to decide the next step instead of assuming that an empty inbox means research succeeded with no recommendations.