[OPEN-7543] Update OpenAI Wrapper to support Responses API

[viniciusdsmello]

Pull Request

Summary

This PR adds comprehensive tracing support for OpenAI's new Responses API (client.responses.create) while maintaining full backward compatibility with the existing Chat Completions API (client.chat.completions.create).

Changes

• Updated trace_openai and trace_async_openai to dynamically detect and patch the responses.create endpoint.
• Implemented new handler functions for both streaming and non-streaming Responses API calls (sync and async).
• Added helper functions for Responses API-specific parameter mapping, output parsing, streaming chunk extraction, and usage data extraction.
• Modified add_to_trace to differentiate between Chat Completions and Responses API calls for improved trace naming and metadata.
• Created a comprehensive example (examples/tracing/openai/responses_api_example.py) demonstrating usage for both APIs, including streaming and function calling.

Context

OpenAI's Responses API unifies multiple capabilities (chat, text, tool use, JSON mode) into a single interface, providing improved metadata structure and traceability. This update extends Openlayer's tracing logic to support this new, more aligned endpoint, ensuring that users can leverage the latest OpenAI features with full observability without breaking existing integrations.

Testing

• Unit tests (comprehensive test suites verifying backward compatibility and new Responses API features for both sync and async clients)
• Manual testing (verified functionality using the new example script)
• Postman CI/CD
• Other (please specify)

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[gustavocidornelas]

@viniciusdsmello, this PR is almost good to go! I left a couple of comments in some parts of the code.

Besides them, it would be good if you could squash the commits so that this PR has a single commit (following the convention we discussed).

Thanks!

[gustavocidornelas]

No need for this example. This is redundant with openai_tracing.ipynb. I would just add a new cell showing that the same tracer works with the responses API.

[gustavocidornelas]

You can remove this metadata. Unless there's an intention to leverage it somehow in the platform. From the name of the step, it's already clear that it's a Response call (instead of a chat completion call)

[gustavocidornelas]

There's an issue with this function. Consequently, the inputs for the OpenAI Response steps are not rendering properly:

For this step, the input should be something like:

{
    "prompt": [{"role": "user", "content": "What is 3+3?"}]
}

I believe you're just sending: {"prompt": "What is 3+3?"}.

You just need to double check the Responses API reference to ensure this function works for all input formats (e.g., single user message, multi-turn conversation, etc.)