Index
InteractionsService(interface)VoicesHttpService(interface)VoicesService(interface)
InteractionsService
API that allows users to interact with models and agents.
| CancelInteraction |
|---|
|
Cancels an interaction.
|
| CancelInteractionHttp |
|---|
|
Cancels an interaction.
|
| CreateInteraction |
|---|
|
Creates an interaction.
|
| CreateInteractionHttp |
|---|
|
Generates a set of responses from the model.
|
| CreateInteractionStream |
|---|
|
Creates an interaction and streams the response.
|
| DeleteInteraction |
|---|
|
Deletes an interaction.
|
| GetInteraction |
|---|
|
Fully typed proto, unary version of GetInteraction that returns Interaction proto.
|
| GetInteractionHttp |
|---|
|
Gets an interaction.
|
| GetInteractionStream |
|---|
|
Fully typed proto, streaming version of GetInteraction that returns Interaction proto.
|
| ListInteractions |
|---|
|
List interactions.
|
| ListInteractionsHttp |
|---|
|
List interactions.
|
VoicesHttpService
VoicesService
VoicesService defines typed RPCs for future SDK generation. NOTE: No handlers are currently registered for these RPCs. All traffic is served via VoicesHttpService (the HttpBody-wrapping service). When handlers are added, the scaffolding_registration_test in labs/language/genai/Voices/ must be updated to include "VoicesService" in its services argument.
Because this service ships in the same proto_library as VoicesHttpService, both are registered into the live ESF config together. A method here must therefore NOT declare a method_http_map matching one of VoicesHttpService's REST templates: ESF resolves on (path, verb), and two methods claiming one route make it reject every request to that route as ambiguous rather than pick one. Every method below uses a distinct custom-verb suffix (":create", ":get", ":list", ":delete") so its REST template never matches VoicesHttpService's bare-path templates, mirroring the convention InteractionsService's typed RPCs use for the same reason (e.g. ListInteractions -> "interactions:list").