Is your feature request related to a problem? Please describe.
The Vertex AI API supports grounding with Parallel AI Search, but the Go SDK does not expose this functionality. Users who want to use Parallel Web Systems' search API for grounding have to manually construct raw JSON requests instead of using typed Go structs.
Describe the solution you'd like
Add ParallelAiSearch as a new field on the Tool struct, along with supporting config types:
ParallelAiSearch — top-level tool config with api_key (string) and customConfigsParallelAiSearchCustomConfigs — source_policy, excerpts, max_resultsParallelAiSearchSourcePolicy — exclude_domains, include_domains (up to 10 each)ParallelAiSearchExcerpts — max_chars_per_result, max_chars_total
Transformer behavior: passthrough for Vertex AI, rejection for Gemini API (this is a Vertex AI-only feature).
The response side requires no changes — existing GroundingMetadata types already handle the Parallel AI Search response format.
Describe alternatives you've considered
Manually constructing the parallelAiSearch tool config as map[string]any and passing it through ExtraBody, but this bypasses type safety and is error-prone.
Additional context
Possible implementation in #690
Is your feature request related to a problem? Please describe.
The Vertex AI API supports grounding with Parallel AI Search, but the Go SDK does not expose this functionality. Users who want to use Parallel Web Systems' search API for grounding have to manually construct raw JSON requests instead of using typed Go structs.
Describe the solution you'd like
Add
ParallelAiSearchas a new field on theToolstruct, along with supporting config types:ParallelAiSearch— top-level tool config withapi_key(string) andcustomConfigsParallelAiSearchCustomConfigs—source_policy,excerpts,max_resultsParallelAiSearchSourcePolicy—exclude_domains,include_domains(up to 10 each)ParallelAiSearchExcerpts—max_chars_per_result,max_chars_totalTransformer behavior: passthrough for Vertex AI, rejection for Gemini API (this is a Vertex AI-only feature).
The response side requires no changes — existing
GroundingMetadatatypes already handle the Parallel AI Search response format.Describe alternatives you've considered
Manually constructing the
parallelAiSearchtool config asmap[string]anyand passing it throughExtraBody, but this bypasses type safety and is error-prone.Additional context
Possible implementation in #690