Galactre
USD

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

Open Chat

GALACTRE / INTEGRATIONS

Connect with purpose.
Build on clear boundaries.

Explore the interfaces around Galactre: account access, credit payments, browser development and application workflows. See the requirements and current status before you connect.

01 / FIND THE RIGHT INTERFACE

Every connection,
with its scope explained.

Publication status describes implementation, not live health. Expand an entry for requirements, data flow and release boundaries.

9 integrations

DeveloperGalactre browser APIUse model discovery, session access, text generation and owned conversation history from the Galactre origin.Published contract
Requirements
A page served by Galactre, an eligible browser session and a current CSRF token for mutations. Model availability and limits are checked separately.
Data flow
Your message and bounded recent conversation context are processed for the requested response. History belongs to the current guest or account identity.
Release boundary
JSON or real SSE responses, request status and cancellation. Expiring server keys are available in API Access. Signed-in browser conversations support selected knowledge, calculator and current-time tools; server keys do not delegate those private sources. File/image input is not released.
Read the HTTP reference
IdentityIAM CentralConnect Galactre login and registration to the ecosystem identity service while retaining the Galactre account experience.Implemented account flow
Requirements
Configured Galactre identity client, approved callback and current account authorization. Use the Galactre login or registration form.
Data flow
The server verifies identity and access with the identity service. The browser uses a server-side session; service credentials are not supplied by chat JSON.
Release boundary
Authentication does not grant administration or access to another account’s history. Guest history does not automatically migrate after sign-in.
Understand account access
BillingQrisbillIssue credit checkout, verify payment outcomes and reconcile an owned invoice through authenticated Galactre billing.Implemented billing flow
Requirements
Configured payment integration, authenticated invoice owner and an issued checkout. Inspect sandbox/live status and the invoice amount before payment.
Data flow
Invoice/payment references, amount, currency and payment status are matched before credit is recorded. Signed notifications or authenticated status checks supply the outcome.
Release boundary
Prepaid monthly or annual subscription terms and one-time top-ups. Renewals require a new invoice; automatic debit, autonomous agent wallets and self-service reversals are not released. A reachable callback depends on deployment.
Read payment and reconciliation scope
DeveloperApplication workflowsUse model text as one reviewed step in code review, knowledge assistance or release preparation.Documented design patterns
Requirements
Use the published Galactre access contract. Your application supplies authorized context, retrieval, real tools and approval policy.
Data flow
Only the excerpts or task context your application explicitly supplies. GT chat does not automatically read repositories or private documents.
Release boundary
A blueprint is not a hosted automation connector. Native scheduling, multi-agent delegation and execution sandboxes are not exposed in this release.
Explore workflow blueprints
Agent ecosystemModel Context ProtocolA future standard interface could connect supported model and tool workflows through an explicit transport contract.Planned
Requirements
No public Galactre MCP URL, supported transport, authentication contract or tool catalog is published.
Data flow
No native MCP exchange is enabled by this website. Data and tool permissions must be specified before any connector is activated.
Release boundary
Do not infer tool execution or a working MCP endpoint from a roadmap description.
Current MCP publication status
Agent ecosystemOpenClawA dedicated connector is a product direction for applications that want Galactre inside their agent workflow.Planned
Requirements
No official extension, package, version compatibility matrix or native setup contract is published by this project.
Data flow
No OpenClaw account or repository is connected by visiting this page.
Release boundary
Generic browser examples do not establish a supported OpenClaw server connector or an OpenAI-compatible endpoint.
Current connector publication status
KnowledgeKnowledge sourcesSupply selected, authorized source excerpts to a Galactre conversation and review the answer against those sources.Available in signed-in chat
Requirements
Sign in, open Workspace in GT chat, and connect documents or add a private text source. Source access is checked again for each retrieval.
Data flow
Only the text submitted for the current task and bounded owned conversation context. No automatic ingestion, crawling or cross-chat search.
Release boundary
Signed-in chat supports private text sources and authorized document connections, with bounded lexical retrieval and source-version snapshots. Vector embeddings, binary file extraction and automatic cross-chat memory are not enabled.
Read context and history boundaries
Agent ecosystemVingolinVingolin is a separate assistant workspace product. A Galactre-native connector must have a verified contract before it is advertised as active.Native connector not published
Requirements
No released Galactre-specific connector package, setup flow or compatibility specification is published here.
Data flow
No Vingolin workspace, chat history or tools are connected by this page.
Release boundary
Membership in the same ecosystem does not by itself prove a working integration.
Review the current Galactre contract
Agent ecosystemAgent orchestration & skillsSigned-in chat can enable calculator and current-time tools per conversation. These bounded operations are separate from instruction recipes and multi-agent orchestration.Read-only tools available
Requirements
The administrator enables the tool service; the user enables each tool in the conversation. Tool names and arguments are validated server-side, with limits and recorded results.
Data flow
No delegated agent, installed skill or tool is activated by browsing the catalog.
Release boundary
Instruction recipes remain editable prompts. Shell execution, deployment, payment tools, arbitrary plugins and a managed multi-agent runtime are not enabled.
Explore current instruction recipes

