> ## 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.

# Together AI

> Prepare a Together AI chat-model candidate and verify the endpoint, model identifier, and streaming connection probe.

Together AI documents a Chat Completions API that can be evaluated with Threetone's custom-model connection probe. Choose a model available to your provider account and preserve the exact identifier with the candidate configuration.

<Note>
  The probe makes a real model request. A successful result does not enable custom-model publication or conversation execution, which remain unavailable.
</Note>

## Candidate settings

| Threetone field | Candidate value |
| - | - |
| Server URL | `https://api.together.ai/v1` |
| Model ID | The exact Together AI chat-model identifier available to your account. |
| API Key | A workspace secret or Secret environment reference containing the provider API key. |

Use Together AI's current [compatibility reference](https://docs.together.ai/docs/inference/openai-compatibility) for the base URL and model naming. Model IDs use provider-specific names, commonly including a namespace. Do not substitute a display label or assume that similarly named models have the same capabilities.

## Test one configuration

<Steps>
  <Step title="Review model access">
    Confirm that the intended chat model is available, that the key can access it, and that a test request is authorized. The provider's image, embedding, or speech endpoints are separate from this text probe.
  </Step>

  <Step title="Configure the candidate">
    In **Custom LLM**, enter the base URL without `/chat/completions`, the model ID, and the secret reference. Environment references use production during the probe. Follow [the field workflow](/agents-platform/advanced/custom-models/overview).
  </Step>

  <Step title="Inspect the response">
    Use **Test connection** and record a safe result. Threetone requests streaming Chat Completions with `stream_options.include_usage: true` and requires assistant text in the stream. Model-specific parameter or response differences can still cause the probe to fail.
  </Step>
</Steps>

Check authentication, exact model access, provider capacity, and stream compatibility separately. Keep credential values out of error reports. Do not treat a successful provider playground request as a substitute for this probe's [endpoint contract](/agents-platform/advanced/custom-models/compatible-endpoints).

For durable review, create a complete server draft and read it back. Publication remains rejected for custom selection; [managed models](/overview/models) use a separate configuration path.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does provider support for tools verify agent tool execution?" id="together-ai-faq-tools">No. This connection probe verifies a text response. Tool schemas, tool authorization, and runtime execution require their own supported tests.</Accordion>
  <Accordion title="Can I omit the namespace from Model ID?" id="together-ai-faq-model">Use the exact identifier supplied by Together AI for the model. A shorter display label may not resolve to a callable model.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.