Response API adds previous_response_id for multi-turn context, and streaming

• Continue conversations across multiple turns using the previous_response_id parameter to maintain context without resending full history
• Stream responses in real time as they are generated for responsive applications
• Control response storage with the store parameter—choose whether responses are retrievable by ID or ephemeral

See the Response API guide for usage examples and details.