Models and Routing

EQUIRE selects a model for each AI request from the settings available to that workflow. A platform administrator can set a feature-specific model or a platform default without a deployment. New IC memo sections, generated deliverable versions, and supported AI usage records distinguish that selected request from a serving model confirmed by AI Gateway. An internal prompt tier is not a model ID.

How a model is selected

For text work, the application considers a compatible model selected for the call, then an applicable workflow setting, then the platform default. If none applies, it uses the application's code fallback. A setting may be skipped when the model is unavailable or fails the workflow's capability, region, or data-handling checks. The active choice can therefore differ from a model named in an older saved setting.

Internal names such as chat, critical, extraction, and verification shape a request. They do not identify the model that ran. A label such as “critical” in an older record is not proof of a specific provider or model version.

Administrators can review compatible choices and the effective default under Admin → Model Config. The available models and each workflow's effective default are loaded from the current catalog and platform settings. An organization's AI usage records show the selected request and, when Gateway metadata attests it, the model that served the call. A completed call without serving evidence retains a requested basis rather than claiming the selection was the served model.

Availability and privacy

When AI Gateway credentials are configured, eligible requests route through Vercel AI Gateway. The Gateway catalog and EQUIRE's compatibility checks determine which models can be selected for a workflow. If only direct Anthropic access is configured, text requests use the supported direct fallback.

The platform's Zero Data Retention setting restricts Gateway choices to models with an eligible route. A model visible in a catalog is not necessarily available for every workflow or every privacy setting. Prompts and completions are excluded from EQUIRE telemetry; generated deal artifacts remain in the deal's permissioned records so the team can review and use them.

Audit trail

Usage is tagged with the workflow, organization, and user when available. For new IC memo sections and generated deliverable versions, the saved serving model ID is present only when Gateway attests it; otherwise it is empty, with the selected request and evidence basis recorded separately. Review that provenance alongside source evidence, release basis, and human review state. Model choice does not turn an AI draft into an approved investment decision.

For data-handling and review rules, see Trust and safety. For specialist workflows, see Specialist agents.