Been checking which models actually power Image Studio against the x402 supported list and honestly the lineup is bigger than the chat UI lets on
x402 gives TEE-verified access to GPT-4.1, GPT-4o, o4-mini from OpenAI, Claude 4.0 Sonnet and 3.7 Sonnet from Anthropic, Gemini 2.5 Flash and Pro from Google, and Grok 3, 4.1 Fast, 2 Vision from xAI.
Image Studio markets itself around Gemini, ByteDance and xAI specifically. but the underlying x402 gateway supports a much wider model roster across four providers, most never named on the product page.
every model routes through the same TEE attestation layer regardless of provider. picking Grok 2 Vision versus Gemini 2.5 Pro doesnt change your privacy guarantee at all, the enclave treats them identically.
if the chat interface only highlights three providers, most users probably never realize they Can request a different model from that same supported list. the breaDth exists in the whitepaper, not really in the product experience.
honestly dont know if this is intentional UI simplicity or a gap between what the backend supports and whats surfaced
whether the model selector ever expands to show the full list, which models get the most usage, any future provider additions
what’s your take a simple three provider UI is good design or hides real choice that already exists??
@OpenGradient $OPG #OPG
x402 gives TEE-verified access to GPT-4.1, GPT-4o, o4-mini from OpenAI, Claude 4.0 Sonnet and 3.7 Sonnet from Anthropic, Gemini 2.5 Flash and Pro from Google, and Grok 3, 4.1 Fast, 2 Vision from xAI.
Image Studio markets itself around Gemini, ByteDance and xAI specifically. but the underlying x402 gateway supports a much wider model roster across four providers, most never named on the product page.
every model routes through the same TEE attestation layer regardless of provider. picking Grok 2 Vision versus Gemini 2.5 Pro doesnt change your privacy guarantee at all, the enclave treats them identically.
if the chat interface only highlights three providers, most users probably never realize they Can request a different model from that same supported list. the breaDth exists in the whitepaper, not really in the product experience.
honestly dont know if this is intentional UI simplicity or a gap between what the backend supports and whats surfaced
whether the model selector ever expands to show the full list, which models get the most usage, any future provider additions
what’s your take a simple three provider UI is good design or hides real choice that already exists??
@OpenGradient $OPG #OPG