Consider renaming openai/chat — name is misleading now that it covers the full API

Summary

The openai/chat doc entry covers far more than Chat Completions — it currently includes the Responses API, structured outputs, function calling, streaming, vision, audio, embeddings, image generation, realtime API, webhooks, and pagination. The name chat is misleading and could confuse agents into thinking it only covers the Chat Completions API.

Context

• The OpenAI SDK now recommends the Responses API as the primary API, with Chat Completions as legacy.
• The doc already says "Primary API (Recommended): client.responses.create(...)" but the entry is still called chat.

Suggestion

Rename openai/chat to openai/api or openai/sdk to better reflect its scope. Other packages use clearer names — e.g., anthropic/claude-api, stripe/api.

This would also be a good time to consider whether openai/package should be merged into the renamed entry or kept separate (for SDK internals like config, auth, error handling).

Related

I noticed this while working on a PR to add Responses API structured outputs (responses.parse()), Responses API function calling, and the Conversations API to the Python, JavaScript, and Go docs. Will link the PR here once submitted.