Overview
Glossary
The terms used throughout the Tanitar documentation.
| Term | Meaning |
|---|---|
| Account / tenant | One organizer's isolated space on the platform, identified by accountId. Everything you own, including players, tournaments, missions, ledger, keys and webhooks, is scoped to it. |
| Administrator | A person on your team who signs in to the Tanitar dashboard and acts on your tenant. |
| API key | A credential issued to your back-end systems, stored by Tanitar only as a digest, carrying capability scopes such as tournaments:mutate. |
| Award | A durable record that a player earned a badge, medal, trophy or organization badge (or an award of a kind you define), created once per trigger and settled through the grant path. Fulfilment, such as an on-chain mint or payout, is optional and separate. |
| Award kind | The category an award belongs to: six fixed system kinds (badge, medal, trophy and so on) plus any you define. A kind you define is never minted on chain. |
| Battle pass | A season with ordered tiers. XP moves a player through the tiers, and each tier can be claimed once for a reward. |
| Chest | An inventory item dropped by a mission or a milestone, opened once, paying out from a pinned drop table with a pity rule that guarantees a better drop after a set number of opens. |
| Control plane | Tenant Management: the single owner of accounts, plans, entitlements, API keys, Player-session credentials, webhooks and audit. |
| Dashboard | The Tanitar web application your administrators use to configure the tenant and run day-to-day operations. |
| Dead letter | A message whose consumer exhausted its retries. It is kept with its reason, and it is visible and replayable by your administrators or your integration. |
| Dedicated storage | A tenant whose data lives in a database you provide and operate, granted by a plan entitlement. The default is shared storage. |
| Tanitar operator | A member of Tanitar's own platform staff, acting through a separate, audited namespace. |
| Dispatcher | The process that leases due outbox and schedule records and publishes them to the message broker. |
| Entitlement | A plan-level permission, checked alongside the key's scopes on every governed request. |
| Grant | The single settlement primitive of the ledger: one request, one record, one balanced ledger effect and one published outcome that is either applied or rejected. |
| Idempotency key | A header you send (Idempotency-Key) that makes a mutation safe to retry. A repeat returns the original outcome. |
| Level curve | The XP needed for each level. You may set your own table and cap; otherwise a fixed default applies. |
| Player-session credential | A backend-only, single-purpose credential used to assert an authenticated external Player and create a short-lived Tanitar Player token. |
| Membership tier | A tier you define (for example free or gold) and grant to players; missions and rewards can be restricted to it. |
| Mission | An authored rule that counts player events over a period and pays XP and optional rewards on completion. |
| Operator grant | A reward you grant to a player directly, rather than through a mission, chest or tournament. It is recorded with the provenance operator-grant. |
| Organizer | The organization that owns a Tanitar account and runs the programme for its players. |
| Outbox | The table where a service writes the messages it must publish, in the same transaction as the change they describe. |
| Player | One of your end users. A player has no Tanitar account and signs in only with you. |
| Player context | A 15-minute signed token carrying the trusted account and Player identity. It is the only Player identity Tanitar services see. |
| Plane | A namespace and the principal it serves: the public API (/v1), the dashboard (/dashboard/v1) and the Player API (/player/v1). |
| Player API | The allowlisted /player/v1/* bearer surface a customer frontend calls with a short-lived Player token. |
| Scope | A capability an API key carries, such as rewards:read, checked on every governed route. |
| Self-test | One zero-value test-network transaction from a signer to itself, run on demand to prove a Web3 configuration can write. It is rate-limited and recorded. |
| Shop listing / order | A listing is something you sell for your own currency: an award, a code from a pool, or a manually fulfilled item. An order is one settled purchase of one or more listings, fulfilled, cancelled or reversed as a whole. |
| Web3 configuration | Your own test network, deployed contracts and signer for one chain, registered and verified before it is used. Without one, your tenant uses Tanitar's. |
| Webhook | A signed HTTPS delivery of a platform event to your endpoint, retried on a fixed ladder and replayable. |