Galactre
USD

Choose how catalog prices and estimates appear. Checkout and account records remain in IDR.

Open Chat

GALACTRE / AGENT IDENTITY

Every action needs
a clear 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

A session. An account.
A future automated actor.

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.

Current browser flow

A limited session, not an account.

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 access
  1. 01

    The browser checks the chat session and receives the current CSRF token and access limits.

  2. 02

    Generation is evaluated against guest eligibility, model availability and service limits.

  3. 03

    Conversation records belong to that guest context. Another guest or account cannot use the ID to bypass ownership.

  4. 04

    Guest history does not automatically migrate into account history when you sign in.

02 / BEFORE AN OPERATION IS ALLOWED

Know the caller.
Check the action.

Use these four questions when planning an application workflow. A successful login alone does not answer all of them.

Who is asking?

Distinguish a guest browser, signed-in account and future automated principal. A model name identifies a product family, not a user.

Whose resource is it?

Check the conversation, invoice or source owner. Knowing an identifier does not establish permission to read or change it.

Which action is allowed?

Generation, history deletion, billing reconciliation and administration have different requirements. Do not infer one grant from another.

What evidence remains?

Record safe request IDs and real outcomes. A generated explanation is not proof that a privileged operation executed.

03 / SIMILAR WORDS, DIFFERENT ROLES

An identifier
is not a permission.

Keep session state, request protection and resource identifiers distinct. Do not turn an implementation detail into an authority grant.

Browser session

Maintains the current guest or account context.

Keep session cookies in the browser; do not expose or reuse them as an agent credential.

CSRF token

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.

Conversation ID

Identifies a conversation for continuation, history or deletion.

The server still checks ownership. An ID is not a secret that grants access by itself.

GT model family

Selects an eligible model product such as Lunar.

It does not identify the caller or authorize tools, billing or administrator operations.

Server API key

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

Start with the
published session contract.

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.

JAVASCRIPT / SAME-ORIGIN SESSION INSPECTION
// 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

Clear access.
Explicit responsibility.

Is a GT release ID an agent identity credential?

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.

Does Galactre issue a public identity to every agent?

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.

Is a model family an agent identity?

No. Lunar, Stellar and Nebular identify GT model families. The caller’s identity, resource ownership and allowed actions must be established separately.

Can a guest read an account conversation with its ID?

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.

Can I reuse a browser session for a background agent?

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.

Does IAM Central login authorize deployments or payments?

No. Authentication does not authorize every operation. Real tool execution, deployment, payment approval and administration need the responsible application’s explicit permissions and controls.

Are DID, blockchain identity or cryptographic agent attestations active?

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

Connect the identity.
Bound the authority.