Skip to main content

Choose models for a document or image assistant

Section: DOC-MA-model-controls#control-which-models-serve-a-request.

Choose a permitted model for the material the customer provides, then follow the request to a usable answer or an explicit selection failure. Start with named candidates whose availability your account supports; add a filter for the capability the task requires.

For an image question, require image input. For a long research thread, require a suitable context window and separately manage the actual history size. Price filters narrow known per-token catalog prices; they are not a total spending budget.

Recipe: answer with a model suited to the input​

Section: DOC-MA-model-controls#start-here.

Before starting, have an authenticated thread, the customer input and permitted model candidates for your account and data-handling requirements.

  1. Check the candidates against the accepted model rules and your provider/account availability.
  2. Choose the image or long-context filter that matches the actual request. Keep every required constraint when using a per-send filter.
  3. Send one representative request and retain its run ID. If no model is eligible, correct the selection error before another send.
  4. Follow the accepted run to its outcome and inspect the answer. A metadata match does not prove the provider honored the requested capability.
  5. Compare actual usage and result quality before using the same setup for more traffic.

Finished result: the application follows the selected candidates to a correlated answer or a selection/generation failure. Check that the answer meets the task's requirements, and do not infer zero cost from missing usage.

Use the worked recipes for a long research thread, a price-filtered summary or a structured task summary.

Step 1: select candidates accepted for the account​

Section: DOC-MA-model-controls#allowed-models.

Select candidates from the accepted model rules in the reference, then confirm their actual availability and suitability for your account.

For repeatable quality comparisons, name the model candidates explicitly. If you leave model selection unset, selection falls back to inherited settings and then the service default; that does not pin a particular model. Inspect the model that actually served the request when comparing quality or usage across runs.

Follow the candidates through validation and fallback​

Section: DOC-MA-model-controls#how-it-works.

Choose candidates that meet the customer’s input, capability and data-handling needs. Use the reference to investigate a rejected candidate or unexpected fallback.

If a fallback answers, inspect the actual returned model and outcome rather than assuming the first candidate served the request. An initial send failure and a later generation failure need different recovery; retain the response you actually received.

Upcoming recipe: summarize a document without hosted inference​

Status: Upcoming — not yet available.

Section: DOC-MA-model-controls#local-model-serving

Use this path when the document must remain on supported local infrastructure.

  1. Select a locally supported model with the required capability, capacity and suitable model-weight licence.
  2. Configure the local deployment and keep hosted fallback disabled for this workflow.
  3. Submit the authorized document and follow generation and structured-output validation when applicable.
  4. Inspect the result and accounting. If local capacity is unavailable, keep the outcome unavailable instead of sending the document to another provider.

Finished result: a locally processed document response or an explicit unavailable outcome, with no silent hosted fallback. Model selection, generation, validation and accounting stay on the selected local path.

Local serving and its setup/compatibility instructions are not yet available. Passing today's allowlist does not establish local runtime compatibility. Use the current request patterns above for the interface available now.

Section: DOC-MA-model-controls#related.

Document ID: DOC-MA-model-controls. Section identities and revisions.