AI clients and agents

Argent for Google Gen AI and Vertex AI

Gemini API and Vertex AI calls from the Google Gen AI SDK route through Argent for policy and records. Here is what Argent governs, how it connects and what your team sets.

Google logo
01 / AI CLIENTS AND AGENTS

What Argent does with Google Gen AI and Vertex AI

Every model call an app makes with Google Gen AI and Vertex AI goes through Argent first. Argent knows which agent sent it and which person owns that agent, checks it against your policy, and writes a signed record of what it decided.

  • A named agent with a human owner. Each app or service you connect uses its own Argent agent key, tied to an accountable person, so no call is anonymous. Identity tethering
  • Only the models you allow. The agent can reach only the providers and models your policy names, and a request can be swapped to an approved model. Model control
  • Sensitive data handled before it leaves. Prompts and replies are scanned for personal and secret data, then redacted or blocked as your policy says. Sensitive data redaction
  • Spend priced and capped. Every request is priced and metered against budgets for the agent, its owner and the teams above them. AI spend caps
  • A signed record you can replay. Each decision becomes a hash-chained, signed audit record, and requests are grouped into sessions you can replay. Session replay
02 / AI CLIENTS AND AGENTS

How Google Gen AI and Vertex AI connect

Google Gen AI and Vertex AI reach Argent in two ways.

  • Gateway base URL. Your app points Google Gen AI and Vertex AI at your Argent route (its base URL setting) and uses an Argent agent key in place of the provider key. Argent removes that key and adds the real provider credential from your vault on the way out, so your app never holds it.
  • TLS-inspecting forward proxy. Your app keeps its normal Google Gen AI and Vertex AI settings and sends its HTTPS traffic through the Argent forward proxy and trusts your Argent certificate; the exact settings are below. The proxy signs in with the agent's own key, so every call is attributed, then runs the same checks as the gateway. It opens only known AI hosts, and its certificate is limited to those hosts.

The same steps are in the Argent console under Integrations > AI Clients, and each agent's Connect tab gives the copy-paste values for your tenant.

03 / AI CLIENTS AND AGENTS

What you configure

What your team sets in Google Gen AI and Vertex AI. These are the settings the Argent console shows for this tool. Values in angle brackets come from your tenant.

  1. Gemini API via gateway. genai.Client(api_key=<an Argent agent key>, http_options={'base_url':'https://<ARGENT_GATEWAY>/<tenant>/google'}).
  2. Gemini API via forward proxy. Forward-proxy mode (no URL change): HTTPS_PROXY=http://<user>:<ARGENT_AGENT_KEY>@<ARGENT_PROXY_HOST> plus trust of the tenant intercept CA. The tenant must have the forward proxy enabled and the vendor host registered as an upstream.
04 / AI CLIENTS AND AGENTS

Make Argent the only path

Make Argent the only path for Google Gen AI and Vertex AI. These controls are documented by the platform each one belongs to (linked); pair them with the Argent settings above.

  • Vertex AI VPC Service Controls. Vertex AI API reachable only through an access level containing the Argent IP. Vendor docs
  • Machine-wide environment variables (Windows). Sets the base URL / proxy / CA variables for every process on the machine so SDK-based apps default to Argent. Vendor docs
  • Managed environment (macOS). Same variables for GUI-launched and shell processes. Vendor docs
  • Service / container environment (Linux, Kubernetes, CI). Sets the variables where most production SDK code runs. Vendor docs

Same settings everywhere it runs. The Argent fleet setup script and certificate bundle give every service, container and build runner the same proxy and certificate settings.

Want to see which AI tools people already run before you push anything? Start with Shadow AI discovery in watch mode. Watch before you enforce

05 / AI CLIENTS AND AGENTS

Check that it works

Send one request and look for the signed row. Signed LLM row for the google route in the Argent console live stream.

Every request also appears on the live stream with the agent's name and owner, and in the session view. Session replay