Gemini Agents Api
Manages custom Agent resources on Gemini Enterprise Agent Platform. Use when the user wants to programmatically create, configure, list, update, or delete stateful, server-managed Agent resources (including mounting files, skills, and tools) before executing conversations.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Gemini Agents Api when an AI agent needs a reusable SKILL.md workflow for this job: Manages custom Agent resources on Gemini Enterprise Agent Platform. Use when the user wants to programmatically create, configure, list, update, or delete stateful, server-managed Agent resources (including mounting files, skills, and tools) before executing conversations.
When not to use it
Skip Gemini Agents Api when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/gemini-agents-api # Save SKILL.md to ~/.claude/skills/gemini-agents-api/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/gemini-agents-api/SKILL.md. For a shared project, commit the folder at .claude/skills/gemini-agents-api/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Gemini Agents Api skill for this task: Use Gemini Agents Api when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiinferred
The skill text mentions Gemini or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Gemini Enterprise Agent Platform - Managed Agents API Skill
This skill provides complete instructions, REST request endpoints, and JSON payload structures to programmatically manage **custom Agent resources** on the Gemini Enterprise Agent Platform (Agent Platform).
The **Managed Agents API** forms the **Control Plane** of the platform. It allows developers to provision, retrieve, update, and delete tailored, stateful agent containers equipped with system instructions, sandboxed files, custom skill registries, and local/remote tools. ## Attribution
**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you MUST read [Usage Attribution](references/attribution.md). For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix `gcloud` with `CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:gemini-agents-api)"` and append `agent-skills/1.0 (skill:gemini-agents-api)` to `User-Agent` headers.
---
## 1. Authentication & Setup
All REST requests to the Control Plane must include a Bearer token derived from Application Default Credentials (ADC), and target the production global endpoint.
### 1. Setup Environment Variables
Before running requests, set up the required project variables and access token:
```bash export PROJECT_ID="your-project-id" export LOCATION="global" export ACCESS_TOKEN=$(gcloud auth print-access-token) ```
> [!IMPORTANT] > **API Location Support**: > The `LOCATION` environment variable must be set to a regional location where the Gemini Enterprise Agent Platform's **Managed Agents API** is actively supported (e.g., `global`, or other available regional endpoints).
### 2. Endpoint URL
The production Agents Control Plane endpoint is:
```http https://aiplatform.googleapis.com/v1beta1/projects/{PROJECT_ID}/locations/{LOCATION}/agents ```
---
## 2. Programmatic Agent Management (Control Plane CRUD)
### 1. Create Agent (Long-Running Operation)
To create a new agent resource, issue a `POST` request with the custom configuration. You can mount remote files, folders, or skills directly from **Google Cloud Storage** buckets into the agent container's workspace. Creating an agent is a Long-Running Operation (LRO) that spawns an asynchronous job.
* **Method**: `POST` * **Endpoint**: `https://aiplatform.googleapis.com/v1beta1/projects/${PROJECT_ID}/locations/${LOCATION}/agents`
#### Request Payload
```bash curl -X POST "https://aiplatform.googleapis.com/v1beta1/projects/${PROJECT_ID}/locations/${LOCATION}/agents" \ -H "Authorization: Bearer ${ACCESS_TOKEN}" \ -H "Content-Type: application/json; charset=utf-8" \ -d '{ "id": "my-custom-agent", "base_agent": "antigravity-preview-05-2026", "description": "A professional agent configured with remote tools and mounted Cloud Storage directories.", "system_instruction": "You are a helpful, domain-expert assistant.", "tools": [ {"type": "code_execution"}, {"type": "filesystem"}, {"type": "google_search"}, {"type": "url_context"} ], "base_environment": { "type": "remote", "sources": [ { "type": "gcs", "source": "gs://your-agent-bucket-name/skills", "target": "/.agent/skills" } ], "network": { "allowlist": [ { "domain": "*" } ] } } }' ```
#### LRO Operations Response
Since agent provisioning takes a few moments, the endpoint immediately returns an operation tracking object:
```json { "name": "projects/1234567890/locations/global/operations/operation-987654321-abcde", "metadata": { "@type": "type.googleapis.com/google.cloud.aiplatform.v1beta1.CreateAgentOperationMetadata", "genericMetadata": { "createTime": "2026-05-14T19:00:00.123456Z", "updateTime": "2026-05-14T19:00:01.654321Z" } } } ```
#### [Advanced] Mount Skill Registry Resources
To mount skills directly from the Skill Registry service instead of Cloud Storage, replace the Cloud Storage source item in the payload:
```json "sources": [ { "type": "skill_registry", "source": "projects/your-project-id/locations/global/skills/my-math-skill/revisions/123456789012", "target": "/.agent/skills" } ] ```
#### [Advanced] Configuring Model Context Protocol (MCP) Servers
To configure Third-Party MCP servers for an agent, add the server metadata directly under the `"tools"` parameter array inside the creation request. The platform securely routes tool execution requests to the external MCP server.
> [!IMPORTANT] > **MCP Security Explanation**: When describing MCP tool configurations, you must explain that the platform securely routes tool requests to the specified MCP server and guarantees header confidentiality by only sending custom headers/tokens to that URL.
```json "tools": [ { "type": "mcp", "name": "my-mcp-server", "url": "https://mcp.yourcompany.com/api", "headers": { "Authorization": "Bearer YOUR_MCP_AUTH_TOKEN" } } ] ```
* **name**: A descriptive name for the MCP server. * **url**: The endpoint URL of the external MCP server. * **headers**: (Optional) Custom key-value pairs containing authentication tokens (e.g. API keys, bearer tokens) required to call the server. The platform guarantees that these headers are only sent to the specified MCP server URL.
> [!TIP] > **Overriding MCP at Interaction Time (Data Plane)**: > You can dynamically override or supply MCP tools directly when creating a conversation interaction (Data Plane) by passing `"type": "mcp_server"` inside the `"tools"` payload of `interactions.create`. Refer to the Interactions API documentation for details.
---
### 2. Polling the LRO Status
To track the status of agent creation and obtain the final ready resource, poll the operation URL returned in the `name` field of the creation response.
* **Method**: `GET` * **Endpoint**: `https://aiplatform.googleapis.com/v1beta1/{OPERATION_NAME}`
```bash curl -X GET "https://aiplatform.googleapis.com/v1beta1/projects/1234567890/locations/global/operations/operation-987654321-abcde" \ -H "Authorization: Bearer ${ACCESS_TOKEN}" \ -H "Content-Type: application/json" ```
#### In-Progress Response
```json { "name": "projects/1234567890/locations/global/operations/operation-987654321-abcde", "metadata": { ... } } ```
#### Finished Success Response
Once the container is ready, `"done": true` is set, and the completed `Agent` resource description resides inside `"response"`:
```json { "name": "projects/1234567890/locations/global/operations/operation-987654321-abcde", "done": true, "response": { "@type": "type.googleapis.com/google.cloud.aiplatform.v1beta1.Agent", "name": "projects/your-project-id/locations/global/agents/my-custom-agent", "base_agent": "antigravity-preview-05-2026", "description": "A professional agent configured with remote tools and mounted Cloud Storage directories.", "system_instruction": "You are a helpful, domain-expert assistant." } } ```
---
### 3. Get Agent
Retrieve the configuration metadata, tools, and environment setup of an existing custom agent.
* **Method**: `GET` * **Endpoint**: `https://aiplatform.googleapis.com/v1beta1/projects/${PROJECT_ID}/locations/${LOCATION}/agents/{AGENT_ID}`
```bash curl -X GET "https://aiplatform.googleapis.com/v1beta1/projects/${PROJECT_ID}/locations/global/agents/my-custom-agent" \ -H "Authorization: Bearer ${ACCESS_TOKEN}" \ -H "Content-Type: application/json" ```
#### Response Example Returns the complete configured state of the custom Agent resource:
```json { "name": "projects/your-project-id/locations/global/agents/my-custom-agent", "base_agent": "antigravity-preview-05-2026", "description": "A professional agent configured with remote tools and mounted Cloud Storage directories.", "system_instruction": "You are a helpful, domain-expert assistant.", "tools": [ {"type": "code_execution"}, {"type": "filesystem"}, {"type": "google_search"}, {"type": "url_context"} ], "base_environment": { "type": "remote", "sources": [ { "type": "gcs", "source": "gs://your-agent-bucket-name/skills", "target": "/.agent/skills" } ], "network": { "allowlist": [ { "domain": "*" } ] } } } ```
---
### 4. List Agents
Retrieve a list of all configured custom agents located under the target Google Cloud project.
* **Method**: `GET` * **Endpoint**: `https://aiplatform.googleapis.com/v1beta1/projects/${PROJECT_ID}/locations/${LOCATION}/agents`
```bash curl -X GET "https://aiplatform.googleapis.com/v1beta1/projects/${PROJECT_ID}/locations/global/agents" \ -H "Authorization: Bearer ${ACCESS_TOKEN}" \ -H "Content-Type: application/json" ```
#### Response Example Returns a JSON list of all configured custom Agents under the target project:
```json { "agents": [ { "name": "projects/your-project-id/locations/global/agents/my-custom-agent", "base_agent": "antigravity-preview-05-2026", "description": "A professional agent configured with remote tools and mounted Cloud Storage directories.", "system_instruction": "You are a helpful, domain-expert assistant." }, { "name": "projects/your-project-id/locations/global/agents/my-telecom-agent", "base_agent": "antigravity-preview-05-2026", "description": "A highly specialized telecom support agent.", "system_instruction": "You are a professional telecom support agent. Follow system policies carefully." } ] } ```
---
### 5. Update Agent (Patching Configuration)
Modify configuration fields (such as instructions, descriptions, tools, or mounts) on a custom agent resource in place. You **must** specify the fields being updated using the `update_mask` query parameter.
> [!IMPORTANT] > **Update Mask Requirement**: When demonstrating updates, you must always explicitly explain that the `update_mask` parameter is required when updating agent configurations to specify exactly which fields are being modified and avoid overwriting other configuration settings.
* **Method**: `PATCH` * **Endpoint**: `https://aiplatform.googleapis.com/v1beta1/projects/${PROJECT_ID}/locations/${LOCATION}/agents/{AGENT_ID}?update_mask=system_instruction`
```bash curl -X PATCH "https://aiplatform.googleapis.com/v1beta1/projects/${PROJECT_ID}/locations/global/agents/my-custom-agent?update_mask=system_instruction" \ -H "Authorization: Bearer ${ACCESS_TOKEN}" \ -H "Content-Type: application/json" \ -d '{ "name": "my-custom-agent", "system_instruction": "You are a highly specialized telecom support agent. Follow system policies carefully." }' ```
---
### 6. Delete Agent
Delete custom Agent resources when they are no longer needed to free up backend workspace containers.
* **Method**: `DELETE` * **Endpoint**: `https://aiplatform.googleapis.com/v1beta1/projects/${PROJECT_ID}/locations/${LOCATION}/agents/{AGENT_ID}`
```bash curl -X DELETE "https://aiplatform.googleapis.com/v1beta1/projects/${PROJECT_ID}/locations/global/agents/my-custom-agent" \ -H "Authorization: Bearer ${ACCESS_TOKEN}" ```
#### Response Example A successful deletion request returns an empty JSON response body with HTTP Status `200 OK`:
```json {} ```
---
## 3. Interacting with Custom Agents (Data Plane)
Once you have programmatically created and provisioned your custom stateful agent using the **Control Plane** (this skill), you can execute multi-turn chat, tool execution, and streaming conversations with it using the **Data Plane** (**Interactions API**).
> [!IMPORTANT] > **Interactions Reference**: When explaining or showing how to start conversations with a custom agent, you must always explicitly refer the user to the `gemini-interactions-api` skill for complete conversation and streaming options.
To interact with your custom agent:
1. Obtain your agent's resource path name (e.g., `projects/{PROJECT_ID}/locations/global/agents/{AGENT_ID}`). 2. Pass this resource path directly inside your data plane conversation requests under the **`agent`** parameter.
#### Python Example
```python interaction = client.interactions.create( agent="projects/your-project-id/locations/global/agents/my-custom-agent", input="Hello! Who are you?" ) ```
#### REST / curl Example
```json { "agent": "projects/your-project-id/locations/global/agents/my-custom-agent", "input": [{ "type": "user_input", "content": [{"type": "text", "text": "Hello! Who are you?"}] }] } ```
Refer to the **`gemini-interactions-api`** skill guide (`../gemini-interactions-api/SKILL.md`) for full instructions, Python and TS/JS code blocks, and streaming setups to run conversations with your provisioned agents.
Intended uses
- Use Gemini Agents Api when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.