Skip to Main Content
Shape the future of IBM watsonx Orchestrate

Start by searching and reviewing ideas others have posted, and add a comment (private if needed), vote, or subscribe to updates on them if they matter to you.

If you can't find what you are looking for, create a new idea:

  1. stick to one feature enhancement per idea

  2. add as much detail as possible, including use-case, examples & screenshots (put anything confidential in Hidden details field or a private comment)

  3. Explain business impact and timeline of project being affected

[For IBMers] Add customer/project name, details & timeline in Hidden details field or a private comment (only visible to you and the IBM product team).

This all helps to scope and prioritize your idea among many other good ones. Thank you for your feedback!

Specific links you will want to bookmark for future use
Learn more about IBM watsonx Orchestrate - Use this site to find out additional information and details about the product.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Under review
Created by Guest
Created on Jun 4, 2026

Add native support for non–OpenAI-compliant Gemini 3.x APIs by introducing a new provider spec beyond openai-oauth2-client-creds.

Google’s newer Gemini 3.x models use updated APIs that are not OpenAI-compatible, so current integrations break and prevent customers from adopting latest model capabilities.

Who would benefit:

  • Existing WXO customers using Google Vertex AI via Apigee (like UPS)
  • Future clients adopting Gemini 3.x and beyond
  • IBM teams aiming to stay competitive with multi-model orchestration support

How it should work

  • Introduce a new provider type (e.g., google-genai-oauth2) that directly supports Gemini-native API schemas
  • Allow flexible request/response mapping instead of enforcing OpenAI chat-completions format
  • Maintain oauth2 client credentials support while decoupling from OpenAI API contract
  • Support configuration of Vertex AI / Apigee endpoints with schema transformation if needed
Idea priority High