Package org.mockserver.llm.client
Class GeminiLlmClient
java.lang.Object
org.mockserver.llm.client.AbstractLlmClient
org.mockserver.llm.client.GeminiLlmClient
- All Implemented Interfaces:
LlmClient
Runtime client for the Google Gemini
generateContent API. The API key
is passed as a ?key= query parameter; assistant turns use the
model role and system text is hoisted to systemInstruction.
Security note: Gemini's API-key auth mandates the key in the query string, so unlike header-based credentials it can appear in HTTP access/proxy logs. This is a property of the provider's API design, not a MockServer choice; in high-security environments front the call with a gateway that injects the key after ingress.
-
Field Summary
Fields inherited from class org.mockserver.llm.client.AbstractLlmClient
OBJECT_MAPPER -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionbuildCompletionRequest(LlmBackend backend, ParsedConversation prompt) Build the outbound completion request (URL path, auth headers, request body) for the given backend and prompt.parseCompletionResponse(HttpResponse response) Parse a successful provider response body into aCompletion.provider()The provider this client handles — the registry key.Methods inherited from class org.mockserver.llm.client.AbstractLlmClient
appendRoleContentMessages, postJson, readBody, resolveBaseUrl, resolveModel, writeJson
-
Constructor Details
-
GeminiLlmClient
public GeminiLlmClient()
-
-
Method Details
-
provider
Description copied from interface:LlmClientThe provider this client handles — the registry key. -
buildCompletionRequest
Description copied from interface:LlmClientBuild the outbound completion request (URL path, auth headers, request body) for the given backend and prompt. The returned request carries the socket address resolved from the backend's base URL (or the provider default). Implementations pintemperature=0and a seed where the provider supports it, for reproducibility. -
parseCompletionResponse
Description copied from interface:LlmClientParse a successful provider response body into aCompletion. Implementations should tolerate missing optional fields and never throw for a well-formed-but-sparse response; malformed bodies may throw and are handled (fail-closed) byLlmCompletionService.
-