Galactre
USD

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

Open Chat

GALACTRE / PROTOCOL & PRODUCT NOTES

Understand the contract.
Build with confidence.

Follow the current scope of Galactre’s models, conversation interfaces and payment workflow. Understand what each change means for your application before you depend on it.

01 / KNOW THE CURRENT SCOPE

The detail behind
the interface.

Filter by area and open a note for behavior, boundaries and the next step. These notes do not represent a live health check or a complete historical changelog.

5 implementation notes

API & accessA session-based text conversation contractModel discovery, session checks and text generation have distinct access and request requirements.
  • Discover the public catalog with GET /api/v1/chat/models. Inspect browser access and the current CSRF token with GET /api/v1/chat/session.
  • Generation uses POST /api/v1/chat/generate with a message, family and optional owned conversation ID. Mutations require the browser session and CSRF protection.
  • Generation supports JSON or real SSE start, delta and completed events. Request status, cancellation and recovery are available. Accounts can issue, rotate and revoke model-scoped server keys. File/image input is not released.

What to check

Check the endpoint contract before adapting an example. Do not place server credentials in a browser request.

Read the HTTP reference
ModelsModel families have explicit availabilityLunar, Stellar and Nebular are presented as GT model families with individual lifecycle and availability information.
  • The Models page reads the public catalog and distinguishes available, unavailable and planned entries. A family name is not a promise that it can serve requests.
  • Guest access is limited to the eligible Lunar path. Account model access is checked separately.
  • Unpublished context limits, output limits or token rates are identified as not published. The evaluation guide does not invent benchmark scores.

What to check

Consult the current model profile for availability and published specifications instead of relying on this dated snapshot.

Inspect the current model catalog
API & accessConversation history remains owner-scopedHistory and continuation are separate from cross-chat memory, document retrieval and tool access.
  • The conversation list returns up to 30 recent owned records. A conversation detail returns up to 100 recent messages in chronological order.
  • Generation may continue an owned conversation using its ID. The model context is bounded; a stored transcript is not a promise that every message is sent to the model.
  • Deletion requires the current owner, a session and CSRF protection. It removes that conversation and its messages from the active store. Guest history does not automatically migrate after sign-in.

What to check

Handle missing or inaccessible conversations and require a deliberate confirmation before deletion in your own interface.

Read context and history guidance
BillingCredit purchases use verified invoice outcomesMonthly and annual prepaid plans, top-ups and verified model usage share a versioned pricing contract.
  • The public package guide reads the same credit catalog as invoice creation. Review the issued invoice and environment before paying.
  • A matching verified payment amount, currency and transaction are required before credit is recorded. Repeated notifications do not create a second credit allocation.
  • Monthly AI allowance expires at its period boundary; paid top-ups do not expire. Annual terms allocate allowance monthly. Renewals require a new invoice; no automatic debit is performed. Published GT input, output and cached-input tariffs settle verified usage with micro-rupiah precision. Uncertain usage stays reserved for review; autonomous agent wallets and self-service reversals are not released.

What to check

Use authenticated billing to inspect an owned invoice. An uncertain outcome requires status verification, not an immediate duplicate purchase.

Understand payment reconciliation
Guides & workflowsWorkflow guides separate reasoning from executionAgent blueprints, instruction recipes and ecosystem guides describe who supplies context, runs tools and verifies outcomes.
  • Instruction recipes can be copied or placed into a chat draft. They do not install a plugin, read a repository or execute a tool.
  • Integration and ecosystem pages identify implemented account/billing interfaces and native connectors that are not published. Listing a product does not connect it.
  • Community guidance includes a local feedback brief. It does not submit a support ticket or claim an active public forum.

What to check

Review the access and execution boundary of a workflow before treating a model proposal as an operational result.

Explore product responsibilities

02 / CURRENT INTERFACE REFERENCE

Keep the contract
close to your code.

Use the developer reference for the full fields and response examples. This summary identifies the interfaces your application should verify.

InterfaceCurrent contractIntegration handling
Model discoveryGET /api/v1/chat/modelsRead the current catalog; do not assume every named family is available.
Browser sessionGET /api/v1/chat/sessionInspect access, limits and CSRF state. Do not treat a session response as an administration grant.
Text generationPOST /api/v1/chat/generateUse session + CSRF. Handle blocked, failed and indeterminate outcomes without blind retries.
Conversation historyGET /api/v1/chat/conversationsExpect owner-scoped records. Use the documented detail and deletion routes.
Error handlingHTTP status + JSON errorHandle 419 CSRF mismatch, access failures, unavailable models and rate limits. Respect Retry-After when supplied.

Documented interface status is separate from service uptime. Check the HTTP reference for the full request and error contract.

03 / UNDERSTAND THE IMPACT

Different changes.
Different review needs.

Use this review guide when adopting a change. It is not a promise of a published support window or a version-retirement policy.

Additive changes

New fields, examples or optional capabilities should be reviewed against the current contract. Parse the documented fields and avoid depending on display text.

Contract changes

A required field, permission change or removed operation needs a compatibility review and explicit migration steps. No public deprecation window is committed by this release.

Operational changes

Model availability, quotas and payment configuration may change without changing an HTTP path. Check the current service response and the issued invoice.

04 / BEFORE YOU ADOPT A CHANGE

Review. Test.
Keep a recovery path.

Apply the checks that match your integration before relying on a changed interface.

Recheck the contract

Compare routes, fields, access requirements and error handling with the current developer reference.

Verify representative cases

Test success, access denial, quota limits, unavailable models and uncertain outcomes with non-sensitive inputs.

Review data and permissions

Confirm owner boundaries and keep real tool execution, deployment and payments behind their own authority.

Record evidence and recovery

Capture safe request IDs and observed behavior. Keep a rollback or reconciliation path appropriate to the change.

05 / UPDATE QUESTIONS

Read a note.
Know its limits.

Where can I find exact model releases?

The Models page now includes Versions & releases with current defaults, exact IDs and release notes from the live catalog. Product model versions are separate from HTTP contract versions, commercial revisions and application releases. No RSS or automatic update subscription is implied.

Is this a complete, versioned release history?

No. These are curated notes about the current implementation, reviewed for the date shown above. The model catalog publishes exact GT release IDs and current defaults. A separate application release archive and public announcement feed are not configured.

Does a note mean a service is currently healthy or production-ready?

No. Implementation notes describe the published scope. Availability still depends on deployment, credentials, model access, configuration and runtime health. This page is not an uptime dashboard or production certification.

Where should I check model availability?

Use the Models page or the public model discovery endpoint. A model can be planned or unavailable even when its family has documentation. This snapshot is not a live availability response.

Will an API change always come with a migration window?

No public support period, deprecation window or compatibility guarantee is committed by this release. Verify the current developer contract and test your integration before relying on a changed interface.

Can I subscribe to RSS, email or webhooks for updates?

A public RSS/Atom feed, email subscription and release webhook are not configured. This page does not collect an email address or pretend to subscribe you. Use the published guides and return here for implementation notes.

How can I report an integration regression?

Prepare a minimal non-sensitive reproduction with the operation, environment, expected result, actual result and a safe request ID. The Community page provides a local feedback brief; an official report submission channel has not been published.

CONTINUE WITH THE CURRENT CONTRACT

Build on what
you can verify.