Who is asking?
Distinguish a guest browser, signed-in account and future automated principal. A model name identifies a product family, not a user.
GALACTRE / AGENT IDENTITY
Understand who is asking, which resources belong to them and what they may do. Understand browser sessions, account-owned server keys and the additional boundaries an automated agent would need.
01 / DISTINGUISH THE PRINCIPAL
These are different access paths with different responsibilities. Browser sessions and account-owned server keys are available. Independent delegated agent identities remain a separate product boundary.
Eligible visitors can use a bounded Lunar conversation without signing in. The server establishes a browser guest session and applies the configured limits.
A guest session does not grant billing, administrator access, external tools or access to private workspace resources.
Explore guest accessThe browser checks the chat session and receives the current CSRF token and access limits.
Generation is evaluated against guest eligibility, model availability and service limits.
Conversation records belong to that guest context. Another guest or account cannot use the ID to bypass ownership.
Guest history does not automatically migrate into account history when you sign in.
Galactre login and registration connect to IAM Central. The browser uses a server-side application session; authentication and permission checks remain separate.
Shared ecosystem identity does not merge product data or grant access to another user’s conversations.
Read account access boundariesSign in through the Galactre account flow and return through the configured callback.
The server establishes the application session. Browser code does not supply service credentials in chat JSON.
Conversation access is checked against the current owner. Invoice access is checked against the authenticated billing owner.
Model eligibility and administrative permission are independent checks. An account does not receive every capability by signing in.
A future automated agent needs an authenticated identity, a responsible owner, bounded permissions and a supported execution contract. A display name or model family is not that identity.
Account-owned server keys support text responses with family scopes, expiry and current IAMC entitlement. A separate agent registry, delegated agent identity, DID attestation and MCP identity contract are not released.
Review workflow responsibilitiesIdentify the application owner and the principal responsible for each task.
Define explicit data permissions, allowed operations, budgets, duration and approval requirements.
Use only a released credential and endpoint contract. Never copy browser cookies or CSRF tokens into a background agent.
Record task outcomes, revocation and recovery evidence before treating an agent as an operational actor.
02 / BEFORE AN OPERATION IS ALLOWED
Use these four questions when planning an application workflow. A successful login alone does not answer all of them.
Distinguish a guest browser, signed-in account and future automated principal. A model name identifies a product family, not a user.
Check the conversation, invoice or source owner. Knowing an identifier does not establish permission to read or change it.
Generation, history deletion, billing reconciliation and administration have different requirements. Do not infer one grant from another.
Record safe request IDs and real outcomes. A generated explanation is not proof that a privileged operation executed.
03 / SIMILAR WORDS, DIFFERENT ROLES
Keep session state, request protection and resource identifiers distinct. Do not turn an implementation detail into an authority grant.
Maintains the current guest or account context.
Keep session cookies in the browser; do not expose or reuse them as an agent credential.
Protects supported browser mutations within the current session.
It is not an API key, user identity or permission grant. Obtain the current token through the session flow.
Identifies a conversation for continuation, history or deletion.
The server still checks ownership. An ID is not a secret that grants access by itself.
Selects an eligible model product such as Lunar.
It does not identify the caller or authorize tools, billing or administrator operations.
Authenticates a server application acting for the key owner.
Issue, rotate or revoke in API Access. Family scope, expiry, balance and fresh owner entitlement apply. It does not create an independent agent identity or inherit private knowledge sources.
04 / INSPECT THE CURRENT BROWSER CONTEXT
This example reports access flags from the current browser session. It does not grant an agent credential or administration. Copying the code does not execute it.
// Run only from a page on the Galactre origin.
// This example is displayed, never executed by this guide.
async function inspectGalactreAccess() {
const response = await fetch('/api/v1/chat/session', {
method: 'GET',
credentials: 'same-origin',
headers: { Accept: 'application/json' }
});
if (!response.ok) throw new Error('Session check failed: ' + response.status);
const session = await response.json();
return {
authenticated: session.authenticated === true,
guest: session.guest === true,
chatAvailable: session.chat_available === true,
limits: session.limits ?? null
};
}
// Keep the separately returned CSRF token within the browser flow.
// Do not log credentials or treat these flags as an admin grant.05 / IDENTITY QUESTIONS
No. A GT version identifies a published model product configuration. It does not identify a human or agent principal and cannot authorize tools, payments or workspace access. Keep model selection and principal permissions separate.
No. The current public interface supports guest and signed-in browser sessions. A native agent registry, delegated agent credential and public identity attestation service are not released.
No. Lunar, Stellar and Nebular identify GT model families. The caller’s identity, resource ownership and allowed actions must be established separately.
No. Conversation routes check ownership. An inaccessible or missing conversation must be handled through the documented error contract; a conversation ID does not bypass access checks.
Keep cookies and CSRF in the browser. Issue a dedicated expiring server key from API Access and call the responses API with an Idempotency-Key. This acts within its owner’s model scopes and balance; it grants no private knowledge delegation or privileged tools.
No. Authentication does not authorize every operation. Real tool execution, deployment, payment approval and administration need the responsible application’s explicit permissions and controls.
No such public contract or verification endpoint is published by this release. This guide does not create a wallet, register an on-chain identity or certify an agent.
BUILD FROM THE CURRENT CONTRACT