01
Define the use case
Start with the interaction, decision, or player-facing question the model should support—not a generic request for model access.
Loading page
Loading page content
ALTERED BRILLIANCE IS LIVE.ALTERED BRILLIANCE IS LIVE ON GOOGLE PLAY.Read the product story →
Codename-TGX1 is Kri Zek’s proprietary small language model for gaming-intelligence workflows. API access is currently designed around defined enterprise, studio, and research integrations—not a public self-serve key.
The API is the governed bridge between approved gaming context and a studio workflow. It does not grant ownership of player data or turn consent into a blanket permission.
Define which signals may leave the player surface, for what purpose, and for how long.
Translate authorised context into a scoped response tied to a concrete game or product question.
Use the result in an approved studio surface, including Majestic Helios workflows, while keeping review and human judgement visible.
The API programme is built for teams that can describe a responsible interaction surface: the data they are permitted to process, the player or operator experience they are improving, and the outcome they need to evaluate. Access is reviewed before credentials or integration details are shared.
01
Start with the interaction, decision, or player-facing question the model should support—not a generic request for model access.
02
Align on input provenance, consent, data handling, evaluation criteria, and the product surface that will receive the output.
03
Receive an integration plan, access path, and commercial proposal matched to the agreed work.
There is no self-serve checkout or generic key issuance. The published B2D API unit price is paired with a scoped review of the intended use, deployment shape, support level, and data boundary.
The current published unit price for specialised gaming-intelligence usage. Access, documentation, and commercial terms remain specific to the approved integration.
For a bounded feasibility question, a defined evaluation set, and a clear success criterion.
For a production integration where usage, support, deployment shape, and data governance are defined together.
For a research or institutional programme that needs a separate methodology, consent, and publication boundary.
Only bring data you are authorised to process. The access review should make provenance and consent explicit before any integration begins.
Define what the product needs to make legible, how a result will be reviewed, and where human judgement remains necessary.
Credentials, schemas, and deployment guidance are released through an approved integration plan rather than a generic sign-up form.
Usage, support, delivery, confidentiality, and data responsibilities belong in the same written scope as the price.
For approved integrations, Codename-TGX1 can provide scoped, structured context derived from gameplay evidence a player is authorised to share. The goal is a better question inside the development loop, not an unrestricted feed of player data.
Agree the design or research question before data moves.
Expose only the fields and time window required for that purpose.
Keep outputs attached to human decisions in Majestic Helios or another approved surface.
Credentials, schemas, retention, support, and pricing follow the written integration scope.
Tell us what your studio, platform, or research team needs to understand. We will respond with the appropriate access and pricing path once the scope is clear.
Integration starts with a defined purpose, bounded data, and a reviewable delivery path.