> ## Documentation Index
> Fetch the complete documentation index at: https://agnt.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Trial
> How the agntdata trial works — eligibility, credits, and the deploy gate.
agntdata offers a 7-day free trial on the **Build** and **Launch** plans so you can deploy and run real agents before committing to a subscription. The **Scale** plan is intentionally not trialable — it's our larger-customer tier.
The trial is org-scoped: one trial per organization, ever. It works the same regardless of how many workspaces you spin up underneath.
## How it works
On **Billing**, choose **Start trial** on Build or Launch. Stripe collects a card up front (no charge yet) and creates a subscription with a 7-day `trial_period_days`.
The trial grant lands as two `credit_transactions` rows — one to your data wallet, one to your AI wallet — sized for the plan you picked. The `trial_credit_grants` row enforces idempotency, so Stripe webhook retries can't double-credit you.
Trial users have full access to the platform: build agents, deploy them, run schedules, connect integrations. The deploy gate is satisfied while the trial is active.
On day 7 Stripe charges the plan's monthly price unless you cancel first. Converting upgrades the trial to a regular feature-plan subscription; canceling leaves the org with no active plan and the deploy gate kicks back in.
## What you get
The trial wallet sizes scale with the plan:
| Plan | Trial data credits | Trial AI credits | Workspaces | Agents |
| ------ | -------------------- | -------------------- | ---------- | ------ |
| Build | per the live catalog | per the live catalog | 1 | 3 |
| Launch | per the live catalog | per the live catalog | 3 | 15 |
The exact dollar amounts and per-plan caps are listed on [the **Billing** page in the dashboard](https://app.agntdata.dev/dashboard/billing) — that page is the source of truth and updates whenever the plan catalog changes.
## The deploy gate
Deploying an agent (moving it from draft to live on Anthropic's runtime) requires an **entitlement reason**. Three reasons unlock the gate:
| Reason | What it means |
| ---------------- | ------------------------------------------------------------------------ |
| `feature_plan` | The org has an active Build / Launch / Scale subscription. |
| `trial` | The org is in an active trial window. |
| `credit_package` | The org has an active credit package (legacy unlock — being phased out). |
If none of those is true, `POST /dashboard/agents/:id/deploy` returns a `402 DEPLOY_GATE_FAILED` response. The dashboard catches this and pops the trial upsell modal with a one-click **Start trial** action.
You can check entitlement programmatically via `GET /dashboard/billing/entitlement`. The response includes the trial's `daysRemaining` and the reason the gate is satisfied (or `none` if it isn't).
## During and after the trial
* **Credit consumption** — trial credits behave like purchased credits: they're spent first, never expire during the trial window, and aren't refunded if you convert.
* **Subscription credits** — once you convert, your plan's monthly allowance starts the next billing cycle. Any trial credits still sitting in your wallets stay available alongside the subscription allowance.
* **No conversion, no charge** — if you cancel before the 7 days run out, Stripe doesn't charge the card, and the trial credits are forfeited.
## Why trials are one-per-org
The `trial_credit_grants` table has `organization_id` as its primary key. That's the idempotency guarantee: a Stripe webhook retry or a manual re-trigger can't grant the trial twice. It also means an org that converts and later downgrades back to no-plan can't restart the trial — they're a paying customer at that point.
## Next steps
Data wallet vs. AI wallet, and how purchased credits work after the trial.
Where to watch trial credit burn in real time.
The trial covers every workspace in the org.