Supported client methods
The Quickstart contains complete cURL, Python, and Node.js examples. A library may be able to send a custom HTTP request, but that does not make its authentication, path construction, retries, response types, or future versions an officially supported SDK integration.
Supported REST operations
All three operations use the same Bearer credential convention. Copy an exact current model ID from the model marketplace or model ID reference.
Compatibility means an implemented subset
The request resembles Google’s GenerateContent structure, but the public contract is not a promise of complete compatibility with every current or future Gemini field, tool, file workflow, authentication mode, streaming method, or SDK feature. A capability is supported only when it appears in the current OpenAPI and the relevant model Parameters page. The model-fixed Playground is also narrower than the generic protocol reference; a successful Try it request does not certify an SDK. If a specific SDK is required for production, send its name, version, language, authentication requirement, and required operations to API support. Until a versioned compatibility matrix is published, use the REST examples as the maintained integration path.Run the REST Quickstart
Generate and parse an image with cURL, Python, or Node.js.
Inspect the OpenAPI
Review the exact request, response, and error contract.