> ## Documentation Index > Fetch the complete documentation index at: https://docs.threetone.in/llms.txt > Use this file to discover all available pages before exploring further. # Endpoint compatibility > Review the supported custom-model probe format, URL shape, credential references, and provider compatibility. Check the endpoint's actual protocol rather than assuming compatibility from a provider or model name. The current Threetone probe supports Chat Completions only. | Setting | Current probe requirement | | - | - | | API type | `chat_completions`; Responses and WebSocket types are rejected by probe policy. | | Response | Streaming Chat Completions with `stream_options.include_usage: true` and a nonempty assistant text delta. | | URL | Public HTTPS API base URL, without credentials or a private-network destination. | | Model ID | A nonempty string without surrounding whitespace, at most 256 characters. | | API key | None when the endpoint needs no key, or a supported workspace secret or Secret environment reference. | | Request headers | Permitted literal or credential-reference headers; reserved and dynamic headers are rejected. | | API version and auth connection | Not supported by the current probe. | The streamed response must use SSE data with a nonempty assistant text delta. An ordinary JSON response or a stream containing only tool calls does not satisfy the current probe. For example, `https://models.example.com/v1` illustrates a base URL. It is not an operational Threetone endpoint. Review the provider's current Chat Completions documentation for the model identifier and response shape. The probe resolves environment references using the workspace's production environment. Review that value before testing; the probe does not select an environment from a future deployment. Recording pending for Inspect a custom-model connection probe. No playable video is available yet. ## Provider review Cloudflare Workers AI, Groq, Together AI, SambaNova, or a self-hosted endpoint may expose different authentication, routing, model, and parameter conventions. Select a provider only after checking the required base URL, available protocol, credential scope, rate limits, and data-processing terms. Provider compatibility must be demonstrated; it is not guaranteed by this list. Keep a controlled probe result with the endpoint configuration and model identity. Retest after changing the endpoint, credential reference, model ID, or headers. A previous success belongs to that earlier configuration. Screenshot pending for custom model endpoint. This illustration is not a product screenshot. ## Frequently asked questions No. The broader authoring schema includes alternatives that current executable probe policy rejects. Use the requirements above for that probe. No. It tests a bounded model request. Agent publication, tool behavior, voice processing, and live execution require separate support. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.