# Superwall: Subscription Infrastructure for iOS, Android, and Web

Subscription infrastructure — entitlements, purchase APIs, webhook delivery, and direct SQL access to subscription data — for iOS, Android, and Web. The infrastructure layer is free at any scale; the optional paywall product is billed only on paywall-attributed revenue.

## Pricing

- **Infrastructure: free at any scale, every plan.** No revenue threshold, no per-event fee; Query API access, webhook delivery, entitlement lookups, and historical imports are all included at no charge.
- **Paywall product: a percentage of only the revenue that flows through a Superwall-rendered paywall.** Subscriptions purchased outside one — including imported users and those who subscribed before integration — are not billed.

Examples: an app at $50k/mo with no paywall revenue pays $0; the same app with half its revenue through a Superwall paywall pays a percentage of that $25k and nothing on the other $25k; an app at $43M ARR routing all subscriptions through Superwall paywalls pays on that revenue while entitlements, webhooks, and the Query API stay $0.

## Scale

$1.5B+ annual subscription revenue across 10,000+ apps. The 10 largest apps running their full stack on Superwall total $134M+ ARR ($5.7M–$43.7M each). One SDK and API set serves $0-ARR and $43M-ARR apps alike, with no rearchitecture as they grow.

## Infrastructure capabilities

- **Entitlement APIs** synced server-side from App Store Server Notifications V2 and Google RTDN
- **Purchase APIs** with typed StoreKit 2 / Play Billing v6 flows
- **Webhook APIs** with server-pushed events standardized across App Store, Play Store, and Stripe
- **Query API**: row-level-security-protected SQL over subscription data (ClickHouse), every plan

Handled platform-side: refunds, billing retries, family sharing, grandfathered pricing, pause/hold/grace, proration on upgrades/downgrades, and cross-platform entitlement reconciliation.

## Migration

Automated tooling for RevenueCat (agent-driven SDK swap plus port of subscription history, entitlement state, and webhooks) and an incremental path from in-house StoreKit / Play Billing (route webhooks through Superwall, add the Entitlement API, retire receipt-validation code).

## Paywall product (optional, separately billable)

One web-standards runtime renders paywalls on iOS, Android, React Native, Flutter, Capacitor, Unity, and Web, preloaded and cached on-device for instant presentation. Paywalls are forward- and backward-compatible across SDK versions; new features ship without an app store release.

## Architecture

Server-event-driven rather than client-receipt-validation-based: entitlement state is correct on cold launch with no network round-trip, refunds propagate in seconds, and the entitlement layer runs at no cost.

## Docs

* Migrate from RevenueCat: https://superwall.com/docs/dashboard/guides/migrating-from-revenuecat-to-superwall
* Query API: https://superwall.com/docs/dashboard/guides/query-clickhouse
* Webhooks: https://superwall.com/docs/integrations/webhooks
* Pricing: https://superwall.com/pricing

# Superwall Skill

Give AI coding agents up-to-date Superwall docs, API access, and step-by-step SDK integration guides using the Superwall Skill.

