Home›Agents›Google Agent Development Kit

AgentenCode evidence profileAutomation

✓ Editorially reviewedChecked: September 30, 2026

Agent profile · Automation

Google Agent Development Kit

Google Agent Development Kit is classified by AgentenCode as a agent framework from Google. It belongs to the Automation category. This English profile does not maintain a separate factual record: it renders the same underlying evidence, trust and history data as the German profile.

GoogleAutomationDevelopers

View profile ↓Check sources ↓

ECOSYSTEM ASSOCIATION

This agent profile links to a curated provider view. Security controls are not inherited across products.

Google · Gemini & Entwickleragenten ↗

Automationeditorial classification

Googleprovider

11 primary sourcessource status

September 30, 2026last verification

AgentenTrust 2.0 · EU & governance evidence

Trust, privacy and control evidence for Google Agent Development Kit

Direct answer: AgentenCode currently documents 4 of 36 normalized trust controls for this profile. Missing fields remain Unknown and are never automatically interpreted as “no”.

EU AI ActEvidence context only. AgentenCode does not infer legal applicability or compliance from individual product controls.

GDPRPrivacy and security signals are documented field by field. Data residency alone is not a compliance or transfer assessment.

Privacy contextPrivacy & data2 of 8 documentedResidency, training, retention, DPA, subprocessors and processing scope.

Security contextSecurity & access2 of 10 documentedEncryption, SSO, SCIM, RBAC, roles and credential handling.

Human controlHuman control0 of 10 documentedApproval, oversight, permissions and stop or rollback controls.

TraceabilityAudit & traceability0 of 8 documentedAudit logs, APIs, SIEM, observability, tracing and activity history.

Important: these numbers show evidence coverage, not a product rating. 0 of 10 means that no field-level public evidence is stored for those ten controls in the current dataset. It does not mean the product lacks those capabilities.

Field-level evidence

Documented controls and values from primary sources.

Documented yesDocumented valueUnknown remains unknown

High confidence

Governance · RBAC

Yes — documented

ADK agents deployed with Agent Identity use Google Cloud IAM roles and policies for resource access.

Scope: adk_on_agent_runtime_with_agent_identity · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Tracing

Yes — documented

ADK deployments on Agent Runtime support OpenTelemetry-based tracing.

Scope: adk_on_agent_runtime · verified 2026-10-01 · Primary source ↗

High confidence

Hosting · Managed

Yes — documented

ADK agents can be deployed to Google Agent Runtime as a fully managed runtime.

Scope: adk_agent_runtime · verified 2026-10-01 · Primary source ↗

High confidence

Hosting · Private Network

Yes — documented

ADK agents deployed on Vertex AI Agent Engine can use private VPC connectivity.

Scope: adk_on_vertex_ai_agent_engine · verified 2026-10-01 · Primary source ↗

High confidence

Hosting · Self Hosted

Yes — documented

ADK supports local/customer-managed runtime execution in addition to managed Agent Runtime deployment.

Scope: adk_local_or_customer_managed_runtime · verified 2026-10-01 · Primary source ↗

High confidence

Privacy · Data residency · Available

Yes — documented

ADK agents deployed on Agent Platform can use regional agent infrastructure with documented data-at-rest residency.

Scope: adk_on_gemini_enterprise_agent_platform_runtime · verified 2026-10-01 · Primary source ↗

High confidence

Privacy · Data residency · Customer Region Selectable

Yes — documented

Customers select a supported Agent Platform location when deploying regional agent infrastructure.

Scope: adk_on_gemini_enterprise_agent_platform_runtime · verified 2026-10-01 · Primary source ↗

High confidence

Protocols · A2A · Server

Yes — documented

ADK agents created with the supported template can expose an A2A service endpoint.

Scope: adk_agents_built_with_agents_cli · verified 2026-10-01 · Primary source ↗

High confidence

Protocols · A2A · Supported

Yes — documented

A2A is a documented first-party interoperability mode for ADK agents.

Scope: adk_agents · verified 2026-10-01 · Primary source ↗

High confidence

Protocols · Mcp · Client

Yes — documented

ADK agents can consume MCP servers through the documented MCP toolset.

Scope: adk_agents · verified 2026-10-01 · Primary source ↗

High confidence

Security · Customer-managed keys

Yes — documented

ADK agents deployed on Vertex AI Agent Engine can use CMEK for data-at-rest protection.

Scope: adk_on_vertex_ai_agent_engine · verified 2026-10-01 · Primary source ↗

Evidence-backed overview

What is Google Agent Development Kit?

Product-specific evidence for Google Agent Development Kit

