X, Grok, and Cursor Subscription Guide: Bot Access, Costs, and Account Unification

Choose the Bundle by the Access You Need

If Grok Bot is your reason for considering the X, Grok, and Cursor subscription, start with Premium or above. Plus costs $8 per month at the official USD list rate, but it does not include Bot. A lower subscription price is not useful if it omits the feature you need.

The following official USD rates were checked on October 16, 2026. They exclude taxes. Annual amounts are total yearly charges, not the amount billed each month. Confirm your account's actual checkout, regional availability, and billing terms before paying.

The public pricing page and subscription pricing documentation distinguish these plans and charges. The usage multiples are not guaranteed message counts. Different products and requests consume allowance differently.

For a short introduction, the official subscription overview video accompanies this guide. The steps below are proposed checks for readers, not an account migration we performed.

Understand the Weekly Pool and Extra Charges

The key budgeting distinction is one shared allowance, not separate allowances you can add together. Under the weekly usage rules, eligible first-party Grok and Cursor activity draws from the same weekly seat pool. Grok Bot uses that seat allowance too; it does not arrive with an independent bonus quota.

Imagine alternating Cursor coding work with Bot research. Eligible activity in either product reduces the same remaining allowance, and different products draw at different rates. A heavy coding week can therefore affect what remains for Bot. Read the actual next-reset information in your account rather than assuming every allowance renews on Monday.

API access is not prepaid API usage. Likewise, choosing a third-party model in Cursor does not make its requests included just because Cursor is part of the bundle. Inspect the model and charging route before a substantial session.

For teams, each seat has its own weekly pool, while the team shares the additional prepaid balance. That is different from everyone sharing one included weekly allowance. Check both the relevant seat and the paid balance when explaining a usage limit.

Compare the Bill Before Leaving a Legacy Plan

Switching is optional. An existing legacy plan continues unless you change or cancel it, so you do not need to merge accounts merely to investigate the offer. Cursor's legacy-plan documentation describes a different allowance structure: two monthly pools for Cursor Models and Other Models, compared with the new weekly first-party pool and separately paid third-party usage.

As price comparisons, legacy Pro at $20 versus Premium at $30, Pro Plus at $60 versus Super at $100, and Ultra at $200 versus Ultra at $200 are useful starting points. They are not identical feature bundles. An unchanged headline price can still produce a different bill when your model mix changes.

This is a worksheet, not a savings estimate. Leave uncertain usage costs unresolved rather than inventing a favorable total. Compare an ordinary week and a busy week, especially if you rely heavily on third-party models. Decide whether the access gained justifies the changed allowance structure before making a permanent merge.

Check Account Identities and Eligibility First

Write down the exact Cursor, Grok, and X identities you intend to include. For each, record whether it is personal or organization-managed, its billing merchant, renewal date, and any past-due invoice. Keep receipts available without sharing passwords or authentication codes.

Emails do not have to match. Conversely, a familiar email is not proof that you selected the intended personal account or workspace. If the linking screen shows a work identity when you intended a personal subscription, stop before confirmation or checkout and correct the sign-in.

The eligibility rules impose several boundaries:

• Personal and team accounts cannot be merged together.
• Organization-managed or affiliated X accounts cannot be added.
• A personal X account can link to only one Grok account.
• Past-due invoices must be paid before proceeding.
• Enterprise is not a general self-service path. Cursor Enterprise customers without Grok can ask their account team; combining existing enterprise accounts on both sides is not yet supported.

Do not create workaround accounts to bypass those restrictions. Resolve the actual account situation first. Most importantly, unification is permanent and cannot be undone, including by support. The preflight checks are reversible; the completed merge is not. If you are uncertain which identity should remain primary, postpone the purchase decision until you understand the choice shown.

Unify Eligible Personal Accounts on the Web

If you already pay for Cursor and want it included, start from the Cursor Unify page. The account-unification instructions explain that starting from X does not include Cursor. Existing paid mobile switching flows redirect to the web.

