Document Tuning Engines as an OpenAI-compatible endpoint

[cerebrixos]

Summary

• Adds a small documentation example showing how to point this project’s existing OpenAI-compatible configuration at Tuning Engines.
• Keeps this project’s APIs and runtime behavior unchanged: no new dependency, adapter, or code path.
• Shows a path for teams to keep this framework in charge of app, agent, tool, workflow, or retrieval logic while routing model calls through a governed OpenAI-compatible endpoint.

Why this belongs here

Tuning Engines is an AI control plane for teams that want centralized model access, routing, tenant-scoped keys, policy/guardrail checks, audit logs, traces, approvals, and usage/cost visibility around existing AI applications.

This project already supports OpenAI-compatible endpoints. The docs change makes that existing capability discoverable for users who want governance and observability without rewriting their application around a separate SDK or changing this project’s runtime behavior.

Testing

• git diff --check

[cerebrixos]

Thank you for taking a look at this docs-only contribution. I checked the current CI results: docs, lint, and mypy pass. The remaining Python 3.14 failures are outside the changed file (docs/models/openai.md), including tests/test_streaming.py::test_run_stream_events_standalone_deprecation. Would a maintainer please rerun the affected test jobs when convenient? I am happy to adjust the example if a docs-specific issue surfaces.