This profile links 11 unique primary sources across the product profile, field-level evidence, trust controls and documented relations. The points below describe this product’s stored evidence rather than generic characteristics of Automatisierung.

Data Residency

Yes · Scope: adk_on_gemini_enterprise_agent_platform_runtime · verified 2026-10-01.

Primary source ↗

Region auswählbar

Yes · Scope: adk_on_gemini_enterprise_agent_platform_runtime · verified 2026-10-01.

Primary source ↗

Customer-Managed Keys

Yes · Scope: adk_on_vertex_ai_agent_engine · verified 2026-10-01.

Primary source ↗

RBAC

Yes · Scope: adk_on_agent_runtime_with_agent_identity · verified 2026-10-01.

Primary source ↗

governance · tracing

Yes · Scope: adk_on_agent_runtime · verified 2026-10-01.

Primary source ↗

protocols · a2a · server

Yes · Scope: adk_agents_built_with_agents_cli · verified 2026-10-01.

Primary source ↗

AgentenCode treats this page as a reference profile rather than a ranking. Product facts are separated from editorial classification, and the profile is tied to a specific verification date. If a capability is not backed by sufficiently precise public evidence, it remains unknown instead of being inferred from marketing language or from similar products.

1primary source

11field-level evidence claims

4documented trust controls

1history events

How to read the evidence

The field-level evidence layer records a value, a scope, a confidence level, a verification date and one or more primary sources. Scope matters: an enterprise-only security feature must not be generalized to every plan or deployment surface. The same rule applies to hosting, privacy, audit and protocol claims.

AgentenCode also keeps Unknown distinct from false. A missing claim means the public dataset does not currently contain sufficiently precise evidence for that field. A negative value is used only when a reliable primary source explicitly documents a restriction or non-availability.

Decision context

Provider and category

Google Agent Development Kit is documented under Automation and is associated with Google. Category labels help navigation but do not replace product-specific evidence.

Verification status

The public profile is marked editorially reviewed and was last checked on September 30, 2026.

Trust coverage

4 of 36 normalized trust controls currently have field-level public evidence. The remaining controls are not treated as negative findings.

Source-first use

For procurement, security or legal decisions, use the linked primary sources and verify the plan, region and configuration that apply to your organization.

Capabilities, strengths and deployment checks for Google Agent Development Kit

Google Agent Development Kit is classified as Agenten-Framework from Google. The profile’s editorial layer is derived from the stored use cases, strengths and checks below; claims about security, privacy or governance remain separate and require field-level evidence.

Agenten entwickeln

This use case is part of the stored profile for Google Agent Development Kit. The related strength is “Open Source”. In a production evaluation, the practical boundary to verify is: Produktionsbetrieb separat absichern.

Multi-Agent-Systeme

This use case is part of the stored profile for Google Agent Development Kit. The related strength is “Modell- und Tool-Abstraktion”. In a production evaluation, the practical boundary to verify is: Tool-Berechtigungen strikt definieren.

Tool-Integration

This use case is part of the stored profile for Google Agent Development Kit. The related strength is “Multi-Agent-Muster”. In a production evaluation, the practical boundary to verify is: Evaluations- und Monitoringkonzept vor Skalierung aufsetzen.

Agenten testen und evaluieren

This use case is part of the stored profile for Google Agent Development Kit. The related strength is “Google-Cloud-Integration möglich”. In a production evaluation, the practical boundary to verify is: Produktionsbetrieb separat absichern.

What to verify before adoption

Produktionsbetrieb separat absichern. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Tool-Berechtigungen strikt definieren. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Evaluations- und Monitoringkonzept vor Skalierung aufsetzen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.

Editorial boundary: The use-case and strength descriptions are product-specific editorial context based on the stored profile. Trust, privacy and governance statements are only presented as facts when field-level primary-source evidence exists.

Verified history

The public history layer records only confirmed profile changes and verification events. Monitoring signals are not published as product facts until they have been reviewed.

September 30, 2026 · New profile

Official sources

This profile links 11 unique primary sources across the product profile, field-level evidence, trust layer and documented relations. Provider documentation remains authoritative when the product changes between verification cycles.

Frequently asked questions

What is Google Agent Development Kit?

Google Agent Development Kit is listed by AgentenCode as an automation agent or agentic product from Google.

How much trust evidence is documented for Google Agent Development Kit?

The current trust layer documents 4 of 36 normalized controls. Missing controls remain unknown rather than being treated as false.

When was this profile last checked?

The current profile verification date is September 30, 2026. The linked primary sources remain authoritative if the product changes between checks.

Method note: AgentenCode does not certify GDPR or EU AI Act compliance. It documents evidence that can support a separate legal, security or procurement assessment.