1. Sign in to the intended paid Cursor account. Recheck personal or workspace identity before beginning.
2. Start the unification flow. Use Get started where offered and inspect the accounts selected for inclusion.
3. Link the intended Grok account. Verify the identity displayed rather than relying on an already-open browser session.
4. Add your eligible personal X account if wanted. Do not include an organization-managed identity.
5. Select the primary account where the flow offers that choice. Review the resulting account selection before continuing.
6. Review the plan and checkout. Check Bot eligibility, monthly versus annual billing, taxes, and the accounts whose old subscriptions are included.
7. Confirm only after accepting permanence and the immediate billing change. Complete checkout yourself; stop if any identity or charge is wrong.

The completed flow makes the account unification permanent and starts the new billing cycle immediately. New checkout charges the full selected price; an old subscription's eligible refund is handled separately, not deducted as an assumed checkout credit.

After unification, use the Grok dashboard for management. Treat automatic top-up as a separate spending decision, not a required recommendation. Only the selected eligible old subscriptions are part of the switch; accounts you did not include remain outside it.

Check Refunds and Renewals by Merchant

Account unification, subscription cancellation, and refund approval are different events. The invoice and refund rules vary by merchant, so inspect the original purchase route even if you now use only an Android phone.

Save evidence of the new invoice and each relevant old renewal status. A refund request is not a refund approval, and there is no guaranteed arrival time stated here. Reconcile the original payment method rather than expecting new-plan credit.

If an old subscription still shows a future renewal, identify its merchant and account before acting. Canceling renewal is not the same as undoing the permanent account merge. Likewise, removing access or closing an app does not establish that a store subscription stopped. Verify the actual subscription status instead of relying solely on a successful new checkout.

Verify Access, Usage, and Paid Spending Controls

After switching, inspect the dashboard for the intended account or workspace, selected plan, seat, renewal information, weekly usage, and next reset. Check linked X benefits under the intended identity. Premium, Super, and Ultra provide Bot eligibility on the new subscription; Plus does not.

For Bot, inspect an existing conversation or make one small, non-sensitive request that fits its documented scope. Check the resulting work, not just whether the interface opens. If access is blocked, first verify plan entitlement, signed-in identity, selected workspace, and remaining allowance. Do not buy another plan or attempt another merge merely because the first screen looks wrong.

The spending-cap documentation distinguishes monthly paid Additional Usage controls from the subscription itself. Review the cap, remaining prepaid balance, and automatic top-up setting. A cap does not reduce the subscription fee, replenish the included weekly pool, or cancel renewal. Keep those controls separate when deciding how much paid activity to allow.

If a charge or entitlement remains unexplained, contact support with the relevant account identifiers, invoice references, merchant, and the discrepancy shown. Redact sensitive payment information. Resolve missing access and old renewal questions independently: one may be an account-selection problem while the other belongs to an app store.

Keep Cloud-Agent Billing Separate From Android Actions

Grok Bot performs task work on a cloud computer. Its subscription entitlement does not establish Android SIM calling or universal control of phone settings. A cloud research result and an event saved in your Android calendar are different outcomes. Can Grok Bot Make Phone Calls on Android? Apps, Voice, and Dialing explains the phone-specific distinction.

FoneClaw is our independent Android phone agent, not part of The X Subscription. A compatible configured model plans while enabled tools act under actual permissions and approval settings. For a supported calendar task, inspect the saved event, date, and time rather than treating a response as completion. Capability differs by edition and enabled tools; our FoneClaw Features page describes the scope.

We offer a free default model, with optional compatible provider APIs billed independently. A consumer Grok subscription does not pay those API charges. Connect an AI Model API to FoneClaw: Text, Images, and Android Tools covers configuration, while AI Agent Sandbox vs Android Permissions: Three Boundaries That Matter explains why cloud access does not automatically grant phone authority.