AiHummer
English▾
Sign inAccount
v1.6.x▾
{ }Swagger

Model capabilities and data-processing routes

v1.6.x · updated 2026-11-15

A successful connection test proves neither every model feature nor a permitted processing location. Start with a configured provider and the model your task needs. A working answer requires a real available provider; a paid API key is not mandatory when a supported local or subscription connection is available.

Select actual capabilities

A capability profile describes observations for a particular account, model and request combination. Tools, structured output, streaming, images and their combinations are separate capabilities. Passing tools and streaming separately does not prove that they work together. A completed test report can still contain failed or unavailable cases.

An authorized administrator reviews and explicitly selects the current profile. Testing may contact the configured provider and consume usage; it does not execute arbitrary business tools. Account reconnection, model withdrawal or profile changes require current checks. An explicit model, effort or output limit remains part of the request rather than permission to silently select a different account.

Stage routing can choose among configured compatible models. A short complete answer does not need escalation merely for its length. A retry or fallback still obeys the source policy, available capabilities, deadline and budget. Usage and charges are different facts; missing prices or late usage must not be presented as zero. Evaluate a route by the complete successful task and its actual attempts, not a connection ping alone.

Declare processing separately from storage

In the model settings, open Where data is processed.

  1. Create a Processing profile for the exact endpoint, processing stage, actual service tier, class, processing region and retention profile.
  2. Create a Source policy with the permitted classes, regions, retention and routes.
  3. Use Assign policy to source to choose the existing workspace, conversation, document or completed media upload. Tenant and inherited restrictions remain applicable.

These profiles contain declarations entered by the operator; they do not independently verify the provider’s actual processing practices. A server name, private network address, storage region or product name does not establish a processing region. Previously unclassified material must not be relabeled as local simply to make a request pass.

The same source rules apply to answers, indexing, embeddings, reranking, OCR, speech, media and delegation where those paths are used. Source access and processing permission are both necessary. Sharing a result does not remove either check. Inspect the request report’s selected route and any unverified processing warning. If a route is incompatible, unconfigured or changed, resolve the concrete restriction rather than retrying through an undeclared endpoint.

Bounded programs for collections

For many similar reads, ask an enabled agent to use a bounded tool program to filter or aggregate permitted results. The optional program tool reads through the same allowed tools; it is not a shell or a new permission. Each source read keeps its current access checks. A stopped or incomplete program must identify its limit instead of claiming that every record was processed. The complete accepted source results remain available under their original access rules.