Defaults
Baseline API behavior. These values apply when a request does not specify them explicitly.
Default priority
Choose the priority used when a request omits the priority parameter: cheapest, fastest, best, or balanced (the default). You can override this per request at any time.
Format & inference
Set the default output format (markdown, JSON, plain text) and toggle priority inference. When inference is on, the pipeline reads your prompt and selects the most appropriate priority automatically. When off, the account default always applies.
Endpoint-specific overrides
Set different defaults per endpoint. For example, always return JSON from /code or use cheapest priority for /entities. This reduces boilerplate in your integration — set it once here instead of on every request.
Assembly settings
Control the final quality assurance step. Critical review runs a second model pass to check quality. Refinement iterations (0–3) control how many critique-and-improve cycles to run. Fact verification cross-checks claims against sources. These default to sensible values per priority level but can be overridden here or per outcome.
Outcome-specific overrides
Set priority and assembly settings for individual outcomes. For example, always use best quality with 2 refinement iterations for "Market Research Report." These overrides take precedence over endpoint and global defaults. You can also set these directly on any outcome detail page.
Principle detection
Toggle whether the pipeline detects and stores principles from your prompts. When enabled, instructions like "always use formal language" are remembered across requests. When disabled, only manually-set principles apply. Manage stored principles in Principles.