Secure web integration

The browser should call your application backend, and that backend should hold the AIx credential. Do not ship a shared inference key in client-side JavaScript or public environment variables.

Application-owned endpoint

An application proxy is your own endpoint, not an extra public AIx API route. It must authenticate callers, validate input, bound output and apply per-user usage limits before forwarding a request.

Example browser boundary

A browser can send a small JSON payload to its application-owned backend and render escaped text from the result. Never let arbitrary users select unlimited models, output size or billing authority. Read key security.

Streaming and failures

Keep cancellation, SSE framing and partial-output states explicit. Test the backend HTTP client with controlled mocks before a permitted live smoke test. See backend integration and streaming UI.

Verification and next steps

These instructions describe inspected repository contracts and safe integration boundaries. They do not prove live account access or external provider behavior. Continue with developer answers, API overview and verification limits.