Add subscriptions your users can buy in the simulated iPhone before you ship.
Describe the result in chat. The agent installs the integration, wires the app, and checks the connection before you ship.
What the agent sets up
One request covers the app code, provider connection, and working proof.
Configures the RevenueCat SDK with the public app key and keeps the secret API key in server storage.
Builds the paywall, entitlement checks, restore flow, and app-owned subscription state together.
Runs server-side API verification and returns a direct fix-it link when the key or permissions are wrong.
Values stay out of the conversation
Private values stay server-side. Stored values are resolved only by server tools. The agent receives the field name, runtime, verification status, and fix-it link, never the stored value.
Secret v2 API key used by the server-side verification probe and provisioning tools.
Create or manage this keyPublic SDK key used to configure RevenueCat in the app client.
Create or manage this keyA blocker comes with the next move
Contrast probes https://api.revenuecat.com/v2 from the server. It classifies a missing key, invalid key or permission, and an unreachable provider separately instead of returning a generic failure.
Each blocked result explains what failed and links to the provider screen where you can fix it. Run verification again and the project moves to Verified only after the provider accepts the probe.
Test the purchase before you ship
RevenueCat Test Store offerings render in peach and test purchases complete inside the preview. Revenue reporting beside your build is the next part of this story and is not yet a released workspace surface.