Xizor documentation
What Xizor is: StoreKit 2 payments, server-driven paywalls authored as web code, subscription analytics, and an MCP server for AI agents.
Xizor is the AI-native subscription platform for mobile apps. It gives you four things that normally require four different products:
- Native StoreKit 2 payments — XizorKit (Swift) and @xizor/expo (React Native) handle purchases, restores, and server-side receipt verification. Entitlements are always computed on the server from cryptographically verified transactions.
- Server-hosted paywalls, authored as web code — paywalls are self-contained web documents edited in the dashboard (or by an AI agent) and served to the SDKs as a page rendered in a WebView, with StoreKit and analytics staying native via a bridge. Publishing a change makes it live at the very next presentation, without an app update.
- Complete subscription analytics — MRR, revenue, churn, trial conversion, LTV, ARPU, cohort retention, and per-paywall funnels, computed from App Store Server Notifications and verified transactions.
- A built-in MCP server — connect Claude, ChatGPT, or Gemini with OAuth 2.1 and your agent can read every stat and _write_: draft, localize, and publish paywalls from a chat prompt.
How it fits together
Your app
- XizorKit (Swift)
- @xizor/expo (React Native)
App Store
- Server Notifications V2
api.xizor.dev
- JWS verification · entitlements · paywall delivery (ETag)
Xizor platform
- dashboard.xizor.dev — editor, stats
- mcp.xizor.dev — AI agents (OAuth 2.1)
Your server (optional)
- apple.did_renew, apple.expired, …
Your app talks to api.xizor.dev with a publishable API key. Apple talks to the same API via App Store Server Notifications V2, so renewals, refunds, and billing issues keep your data current even while the app is closed. The dashboard and the MCP server sit on top of the same data — what your agent sees is exactly what you see.
Where to go next
| Guide | What you get |
|---|---|
| iOS quickstart | XizorKit installed, purchases and paywalls working in SwiftUI |
| Expo quickstart | @xizor/expo with provider, hooks, and the WebView paywall renderer |
| Migrate from Superwall | Concept mapping, automatic subscriber migration, and the cutover checklist |
| Apple setup | App Store Connect key + Server Notifications wired to Xizor |
| Paywalls | Placements, versions, save-to-live, and the full document schema |
| Analytics | Exact definitions behind every metric |
| MCP server | Your subscription business inside Claude, ChatGPT, or Gemini |
| REST API | The full api.xizor.dev reference and webhook verification |
| For coding agents | A copy-paste prompt that integrates Xizor into an app |
The five-minute version
- Sign up at dashboard.xizor.dev and create an app — you get a publishable API key (
xz_pub_…). - Complete the Apple setup: In-App Purchase key + Server Notifications URL.
- Install a SDK and call
configurewith your key (iOS / Expo). - Create a paywall in the dashboard, assign it to a placement (e.g.
onboarding), and present it from the SDK. - Optionally connect your AI agent — and let it run your paywall experiments.
Machine-readable indexes of these docs live at /llms.txt and /llms-full.txt.