API-first · Agent-native · No revenue tax

In-app subscriptions, run by your AI agent.

One REST call to normalized entitlements, with store-specific purchase-verification endpoints. Your agent configures Tierux over MCP; Google Play Console and App Store Connect steps remain manual. No client API key. Apple App Store support is implemented with limitations — see platform support.

Read the docs 
# server-side call
curl https://tierux.com/api/v1/entitlements/$USER_ID \
  -H "Authorization: Bearer $KEY"
# → { "pro": { "active": true, "expires": "2026-07-01" } }
Server-side verified
Raw tokens never stored
No client API key
Encrypted token vault
Watch an agent configure Tierux
claude code · tierux mcp 
▸ Add a $9.99 Pro monthly subscription, then build the paywall.

Agent → Tierux MCP
create_project(name: "My App") → app_xxx                       ✓
create_play_product(productId: "pro_monthly", billingPeriod: "P1M",
  price: "9.99", currency: "USD", appId: "app_xxx")                  ✓
create_product_mapping(productId: "pro_monthly", entitlementId: "pro",
  productType: "subscription", appId: "app_xxx")                     ✓
create_paywall(id: "pro", theme: "auto", accent: "#7c3aed", badge: "PRO",
  headline: "Unlock Pro", subtitle: "Everything you need", features: ["Unlimited access"],
  packages: [{ id: "monthly", productId: "pro_monthly", label: "Monthly", price: "$9.99",
    sub: "per month", type: "subscription", on: true }], recommended: "monthly",
  ctaSub: "Subscribe", ctaOneTime: "Buy now", localizations: {}, appId: "app_xxx")  ✓ preview ↗

# From your backend — verify a purchase over REST:
POST /api/v1/purchases/google-play/verify   ✓
→ { "active": true, "entitlement": "pro" }
Two ways in
Building an app?

Ship entitlements today

One REST call to entitlements, drop-in paywalls, and server-side verification for Google Play and Apple. Start free — your agent configures the Tierux side over MCP. Apple App Store support is implemented with limitations — see platform support.

Explore for developers →
Evaluating at scale?

See what you'd save

Run the numbers against a 1%-of-revenue incumbent, plan a migration off RevenueCat or Adapty, and review the security architecture — then talk to the team.

See the enterprise case →
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 purchase and entitlement path.
Pricing
Free
$0
Unlimited apps · 1 paywall · Unlimited users. No credit card.
Pro
$39 /mo
Unlimited apps, paywalls, and users. Flat monthly fee.
Scale
$199 /mo
Everything in Pro + lifecycle sync, integrations & priority support.
See full pricing →

No revenue tax — ever.

Others take ~1% of your revenue forever. We charge a flat fee per active subscriber — your effective rate falls as you grow. At $100k MRR, 1% is $1,000/mo. At Tierux Pro + 10k subscribers, you pay $309/mo.

Why teams pick Tierux
Security-first
Google Play purchases are verified through Google's Android Publisher API. Apple transactions use signed-JWS and certificate-chain validation, while App Store Server Notifications drive lifecycle sync. Client results are untrusted. Raw purchase tokens are never stored or logged: we keep a SHA-256 hash for dedup and an AES-256-GCM encrypted copy. No Tierux API key ever ships inside your app. Read the security architecture →
Agent-native
Your AI agent configures Tierux products and paywalls over MCP, with a visual approval UI inside supported editors. Google Play Console and App Store Connect product and notification steps remain manual. Apple App Store support is implemented with limitations — see platform support.
No revenue tax
A flat fee per active subscriber instead of a percentage of your revenue — deep Google Play coverage, with Apple App Store support implemented with limitations. See platform support. Your effective rate falls as you grow.

Four steps to configure Tierux.

Create a project, build your paywall, connect MCP, and verify a test purchase. Complete the required store-console steps before launch.

Tierux
MCP Setup
Step 1 of 4
Tierux
Dashboard
Status
—
○ checking…
Active Entitlements
—
As of right now
Verifications · 24h
—
Purchase checks today
Active Subscribers
—
Verifications — last 7 days
Purchase-verification calls per day
Entitlement status breakdown
Current distribution across all users
Your apps
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.
Tierux
Upgrade to continue

You've passed the Free plan limit

Your Free plan covers up to 500 active subscribers. You've grown beyond that — congratulations! Your subscribers keep their access and nothing on your end users' side is affected.

To get back into your dashboard, manage paywalls, and use the MCP tools, upgrade to a paid plan. Paid plans include 1,000 active subscribers, then +$30 per additional 1,000.

Copied!