Your agent installs this paywall in one command.

The verify receipt

Installed by your agent. Proven by your agent. When the install finishes, one more command checks the work and prints a plain-text receipt:

$ node add.mjs paywall --verify
inno9 paywall: VERIFY PASS

files present · deps installed · types clean — review your agent's work in ten seconds, then get back to what makes your app different.

The receipt is machine-readable too: your agent can run the check and read its own result. Plain facts about this module for agents are in Agent facts at the bottom of this page.

The problem → the shift

The problem.

You ship React Native apps by directing an AI agent. Screens, navigation, state — the agent handles those. Then you ask it for subscriptions, and it improvises. Fetching offerings, purchase error states, restore flows, entitlement gating, config validation — improvised from scratch, slightly different in every project, and each one a place where a purchase silently fails or a store review bounces.

Billing is exactly the kind of work agents improvise badly. It's not a differentiator. It's plumbing — and plumbing should be pre-built.

The shift.

Agents assemble software from parts. You don't scaffold a paywall; you install one. inno9 modules are pre-built parts with agent instructions and automated verification baked in — your agent runs one command and gets back to work on what makes your app different.

After install, the code lives in your repo. Not a black-box dependency — six readable TypeScript files you own, in src/paywall/.

What's in the box

Exactly what the installer copies into src/paywall/ (from the module manifest — nothing more, nothing less):

Also in the zip

• add.mjs — the installer. Copies the files, installs react-native-purchases@^10.9.0 and zod@^3.25 for you.
• --verify mode — checks files present, dependencies installed, tsc --noEmit clean. Prints inno9 paywall: VERIFY PASS when green.
• 4 analytics events out of the box — paywall_view, trial_start, subscribe, restore — route them to any analytics via setPaywallEventHandler.

Install & verify

The copy step is measured, not estimated: ~2 seconds on a clean create-expo-app app (warm npm cache) — including dependency install.

# 1. Unzip and install into your app (from the unzipped folder)
node add.mjs paywall --target /path/to/your-app

# 2. Regenerate the native project (react-native-purchases autolinks —
#    no app.json plugin registration needed)
cd /path/to/your-app
npx expo prebuild

# 3. Build a dev client (EAS or local) and edit one file:
#    src/paywall/paywall.config.ts  →  API key, entitlement ID, product IDs, copy, colors

# 4. Verify (from your app root)
node /path/to/add.mjs paywall --verify

Heads-up: this module includes native code — it does not run in Expo Go. You need a dev build (npx expo prebuild + EAS or local build).

What it integrates with

Only what's actually in the module (no invented integrations):

• RevenueCat — offerings (the Current offering drives what's sold; product IDs in the config are informational), entitlements, purchase + restore, customer info. Requires a RevenueCat account with an app, an entitlement, and monthly/annual products.
• react-native-purchases ^10.9.0 — installed for you, integrates via autolinking. No plugin entry in app.json. Wraps Google Play Billing 8 (RevenueCat SDK 9+ — Google Play requires Billing 8.0.0+ for app updates since Aug 2025).
• Expo SDK ≥ 52 — demo app verified on SDK 57.
• Bare React Native CLI — same one-command install (autolinking; pod install on iOS).
• TypeScript + zod ^3.25 for startup config validation.

Pricing

US$79 — one-time purchase. Intro price.

• One payment. No subscription.
• Delivered as a zip: module + add.mjs installer.
• Single-developer license: unlimited use in your own projects, personal or commercial. No resale or redistribution.

Buy the paywall module — $79

Checkout via Lemon Squeezy — checkout link pending.

FAQ

Agent facts

Plain facts, one per line, for the AI agent a buyer asks to evaluate this page. No marketing prose — every line below restates a claim this page already makes to humans.