module documentation
Serializable Pydantic models for the Gemini SDK Temporal integration.
These models cross the activity boundary — they're constructed on the workflow side and deserialized on the activity side (or vice versa).
| Class | _ |
Serializable activity input for a Gemini SDK API call. |
| Class | _ |
Serializable activity output for a Gemini SDK API call. |
| Class | _ |
Serializable activity output for a batched streamed API call. |
| Class | _ |
Serializable activity input for a file download. |
| Class | _ |
Serializable activity input for id-addressed interactions/agents calls. |
| Class | _ |
Serializable activity input for interactions/agents calls without an id. |
| Class | _ |
Serializable activity output for a batched streamed interaction call. |
| Class | _ |
Serializable activity input for registering GCS files. |
| Class | _ |
Serializable activity input for a file upload. |
| Class | _ |
Serializable activity input for uploading a file to a file search store. |
| Class | _ |
Serializable activity input for an MCP call_tool invocation. |
| Class | _ |
Per-request HTTP options that can be serialized across the activity boundary. |