GT model service
The published catalog, text generation, session-based access and bounded owned conversation context.
GALACTRE / INTEGRATIONS
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
Publication status describes implementation, not live health. Expand an entry for requirements, data flow and release boundaries.
9 integrations
Try a different search, category or availability filter.
02 / FROM INTERFACE TO WORKFLOW
Start with a supported contract and test real outcomes before treating an integration as operational.
Start with published Galactre routes and the integration’s current status. A product logo or ecosystem relationship is not an API contract.
Confirm identity, ownership, message limits and which context may be sent. Keep credentials outside browser snippets and model prompts.
Your application owns retrieval, tools, state, validation and approvals. Use completed model text as a proposed result, not an execution command.
Test unavailable models, access failures, rate limits and uncertain outcomes. Payment integrations also need matching verification and reconciliation.
03 / KEEP OWNERSHIP EXPLICIT
A model response cannot grant itself permission to read a repository, execute a command or spend funds.
Explore application blueprintsThe published catalog, text generation, session-based access and bounded owned conversation context.
User permissions, source retrieval, task state, real tools, artifact handling and an interface that explains outcomes.
Output validation, required approvals, operational evidence and recovery decisions for actions outside chat.
04 / INTEGRATION QUESTIONS
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.
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.
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.
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.
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.
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.
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