> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zprotocol.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Subscription tiers

> ⚠️ **Not available at launch.** Subscription tiers are planned for a release after phase one. At launch, all paid access settles through x402 per-request, Stripe top-up to the unified credit pool, or MPP sessions. This page documents the planned subscription model so partners and integrators can plan ahead; the specifics below are subject to change before the feature ships.

Subscription tiers are Stripe-billed plans for developers and organizations who prefer a predictable monthly or annual relationship with Z over per-request settlement. This page describes how subscription billing is planned to relate to the unified credit pool, what is planned for each tier, and how Tier 4 access will work for subscription users when the feature ships.

## How subscription billing relates to credits

A subscription bills on a recurring cycle. Credits are applied to the unified credit pool at `invoice.paid`. Subscription entitlements are tracked separately from pay-as-you-go credits, and the debit priority is subscription entitlements first, then top-up balance, then live x402 per-request.

## Planned tiers

The planned tiers are Pro, Pro Plus, and Max, alongside the existing Free guest tier. Each tier bundles a monthly credit allowance, a welcome-credit grant on first paid subscription, and a credit-banking window during which unused credits carry over.

Welcome credits are a one-time grant on first paid subscription and expire 90 days after grant. On tier upgrade, the welcome-credit delta is applied (new grant minus unused balance).

Credit banking varies by tier: Pro carries no banking, Pro Plus banks credits for two months, and Max banks credits for three months.

The specific monthly credit allowances, included models, bonus rates, and pricing for each tier are maintained on the pricing pages in the dashboard. The categories above are stable; the specific numbers are confirmed at feature ship.

## Tier 4 is not on subscriptions

Tier 4 inference is not bundled into any subscription plan. Subscription users access Tier 4 by linking a wallet and paying through x402 or MPP. Tier 4 uses wallet-native settlement and a per-session wallet-signed AUP attestation at `/v1/handshake`; subscription credits cannot substitute for that wallet path.

## Top-up alongside a subscription

A subscription account can also fund pay-as-you-go credits via Stripe top-up. Top-up credits and subscription credits both reside in the unified pool. Subscription entitlements consume first; top-up credits consume after the subscription allowance is exhausted.

## OAuth and identity

Subscription accounts authenticate via OAuth: Google, Apple, or GitHub. The OAuth token is the identity binding. Z stores no name, email, or profile photo from the identity provider. Card data is held by Stripe, not by Z. Anonymity guarantees that apply across all paid tiers continue to apply to subscription accounts.

## Tier 4 access for subscription users

A subscription user who needs Tier 4 links a wallet to the account and proceeds through the standard Tier 4 handshake, which includes the AUP attestation per the Tier 4 attestation requirement. After wallet linkage, Tier 4 requests work from the same client code; payment for Tier 4 settles through the linked wallet via x402 or MPP. Tier 1 through 3 requests continue to debit the subscription's credit pool.

Wallet linkage does not change anything about the subscription billing or the OAuth identity binding.