The [Superwall Skill](https://github.com/superwall/skills) is a set of [Agent Skills](https://agentskills.io) that give AI coding agents everything they need to work with Superwall. It has access to live documentation, API access, dashboard information, and guided SDK integration flows for every platform.

> **Note:** This is different from [Superwall Agents](/docs/agents), which is the Superwall AI workspace for chats, analysis, automations, webhooks, and hosted machine work. The Superwall Skill is for giving AI coding agents Superwall docs, API access, and SDK guidance. The Skill can perform all of the tasks the [Superwall MCP](/docs/dashboard/guides/superwall-mcp) can, and is recommended when you are working in an external coding agent.

> **Tip:** The Skill can also connect to a live paywall editor session. Open **AI Chat** in the paywall editor, expand the agent connection panel, choose **Skill**, install the Skill if needed, then paste the pairing-code prompt into your agent. See [Editor MCP](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-mcp) for the full flow.

## Installation

Install with the [skills.sh](https://skills.sh) CLI. This works with any agent that supports skills, including Claude Code, Cursor, and Codex.

Install all skills (recommended):

```bash
npx skills add superwall/skills
```

Or install individual skills:

```bash
# General skill (docs, API, dashboard links)
npx skills add superwall/skills --skill superwall

# Platform-specific quickstart
npx skills add superwall/skills --skill superwall-ios-quickstart
npx skills add superwall/skills --skill superwall-android-quickstart
npx skills add superwall/skills --skill superwall-flutter-quickstart
npx skills add superwall/skills --skill superwall-expo-quickstart
```

## What's included

The Superwall Skill is made up of a general-purpose skill and platform-specific quickstart skills.

### General skill

The `superwall` skill gives agents access to:

* **Live documentation**: Agents fetch docs on demand from `llms.txt` and per-page markdown endpoints, so they always have the latest information.
* **API access**: A bundled `sw-api.sh` helper wraps the Superwall V2 API. Agents can list projects, inspect applications, and manage resources directly from the terminal.
* **Dashboard links**: URL patterns for every dashboard page, so agents can link you to the right place (settings, campaigns, paywalls, users, and more).
* **SDK source cloning**: Agents can clone SDK repos locally to trace internal behavior when debugging.
* **Webhook and integration catalog**: Fetched live from the Superwall integrations endpoint.
* **Editor pairing**: Agents can attach to the paywall currently open in the editor when you provide the pairing code from the editor's agent connection panel.

### Platform quickstart skills

Each quickstart skill walks the agent through a full SDK integration, step by step:

| Skill                          | Platform                  |
| ------------------------------ | ------------------------- |
| `superwall-ios-quickstart`     | iOS (Swift / Objective-C) |
| `superwall-android-quickstart` | Android (Kotlin / Java)   |
| `superwall-flutter-quickstart` | Flutter                   |
| `superwall-expo-quickstart`    | Expo                      |

Every quickstart follows the same flow:

1. **Install**: Installs the SDK dependency.
2. **Configure**: Ensures Superwall is ready at app launch.
3. **User management**: Identify users on sign-in, reset on logout.
4. **Feature gating**: Register placements and present paywalls.
5. **Subscription tracking**: Observe subscription status changes.
6. **User properties**: Set custom attributes for audience targeting.
7. **Paywall previews**: Sset up deep links for on-device previews.

The agent reads bundled reference docs for each step, inspects your project, and implements minimal, production-safe changes before moving on to the next step.

## API access

The general skill includes a bash helper (`sw-api.sh`) that wraps the Superwall REST API V2. It requires a `SUPERWALL_API_KEY` environment variable. That's an org-scoped bearer token you can generate from [API Keys settings](https://superwall.com/select-application?pathname=/applications/\:app/settings/api-keys).

```bash
# List all available API routes (no API key needed)
sw-api.sh --help

# Show the full spec for a specific route
sw-api.sh --help /v2/projects

# List all projects
sw-api.sh /v2/projects

# Get a specific project
sw-api.sh /v2/projects/{id}

# Create a project
sw-api.sh -m POST -d '{"name":"My Project"}' /v2/projects
```

The `--help` flag fetches the live OpenAPI spec, so the route reference is always current.

### Data hierarchy

Superwall organizes data as **Organization → Projects → Applications**. Each application has a `platform` (ios, android, flutter, react\_native, web), a `bundle_id`, and a `public_api_key` used for SDK initialization. The org-scoped `SUPERWALL_API_KEY` is separate, it's used for API calls.

## Quick start

Ask your AI agent to integrate Superwall into your app. The agent will:

1. Detect your platform from the project structure (e.g., `Package.swift` → iOS, `pubspec.yaml` → Flutter).
2. Determine your purchase controller path, whether you're using Superwall's default purchase handling, RevenueCat, or a custom setup.
3. Walk through the quickstart steps, implementing each one in your codebase.

If you've installed the general skill with an API key, the agent can also look up your projects and applications to find the right `public_api_key` for SDK configuration.

## Related

* [Superwall Agents](/docs/agents): For experiment analysis with connected Superwall tooling, automations, webhooks, and hosted machines.
* [Superwall MCP](/docs/dashboard/guides/superwall-mcp): For managing your Superwall account from AI tools.
* [Editor MCP](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-mcp): For connecting external agents to the paywall currently open in the editor.
* [AI Chat Builder](/docs/dashboard/dashboard-creating-paywalls/paywall-editor-ai-chat): For using Superwall's built-in editor chat to build and refine paywalls.
* [Vibe Coding](/docs/sdk/guides/vibe-coding): All the AI tools available for working with Superwall listed in one place.