Authoritative documentation · English

Runtime API

The production Runtime is self-hosted. Trusted server applications authenticate with revocable credentials and select an activated assistant release; browsers and mobile applications should call that trusted server, not hold Runtime credentials.

Answer contract

Admitted questions stream typed events over HTTPS. A supported completion identifies its assistant and release, includes citations, and reports normalized provider/model usage. A semantically unsupported complete answer returns the exact abstention I don't know; operational faults use typed errors instead.

Request safety

Use an idempotency key for retryable requests. Respect request-size, rate, concurrency, timeout, token, and cost limits. The Runtime does not silently select another release, provider, or model when the requested configuration is unavailable.

Integration source

Generate clients from the versioned OpenAPI contract and verify compatibility before deployment. The Laravel server-side example keeps answering credentials outside browsers and native clients.