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.

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.

Vyra AI is metered by tokens: each plan includes a token allocation; usage above it moves to overage.

Add-ons

Global Add-ons (extra identity verifications), extra Vyra AI tokens, and Workflow Automation for Customer Onboarding. Compose exactly the stack you need.

Overage

Applies on two meters: the entity allowance (base-equivalent units) beyond the monthly pool, and Vyra AI tokens beyond the plan allocation. Usage past the bundle, at the published rate.

Enterprise

All tools, usage-based custom pricing under a negotiated rate card and SLA, enterprise-grade support. Carries a commitment: a contracted volume threshold and duration (term), with rates set against that committed volume.

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.

1 · Grace period

Default [7–14 days]: full access + renewal reminders.

2 · Restricted / read-only

Default next [30–60 days]: chargeable actions suspended; read-only access + data export retained (reactivation paywall).

3 · Dormant / archived

Access behind a reactivation paywall; data retained in archival storage, not deleted.

4 · Deletion

Only at end of legal/contractual retention, or on the controller's documented instruction with no legal hold, after a final export.

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.