> For the complete documentation index, see [llms.txt](https://doc.youverify.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.youverify.co/get-started/plans-entitlements-and-billing.md).

# Plans, Entitlements and Billing

The billing model mirrors the product model: the metered action is **Add Entity**. Each plan includes a prepaid **entity allowance** (a pooled, base-equivalent figure) plus a Vyra AI token allocation. Live numbers and the full comparison are on the [pricing page](https://www.youverify.co/en/pricing).

> Everything essential is included from day one. Deepfake-resistant liveness, document capture, PEP and adverse-media screening are **bundled, not separate fees**. Turn capabilities on or off as you grow.

| Plan                | Entity allowance (base-equiv.) | Example mix (base / relationship)           | Vyra AI tokens |
| ------------------- | ------------------------------ | ------------------------------------------- | -------------- |
| Scale with Vyra AI  | up to 500 units                | 500 base, or 1,000 relationship, or a mix   | 4 million      |
| Growth with Vyra AI | up to 1,200 units              | 1,200 base, or 2,400 relationship, or a mix | 11 million     |
| Pro with Vyra AI    | up to 2,000 units              | 2,000 base, or 4,000 relationship, or a mix | 20 million     |
| Enterprise          | unlimited                      | custom                                      | custom         |

> **Base vs Relationship pricing**. One pooled allowance, but a Base Entity (fully diligenced) costs a full unit and a **Relationship Entity** (UBO / downstream, thin at creation) costs a fraction, illustrated here as 1 base = 2 relationship. **Anti-gaming rule**: if a relationship entity is later promoted to full verification, it then consumes a full base unit, so you can't get full diligence at the relationship rate.

{% hint style="info" %}
Vyra AI is metered by **tokens**: each plan includes a token allocation; usage above it moves to overage.
{% endhint %}

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><h4>Add-ons</h4></td><td>Global Add-ons (extra identity verifications), extra Vyra AI tokens, and Workflow Automation for Customer Onboarding. Compose exactly the stack you need.</td></tr><tr><td><h4>Overage</h4></td><td>Applies on two meters: the <strong>entity allowance</strong> (base-equivalent units) beyond the monthly pool, and <strong>Vyra AI tokens</strong> beyond the plan allocation. Usage past the bundle, at the published rate.</td></tr><tr><td><h4>Enterprise</h4></td><td>All tools, usage-based custom pricing under a negotiated rate card and SLA, enterprise-grade support. Carries a <strong>commitment</strong>: a contracted <strong>volume threshold</strong> and <strong>duration</strong> (term), with rates set against that committed volume.</td></tr></tbody></table>

> **Single-tool usage is Enterprise-only**. Subscription plans cover the end-to-end workflow. To consume just one capability in isolation (e.g. only government-data verification, or only the SDK), you need an **Enterprise agreement with volume pricing** for that capability.

### Lapsed subscriptions: suspension & data retention

Access and data are handled separately. Access is a commercial lever; the data is **compliance data**, governed by record-keeping law and the customer agreement, not payment status. Cowork does **NOT** delete compliance records just because billing stops.

<table data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td><h4>1 · Grace period</h4><p>Default <mark style="color:$primary;"><code>[7–14 days]</code></mark>: full access + renewal reminders.</p></td></tr><tr><td><h4>2 · Restricted / read-only</h4><p>Default next <mark style="color:$primary;"><code>[30–60 days]</code></mark>: chargeable actions suspended; read-only access + data export retained (reactivation paywall).</p></td></tr><tr><td><h4>3 · Dormant / archived</h4><p>Access behind a reactivation paywall; data retained in archival storage, not deleted.</p></td></tr><tr><td><h4>4 · Deletion</h4><p>Only at end of legal/contractual retention, or on the controller's documented instruction with no legal hold, after a final export.</p></td></tr></tbody></table>

> **Retention over deletion.** AML rules (FATF R.11 and most national laws) generally require KYC/CDD and transaction records to be kept ≥5 years after the relationship ends; the customer may be legally obliged to retain them.

#### What this means for an integrator?

If a capability is in these docs, your plan can use it; no check is a separately licensed product. The two quantities to plan capacity around are **new entities per month** and **Vyra AI tokens**. Create entities deliberately and reference them thereafter, and usage stays predictable.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.youverify.co/get-started/plans-entitlements-and-billing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.