Documentation menu
DEVELOPER DOCUMENTATION

Gemini interface concepts and checks

Validate input formats, required capabilities, and availability separately.

Identify the interface before compatibility

This page treats Gemini-related interfaces as a conceptual evaluation topic, not a statement that UBTL currently supplies any related model. Interfaces may arrange content blocks, roles, tools, and media inputs differently. A conversion must preserve the semantics the application needs. Confirm the base URL, protocol, authentication, and model identifier with support, and consult version-specific documentation rather than assuming another message format can be sent unchanged.

Validate required inputs and results individually

For images, documents, or tools, first confirm that the selected model and interface provide the needed capability, then test formats, sizes, and failure behavior. Do not infer support from a brand name. Use authorized non-sensitive samples and record conversion rules and unsupported-feature paths. Check product subscriptions, cloud permissions, and API authentication separately; one form of access does not establish eligibility for another service.