> For the complete documentation index, see [llms.txt](https://help.intangible.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.intangible.ai/teams-and-billing/plans-and-billing.md).
# Plans and billing
Free, Explorer, Business plans. Payment methods, multiple owners, credit packs, annual discounts.
Pick the tier by who is doing the work. Free lets you try the product, Explorer is for an individual creator, Business gives a team shared workspaces with pooled credits, and Enterprise covers custom-fit engagements at scale.
## Plan comparison
The authoritative, up-to-date per-feature matrix lives at [intangible.ai/pricing](https://www.intangible.ai/pricing). The matrix changes faster than these docs can, so the comparison isn't duplicated here.
A few points about the shape of each plan hold steady. Free is for trial and Explorer is single-seat. Business adds multi-seat team workspaces with credit pooling, and Enterprise is custom scope. Generate 3D Asset isn't available on Free, and upgrading to Explorer or Business unlocks it.
## The four tiers
### Free
Free is the trial tier. It includes:
* Enough credits to render a few dozen 1K image stills.
* Single user, personal workspace only.
* The canvas, Build, Compose and Visualize, and most features.
* No Generate 3D Asset (requires Explorer or Business).
* No multi-seat teams.
* No team workspaces.
Use Free to walk through [the first render in 20 minutes](/get-started/your-first-project.md) and try the product before committing.
### Explorer
Explorer is the individual creator tier. It includes everything in Free, plus:
* More credits per cycle.
* Full Generate 3D Asset capability.
* No multi-seat teams.
Explorer is right for solo agency creatives, freelancers, and creators producing client work without a team.
### Business
Business is the team tier. It includes everything in Explorer, plus:
* Multi-seat team workspaces with collaboration and credit pooling across the team.
* [Generate 3D Asset](/build/generate-3d-asset.md) (text/image/multi-view to mesh).
* Higher per-cycle credit allotments.
* Multiple billing owners and payment methods.
* Priority support.
### Enterprise
Enterprise is the custom tier for teams at scale, with pricing and feature scope handled directly with the Intangible team. It adds set design support, custom configuration and development engagements, and the elastic scaling that larger production pipelines need.
To reach the Intangible team, use the **Contact Us** action on the in-product subscription page or go through your account contact.
## Billing cycles
Intangible bills on one of two cycles:
* **Monthly** – billed each month, can cancel any month.
* **Annual** – billed once a year at a discount versus monthly. The exact discount varies; see [intangible.ai/pricing](https://www.intangible.ai/pricing) for current figures. You pay for the year up front, and the credits arrive month by month, one month's allowance at a time.
Annual is the right call when you know you're committing to the product for a quarter or more.
### The free trial
Each team gets one free trial with its first paid subscription. The trial applies to any plan, billed monthly or annually. A team with a past subscription gets no further trial, even on a different plan. A Free team that has never had a trial sees a banner above the plans, and the Explorer and Business buttons start the trial.
The trial is **prepended** to the billing cycle, not consumed from it:
* The trial starts at checkout.
* During the trial no invoice is generated, and the team gets a full month of its plan's credits, which expire when the trial ends.
* When the trial ends, Stripe generates the first invoice automatically, and the first paid month or year begins.
The trial is free time added before your first paid month or year, and your first paid period starts the day the trial ends.
### The trial covers one seat
Checkout states the one-seat limit before you pay: "Your free trial includes one seat. Adding seats ends the trial and starts billing." Adding a second seat during the trial ends it that day. A new billing period starts, every seat is charged at the full price, and nothing is prorated. The Seats section on the Team page warns you and shows the exact charge before you confirm. See [Adding seats during a free trial](/teams-and-billing/create-and-invite.md#adding-seats-during-a-free-trial).
**Upgrade only when a job needs it.**
Start free with Intangible
## Where billing lives in the app
The **Team Admin** page (`studio.intangible.ai/team/...`) has three tabs at the top:
* **Team** – members, roles, invites.
* **Subscription** – every plan on one page, in two sections. **Annual** sits on top with Explorer, Business and Enterprise; **Monthly** below it has Free, Explorer and Business. Each paid card says how it is billed and shows an approximate usage line, and annual cards show what you save.
* **Usage** – current cycle's credit balance, Purchased Credits balance, billing entry point.
The Usage tab is the in-product summary. Billing itself runs in Stripe. The Usage tab exposes a **Manage billing in Stripe** action, which opens the Stripe customer portal in a new tab for invoice history, card management, and downloads.
### Monthly Credits
Each cycle, the tier's allotment refills the Monthly Credits balance. **Monthly credits do not roll over.** The balance is capped at the monthly allocation, so an unspent month is not carried into the next one: use the credits or lose them at the cycle boundary. The Usage tab shows current usage as a progress bar (e.g. "0/1000") and the refill date in prose ("Your monthly credit balance will refill January 9 based on your business plan.").
### Purchased Credits
Top-ups bought via the Get Credits flow add to a separate Purchased Credits balance. Purchased credits **expire one year after purchase**. They survive the monthly cycle, which monthly credits do not, but they are not permanent. Monthly credits draw down first; purchased credits are spent only after the monthly bucket is empty.
## Reading the Usage page
The balance tells you what's left. The Usage page tells you where it went, which is the number you need when a project burns a month's credits in a week and nobody can say why.
Intangible has two usage views, and which one answers your question depends on whose spend you're chasing.
**Your own spend: My usage.** Open the profile menu at the top right and choose **Usage**. My usage shows what *you* have spent inside the team currently selected in the workspace switcher, so check the switcher first if the numbers look wrong. Every member has this.
**The whole team's spend: the Usage tab on Team Admin.** Open the team menu at the bottom left of the rail, then the **Usage** tab. The team Usage tab is Owner-only. Members do not see the tab at all, and a Member who reaches the page by switching teams gets a notice offering their own usage instead. See [Permissions](/teams-and-billing/permissions.md).
The team view answers a different question from your own. Beside the same net-credits donut, its headline cards are **Active members**, **Projects**, and **Credits / generation**. The **By member** table shows who spent what, with a last-activity date, and **By project** beside it splits the same spend by project wherever a generation can be traced to one. Click a member to open their own breakdown, the same shape as My usage but scoped to them.
Across the top, four filters set the window: **7D**, **30D**, **90D**, and **All time**.
Both views break the spend down the same way:
* **By category.** A donut of net credits used, split across Video, Image, 3D and Other. Messages to Intangible agents count under Other. This is the first place to look. Video is almost always the largest slice, and a category that's larger than you expected usually means someone is generating video where a still would have answered the question.
* **By headline number.** Three cards: **Generations**, **Projects**, and **Credits / generation**. The third is the useful one over time. A rising cost-per-generation means the team has drifted to more expensive models or higher resolutions.
* **By project.** Which projects consumed the credits.
* **By type.** A table of Category, Type, Credits and Generations, described in the product as what credits were used for: image, video, or 3D generation. Sort it by either Credits or Generations. The table puts the donut's numbers in a form you can read a total off.
* **By transaction.** A **Recent activity** table listing each charge with its date, what it was used for (such as Image generation, Video generation, 3D generation, Image edit or Agent prompt), the project it belongs to, the type, and the credit amount. Page through it with the Previous and Next controls, and export what you have loaded with the CSV download beside the heading.
Two panels report the balances themselves: **Monthly Credits** with the refill date and the plan allowance, and **Purchased Credits**, which are bought as credit packs and expire a year after purchase.
{% hint style="info" %}
If your team has Enterprise terms with Intangible, those terms supersede what this panel shows.
{% endhint %}
{% hint style="info" %}
A dash in the Project column means the charge has no project attached. That covers work done outside a project, and older charges from before spend was attributed at the point of the transaction. An unnamed project shows as "Untitled" with its project id rather than being merged with other untitled projects.
{% endhint %}
## Payment methods
Card management lives in Stripe via **Manage billing in Stripe** on the Usage tab. Adding or updating a card requires Owner permission. See [Permissions](/teams-and-billing/permissions.md).
## Auto top-up
Credit packs can buy themselves. Turn on auto top-up and pick which pack it should buy; when the balance runs low, that pack is purchased automatically so a render doesn't fail mid-session.
It has one setting: which pack, or **Off**. Set it in the **Auto top-up** panel on the Usage page, below Monthly Credits and Purchased Credits; picking a pack turns it on, and **Off** turns it off. Owners also get an **Auto top-up** switch on each card in the Buy One-Time Credits modal. Any pack can be the auto top-up pack. Once it is on, the panel names the pack and the balance it refills below, and after it has fired, when it last did.
Only the team Owner sees these controls, and only on a paid plan; Free teams don't get auto top-up.
### Auto top-up on Enterprise
On an Enterprise team with a signed contract, the Owner picks the pack from the same **Auto top-up** panel. The packs are priced in dollars, each labelled with the credits it buys, and the panel shows your rate per 1,000 credits. The rate is your contract rate or the standard rate, whichever is lower, read on the day the top-up runs, so the credits a pack buys can change with your contract. Picking a pack needs a card on file and a team billed in US dollars. The refill point comes from your contract, not from the 20% rule below; the panel shows it. On an annual contract it is lower, because the pool is a year's worth of credits.
When something blocks a pack it already holds, the panel says so: "Paused: no card on file. Add a card to resume." or "Paused: this pack isn't available at your current rate. Pick another pack." An Enterprise team on an evaluation, or one that otherwise can't pick a pack, sees "Need more credits? Contact your account manager." instead, with **Turn off** if an auto top-up is already on.
On the other plans, auto top-up fires at a fixed point, when your remaining credits fall below **20% of your ceiling**: your plan's monthly allowance plus any purchased credits you still hold. The allowance counts once for the team, not once per seat. Counting both buckets is deliberate: a team with monthly allowance still to spend has runway that a pack-only calculation would miss.
{% hint style="warning" %}
After **five consecutive failed charges**, auto top-up switches itself off. That is almost always an expired or declined card. Fix the card in Stripe, then turn auto top-up back on; it does not re-enable itself.
{% endhint %}
## Credit packs
When the monthly allotment runs short on a heavy project, a credit pack tops up without changing your tier. Packs are for teams on a plan: on a Free team, the Usage tab shows **See plans** instead of **Get Credits**, and running out of credits offers a plan. Credits a team already bought stay usable if it moves to Free. Buy packs from the same billing settings panel:
1. **Open Get Credits** from the Usage tab. The **Buy One-Time Credits** modal opens with the packs in one row: three cards at a time, the next one peeking, arrows below to scroll.
2. **Pick a pack.** Packs run from 1,000 to 20,000 credits. Each card shows its credits, its price and roughly how many images or seconds of video it buys.
3. **Click Buy** on that card, such as **Buy 5,000 credits**. Stripe Checkout opens; complete the payment.
4. **Wait for the credits to land.** The workspace balance updates as soon as the Stripe webhook fires.
There is no quantity stepper. To buy more, buy a larger pack or buy again.
Credit packs persist beyond the monthly cycle and are not cleared when it rolls over, though they do expire one year after purchase. The cycle's allotment is used first, and pack credits get used after the cycle's allotment runs out.
If a credit pack is refunded, its unspent credits come off the balance. Refunding a subscription payment doesn't change your credits.
On an Enterprise team, the owner sees packs priced in dollars at the team's contract rate, and each card shows how many credits it buys. A team only sees the cheaper of the contract packs and the standard ones.
A larger pack is useful when a campaign is about to start and you know you'll need a substantial budget over the next month.
{% hint style="info" %}
Credit packs are workspace-scoped. A pack purchased on a personal workspace doesn't subsidize a team workspace and vice-versa. Buy on the workspace where the spend will happen.
{% endhint %}
## Upgrades and downgrades
* **Upgrade**: takes effect immediately. The new tier's monthly allotment becomes available at the next cycle; new tier features unlock immediately.
* **Downgrade**: takes effect at the next billing cycle. The current cycle keeps the higher tier's features until it ends. Tier-gated features stop working at the cycle change.
Monthly credits don't accumulate across cycles. Whatever credit balance you have at downgrade is preserved into the new tier; only the per-cycle refill rate changes.
### Cancelling a monthly plan
When an Owner cancels a full-price monthly Explorer or Business plan from the Subscription tab, Studio first offers a discount to stay: "Before you go: 50% off your next invoice". **Keep my plan at 50% off** puts the discount on the next invoice (the first one after the trial, if you're in a trial), cancels nothing, and leaves your credits as they were. **Continue cancelling** carries on with the cancel as before; on Explorer that opens Stripe, where the cancel happens. A team gets the offer once. Annual plans, plans already discounted and plans already set to cancel or change don't see it.
If you downgrade from Business to a lower tier with active team workspaces, the team workspaces remain accessible to existing members, but no new invites can be sent until you re-upgrade.
## Deleting a team
An Owner deletes a team from the Team page: open the **⋯** menu (Team actions) beside **Team details**, then **Delete team**, then confirm. The team disappears from the app for everyone straight away, and there is no undo.
What happens to billing when you delete a team depends on the plan:
* **Self-serve plan (Explorer, Business).** The subscription is set to cancel at the end of the period you already paid for. You won't be invoiced again, and the remaining paid time is not refunded. The confirm dialog says so: "Deleting this team cancels its subscription at the end of the current billing period. You won't be charged again, and the remaining paid time is not refunded. This can't be undone."
* **Enterprise.** The delete is refused while the deal is live, and nothing changes. You see "This team is on an Enterprise plan. Contact your account executive to end the deal before deleting the team."
* **No subscription.** The dialog reads "Are you sure you want to delete this team? This can't be undone."
Your personal workspace can't be deleted.
## Limits and known issues
* **Plan changes don't refund partial cycles** for downgrades. If you downgrade mid-month, the remaining time on the higher tier is honored but no refund is issued.
## Related
* [intangible.ai/pricing](https://www.intangible.ai/pricing) – the current pricing matrix
* [Workspaces](/teams-and-billing/workspaces.md)
* [Create and invite](/teams-and-billing/create-and-invite.md)
* [Permissions](/teams-and-billing/permissions.md)
* [Credits and tokens](/learn-more/concepts/credits-and-tokens.md)
* [Resolution and cost](/visualize/resolution-and-cost.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.intangible.ai/teams-and-billing/plans-and-billing.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.