API key
An expiring, model-scoped credential for server integrations. Create, rotate or revoke your keys in this page after signing in. Plaintext appears once; a model ID alone does not grant access.
GALACTRE / API ACCESS
Explore Galactre as a guest, use your account or understand what another application needs. Keep identity, permissions and credentials clear from the first request.
Configuration is checked when this page loads. Access, quota and service health are checked again when you send a request.
01 / THREE DIFFERENT BOUNDARIES
A public conversation, an account session and a server integration have different requirements. Select a path to see what applies.
Use a limited GT Lunar conversation in the same browser. No API key is required. The service creates an eligible guest session and enforces its configured allowance.
Open guest chatUse a page on the Galactre origin with same-origin credentials.
Read chat_available, guest, limits and csrf_token from the session endpoint.
Use Lunar and honor the message length, reset and expiry returned for that session.
Supply only relevant text you are authorized to share. Guest access grants no private workspace or billing permissions.
Guest availability is checked at request time. A public catalog does not guarantee a session has remaining quota.
Sign in or register through Galactre. Account authentication is connected to IAM Central, while your chat and developer experience stay in Galactre.
Sign in to Galactre Create a Galactre accountUse the Galactre login or registration form and finish the required identity checks.
Discover the session and verify authenticated before using account-only functions.
Send a current CSRF token on mutations; never turn a browser cookie into an integration key.
Keep account conversations separate from guest history. Model access and usage still follow service policy.
Signing in does not migrate guest chats, activate planned models or grant administrative access.
Create a model-scoped server key from your signed-in API Access page. Use the bearer key with POST /api/v1/responses and an Idempotency-Key. Session endpoints remain exclusive to the Galactre browser.
Read the current access contractDo not copy a browser cookie or CSRF token into another application.
Do not assume an OpenAI-compatible endpoint or an official SDK has been published.
Before connecting a backend, require an explicitly supported Galactre credential and endpoint contract.
Choose the smallest set of model families, a short expiry and a separate key for each backend. Rotate or revoke keys from API Access.
Sign in to manage server keys. A model ID alone does not authorize a request.
02 / PERMISSION BOUNDARIES
Access follows the current identity, operation and service policy. A valid session or a known model ID does not grant every permission.
| Capability | Guest | Signed-in account | What to check |
|---|---|---|---|
| Read model catalog | Public | Public | Availability and published specifications; no execution permission. |
| Generate text | Lunar, within limits | Permitted available models | Session, CSRF, model availability and service policy are checked. |
| Read or delete history | Own guest session | Own account | Conversation IDs do not bypass ownership checks. |
| Credits and invoices | Sign-in required | Authenticated billing | Credit purchases do not unlock unavailable model capabilities. |
| Administrative configuration | No access | Separate authorization | An ordinary account session does not grant administrator permissions. |
| Knowledge and bounded tools | Sign-in required | Selected sources and tools | Calculator, current time and authorized private text retrieval; files, shell and deployments are not released. |
This matrix describes the current release. Server API key issuance is not a third active access tier.
03 / SET UP A BROWSER SESSION
The example reads session state from Galactre. Copying it does not run it, send a message, create an API key or make a purchase.
Use the origin serving your Galactre page. Production traffic requires HTTPS. Relative /api/v1 paths keep the request with that service.
Read the session endpoint with same-origin credentials. Inspect chat_available and authenticated/guest instead of inferring access from a cached UI label.
Use the returned csrf_token in X-CSRF-Token for POST requests. Keep it in memory and out of URLs, analytics, logs and public examples.
Refresh session state after sign-in, expiry or an access error. A token from an earlier session should not be reused blindly.
// Run only on a page served by Galactre. Calling this reads session state.
async function discoverGalactreAccess() {
const response = await fetch('/api/v1/chat/session', {
credentials: 'same-origin', cache: 'no-store'
});
const session = await response.json();
if (!response.ok || !session.chat_available || !session.csrf_token) {
throw new Error('GT chat is temporarily unavailable.');
}
// Keep this value in memory. Never print it or put it in a URL.
return {
authenticated: session.authenticated,
guest: session.guest,
limits: session.limits,
mutationHeaders: { 'X-CSRF-Token': session.csrf_token }
};
}
// This example does not send a message or purchase credits.04 / CREDENTIALS ARE NOT INTERCHANGEABLE
Keep secrets in their intended boundary. Public snippets, URLs and model prompts should never contain real credentials.
An expiring, model-scoped credential for server integrations. Create, rotate or revoke your keys in this page after signing in. Plaintext appears once; a model ID alone does not grant access.
The browser carries its server-managed session with same-origin requests. Keep it out of application configuration and shared scripts. Its presence alone does not prove model or billing access.
A session-bound value sent in X-CSRF-Token. It is not a provider credential, long-lived API key or permission to access another identity. Renew session state when the check fails.
Identifies saved chat history. Every read, continuation and deletion still checks ownership. Treat IDs and saved text as private to their current guest/account context.
05 / ACCESS TROUBLESHOOTING
Reading the error is more useful than repeatedly resubmitting. Preserve any unsent draft and distinguish denied access from an uncertain execution.
HTTP errors and retry guidanceThe model catalog is public. Generation additionally requires an eligible session, a current CSRF token, an available permitted model and remaining allowance. Check the session response and actual error.
Account and guest histories are separate. A guest conversation belongs to its original browser session and expiry. Signing in does not automatically move it into account history.
Check the operation: billing requires login, administration requires separate authorization and guest chat is restricted. Refresh the session through the normal flow and inspect the response rather than swapping credentials.
Fetch current session state from the Galactre origin with same-origin credentials. Reuse its current CSRF token only with that session. Inspect any earlier generation outcome before resending.
Respect Retry-After and the reported reset. Limits may apply to the session, IP and public service together. Creating another local label or refreshing the page does not grant additional allowance.
The example is intentionally a same-origin browser contract. Do not bypass cookie, origin or CSRF protections. Another backend uses an expiring server key from API Access with the separate responses endpoint.
06 / QUESTIONS, ANSWERED
No. Family defaults and exact release IDs use the same session, CSRF, allowance and permission checks. Guest access remains limited to available Lunar releases. A pinned ID never substitutes for authorization; retired or suspended releases are unavailable.
No browser API key is needed for eligible guest or signed-in chat. The browser uses a server session and CSRF protection. Guest chat has separate limits and currently supports Lunar.
Yes, after signing in. Create expiring keys for selected GT families, copy each key once, then rotate or revoke it from API Access. Fresh IAMC authorization and your account balance are checked for server requests.
No. Account authentication and administrative authorization are separate. Your account can only use operations permitted by its current service policy and ownership.
No. A verified purchase records credit according to billing policy. It does not bypass session checks, grant administrative permissions or enable planned models and tools.
The example contains no credentials. Do not add real cookies, tokens, private conversation IDs or user messages to a public snippet. Copying the example does not run it.
The Developers page documents the current routes, fields, completed responses, history operations, errors and limits. Quickstart provides first prompts and a copyable generation example.
YOUR NEXT STEP