impact-ai. Update imports, startup and request boundaries when moving from the earlier API.
Use ESM and the supported Node release lines. If you use the historical Google client or LlamaIndex, check the
current integration catalogue before moving the application.
Migrate from the OpenAI Assistants API
Move the application toclient.responses.create, carry forward its instructions and tool definitions, and
choose how to manage conversation state. Check the tool calls, output items and stream events your application
actually consumes. For Microsoft Foundry, use the standard OpenAI client with the resource’s /openai/v1/
base URL and the deployment name. Check the selected capture boundaries. Integration catalogue.
OpenAI migration guide ·
Microsoft Foundry v1 API