One call — showPaywall("pro") — renders your paywall, runs the store purchase, and verifies it server-side. Your agent wires up products, paywall, and SDK over MCP. No billing code, no client API key.
▸ Add a Pro subscription with a 7-day trial, then build the paywall.Agent → Tierux MCPcreate_play_product(id: "pro_monthly", trial: "P7D") ✓create_paywall(template: "trial-led", products: ["pro_monthly"]) ✓ preview ↗generate_sdk_snippet(platform: "android") ✓# In your app — one line:
Tierux.showPaywall("pro") // renders · runs billing · verifies server-side
What you get
MCP-first setup
Add the MCP server to your agent once. No multi-screen dashboard to click through — the agent drives the whole integration.
One prompt, full setup
A single prompt connects your store, maps your products, builds your paywall, generates the SDK snippet, and runs a test purchase — each shown as a preview before anything is saved. Google Play and the App Store are both supported.
In-browser paywall builder
Design your paywall right in the wizard — packages, pricing, and copy — with a live phone preview. The config hands straight to your agent, which wires it up via create_paywall.
Server-side verification
Purchases are verified with the store and normalized into queryable entitlement state — gate features with one check. Payments are securely managed by Google.
Built-in troubleshooting
The common MCP connection failures — 401s, transport errors, gcloud auth, package mismatch — with fixes inline so you're never stuck.
Entitlement analytics
A dashboard with verifications over time and a live status breakdown — active, grace period, account hold, cancelled, expired.
Works in your editor
Claude Code, Codex, and Cursor. Every change arrives as a preview you approve before it commits — nothing happens behind your back.
How it works
1
Create project
Name your project and get your API key.
2
Build paywall
Design packages, pricing, and copy with a live phone preview.
3
Connect MCP
Add the MCP server to Claude Code, Codex, or Cursor.
4
Verify
Run a test purchase to confirm the integration end-to-end.
We're new, so no customer logos or invented metrics. What's real today: server-side verified purchases, raw tokens never stored, and an SDK you can read end-to-end.
Agent-native
Your AI agent drives the whole setup — products, paywalls, SDK snippets, Google Play config — over MCP, with a visual approval UI inside supported editors. No clicking through dashboards.
The wedge
AI-native, Android-native subscription infrastructure — now with iOS. The incumbents bolt Android and MCP on as an afterthought; we lead with both.
Four steps. The agent does the rest.
Create a project, build your paywall, connect the MCP, verify a test purchase — that's it.
Tierux
MCP Setup
Step 1 of 4
Your account
Free plan
YA
Tierux
Dashboard
Your account
Free plan
YA
Status
—
○ checking…
Active Entitlements
—
As of right now
Verifications · 24h
—
Purchase checks today
Verifications — last 7 days
Purchase-verification calls per day
Entitlement status breakdown
Current distribution across all users
Plan
Loading plan…
Open paywall builder in your agent
Copy the prompt below and paste it into Claude Code, Codex, or Cursor. Your agent will open the paywall builder via MCP and let you edit it interactively.