TokenPass is the governed token layer for defined VCV service events. Tokens are consumed only when a client explicitly selects or authorizes a tokened service event.
No silent consumption. No multipliers. No ad hoc pricing.
Operating rule: TokenPass is charged by service event, not by ordinary page use, orientation reading, account review, or mode selection.
A TokenPass service event proceeds only after the selected event, applicable rate, and required authorization are confirmed.
Client Selection Controls TokenPass Use
This Rate Card identifies published TokenPass rates for defined VCV service events. When a client selects a service event from this Rate Card or another approved TokenPass selection interface, the client identifies the requested service and initiates the TokenPass purchase or authorization path for that selected event.
Selection initiates authorization. Confirmation completes authorization. Before the event proceeds, the client should be shown the selected service event, the applicable rate, and the authorization required.
No TokenPass service event should run through assumption, implication, or silent consumption. The power to purchase, authorize token use, decline the event, or request clarification belongs to the client.
TokenPass packs
Pack A
5,000 tokens
Pack B
15,000 tokens
Pack C
50,000 tokens
Pack selection is about operating volume. Pricing is stable because the unit is the service event.
Service-event pricing
Search
Search (internal library / governed index) — 500
Search (account-authorized materials only) — 750
Search (external retrieval via Search VCV) — 1,500
Verify claim vs page governing text — 500
Select this event
Active test selection. This link should open the TokenPass page with the selected event and rate displayed.
Verify claim vs one authorized file — 1,000
Verify claim vs multiple authorized files — 2,000
Record integrity check (required fields + constraints) — 750
Traceability log (sources used + unknowns register) — 750
Versioning: This is TokenPass Rate Card v1.2. Any future changes should be published as a new version to preserve operational clarity.
Pack-fit examples
5,000 supports ~2 major builds, or a focused Intelligence + Verify cycle.
15,000 supports an active workflow with buffer.
50,000 supports institutional volume across multiple positions or multiple candidates without frequent repurchase.
TokenPass is designed to be predictable. The client selects a service event; the system applies the published rate and proceeds only after the required authorization is confirmed.
TokenPass Continuity
Return to TokenPass Access
Use the QR code to return to this TokenPass page, review the operating rules, or continue account setup from another device before requesting a tokened VCV service event.