02 / FROM INTERFACE TO WORKFLOW

Define the boundary.
Then verify the connection.

Start with a supported contract and test real outcomes before treating an integration as operational.

  1. 01

    Identify the supported interface

    Start with published Galactre routes and the integration’s current status. A product logo or ecosystem relationship is not an API contract.

  2. 02

    Define access and data

    Confirm identity, ownership, message limits and which context may be sent. Keep credentials outside browser snippets and model prompts.

  3. 03

    Implement the surrounding workflow

    Your application owns retrieval, tools, state, validation and approvals. Use completed model text as a proposed result, not an execution command.

  4. 04

    Verify success and recovery

    Test unavailable models, access failures, rate limits and uncertain outcomes. Payment integrations also need matching verification and reconciliation.

03 / KEEP OWNERSHIP EXPLICIT

Useful connections.
Reviewable responsibilities.

A model response cannot grant itself permission to read a repository, execute a command or spend funds.

Explore application blueprints

GT model service

The published catalog, text generation, session-based access and bounded owned conversation context.

Your application

User permissions, source retrieval, task state, real tools, artifact handling and an interface that explains outcomes.

Authorized reviewers and operators

Output validation, required approvals, operational evidence and recovery decisions for actions outside chat.

04 / INTEGRATION QUESTIONS

Connect with
fewer assumptions.

How should integrations handle version upgrades?

Read the live model catalog and choose an approved family default or an exact release. Test representative requests before changing a pinned ID. An unavailable pinned release returns an explicit error; integration code should surface it and let the operator choose a replacement.

Does an implemented integration mean the service is online?

No. Status describes the code/interface available in this release. Runtime availability depends on configured credentials, deployment, access, model availability and service health. This catalog is not a live uptime monitor.

Does choosing an integration connect an account?

No. Search, filters and disclosures only explain the integration. They do not grant permissions, send credentials, connect a repository, submit a prompt or create a payment.

Can I call Galactre from a backend with an API key?

Yes. Sign in to API Access, issue a model-scoped expiring key, and use the documented responses endpoint with a bearer key and Idempotency-Key. It uses your account balance and current entitlement. Do not forward browser cookies or private conversation connectors.

Does Galactre support tool execution or MCP today?

Signed-in browser conversations can enable bounded calculator and current-time tools. A model plans a validated operation, the tool service executes it, and GT uses the recorded result. Arbitrary tool execution and a public MCP transport are not released.

Can knowledge sources be read automatically?

Signed-in conversations retrieve bounded excerpts from sources you explicitly connect in Workspace. Access and source versions are checked on each retrieval. Automatic crawling, binary file extraction and cross-conversation memory are not enabled.

Where should I start?

Use Quickstart for the first conversation, API Access for permission boundaries and Developers for the current request/response contract. Code Examples provides copyable browser functions without automatically executing them.

START WITH THE CONTRACT

Build a useful connection.
Keep the outcome clear.