Current access boundary
Tensor Cortex documentation covers a committed product contract and deployment-scoped pilot or private-alpha integration surface. Tensor Cortex has not announced a public production API or self-service signup. An approved deployment supplies its own base URL and scoped credentials.
Start with the job you need to do
The shortest reliable path is to choose the public page that owns the decision you are making. Product descriptions explain intent; the API reference defines the request boundary; Insights articles explain architectural responsibilities.
Implement
Gateway API reference
Review authentication, logical profiles, chat completions, streaming, response metadata, and safe error behavior.
Read the API reference →Evaluate
Product overview
Understand Workspace, Gateway, Control, policy-first routing, and the supported deployment direction.
Explore the product →Design
Architecture boundaries
Separate proxy, router, gateway, and control-plane responsibilities before choosing an implementation boundary.
Read the responsibility guide →Research
Tensor Cortex Insights
Use evidence-led technical guides with primary-source packets, original artifacts, and explicit editorial inference.
Browse Insights →Documentation map
| Reader job | Authoritative public page | Current boundary |
|---|---|---|
| Integrate an approved application | Gateway API reference | Use the base URL and scoped key supplied for that deployment. |
| Evaluate the product boundary | Product overview | A capability description is not a release or availability statement. |
| Compare infrastructure responsibilities | Insights | Editorial frameworks identify inference and cite current sources. |
| Review public-site data handling | Privacy policy | Product or customer deployment terms require a separate agreement. |
Release and offering semantics
Tensor Cortex uses one product contract across planned delivery models, while availability and operating responsibility remain separate questions. Public documentation therefore distinguishes the interface from the service that may eventually expose it.
- Self-Managed and dedicated pilot paths use a single-tenant installation boundary. The current product remains an in-progress release candidate pending real design-partner validation and release hardening.
- Tensor Cortex Cloud is the shared, Tensor Cortex-managed offering direction. Private-alpha engineering evidence does not make it a generally available service.
- Public Gateway access is not announced. Do not treat a hostname, example URL, API shape, or roadmap entry as an active endpoint.
Need deployment-scoped integration details?
Use the pilot request to discuss a reviewed environment and its exact support boundary.