[api设置] What impact will the launch of Assistants API v2 have on assistants created using API v1?

Impacts on Playground, Costs, and Migration

No automatic upgrade: Your current assistants, threads, and runs will not be automatically migrated to v2. They will remain accessible and operable under the v1 API unless you choose to migrate them manually.

Simultaneous access to both versions: You can access both v1 and v2 API versions at the same time. This means you can continue using v1 for existing assistants and also explore the new features and improvements offered by v2.

Token usage differences: There may be differences in token usage between v1 and v2, especially when using file search and retrieval tools. The file_search tool in v2 generally consumes fewer tokens on average than the retrieval tool in v1, but if you prefer, you can continue using the old retrieval tool with the v1 version header.

Migration options: Although the Playground UI and newer SDK versions have migrated to using the v2 API, your assistants will not automatically upgrade. You have flexibility in choosing the API version used for integration. Please keep in mind that assistant objects do not have a default API version, and you can continue using the old version until the end of 2024. If you need more information about migrating from Assistants v1 to v2, please see the migration guide.

By understanding these impacts, you can better decide how to manage and migrate your assistants between old and new versions.