Reference

Reference pages describe exact accepted syntax and supported machine contracts. They are generated from application source definitions wherever possible. Choose the contract you are writing or inspecting.

Configuration

• Use Configuration reference for generated project, connection, source, workspace, model-table, semantic-model, dashboard, access, and refresh-pipeline fields.
• Use Environment variable reference for process settings, defaults, lifecycle, secret classification, and production relationships.
• Use Supported capabilities for the current boundary of resource, data, visual, security, operational, and integration surfaces.

Commands and APIs

• Use Agent tool reference for generated names, privileges, defaults, MCP annotations, and input and output schemas.
• Use CLI command reference for generated usage, arguments, flags, defaults, and inherited options.
• Use API reference for generated operation groups and the downloadable OpenAPI contract.
• Use API conventions for shared authentication, pagination, error, retry, timeout, and compatibility rules.

Visuals

Use Visual types for every supported renderer-neutral visual shape, its dashboard configuration, expected query shape, and live example.

Keep generated reference authoritative

When a guide and generated reference disagree on exact syntax, follow the reference for the deployed version and report the guide drift. Agent tool contracts are generated from the same provider composition used by built-in chat and MCP. Do not hand-edit generated pages. Contributors should use Write documentation and the Repository and development workflow to regenerate and verify reference artifacts.