canonical: https://jentic.com/apis/googleapis.com/vpcaccess

# Google Serverless VPC Access API

The Serverless VPC Access API manages connectors that let serverless services (Cloud Run, Cloud Functions, App Engine standard) reach internal IP addresses inside a VPC network. It exposes connector create, list, get, and delete operations along with locations and long-running operation tracking. Connectors are the canonical bridge for serverless workloads that need private connectivity to databases, internal load balancers, or other VPC-only resources.

## For AI agents

Provision and manage VPC Access connectors so serverless services can reach VPC-internal resources, without giving the agent broad networking privileges.

## Scope

Does not handle VPC subnet creation, firewall rules, or Cloud Run/Cloud Functions service deployment - use for managing Serverless VPC Access connectors only.

## Capabilities

- Create a Serverless VPC Access connector in a chosen region and network
- List existing connectors in a project to audit serverless-to-VPC bridges
- Get a connector's state, throughput, and IP CIDR range for capacity review
- Delete a connector that is no longer needed by any serverless service
- List supported regions for connector creation
- Track the long-running operations behind connector create and delete calls

## Use cases

### Serverless to VPC Database Connectivity

Application teams running Cloud Run or Cloud Functions services configure a Serverless VPC Access connector so the serverless workload can reach a Cloud SQL private instance, a self-hosted database in Compute Engine, or an internal load balancer. The API creates the connector with a specified IP CIDR range and minimum and maximum throughput, then a separate Cloud Run or Cloud Functions configuration call attaches the connector to the service.

Example prompt: Create a connector named svc-vpc-1 in us-central1 with throughput min 200 and max 1000 in the production VPC

### Connector Inventory and Cleanup

Platform teams audit projects for unused connectors that incur ongoing cost by listing all connectors and cross-referencing with the serverless services that reference them. The VPC Access API exposes a get endpoint that returns connector state and configuration so the cleanup job can verify the connector is no longer attached before issuing a delete.

Example prompt: List connectors in the project, identify those with zero attached services, and delete the orphans

### Multi-Region Serverless Network Topology

Teams deploying serverless services across multiple regions provision a connector per region so each service has a low-latency path into the local subnet. The VPC Access API exposes per-region connector resources and a locations list endpoint so the deployment script can iterate over supported regions and create connectors with consistent throughput settings.

Example prompt: Iterate over us-central1, us-east1, and europe-west1 and create a connector in each region

### AI Agent Networking Operator

An AI agent integrated through Jentic responds to platform prompts like 'enable private connectivity for our new Cloud Run service' by creating a VPC Access connector in the right region and reporting the connector resource name back to the caller. Because the API uses OAuth 2.0 with the cloud-platform scope, Jentic isolates the token in your Jentic One instance and exposes only a scoped reference.

Example prompt: Search Jentic for create vpc access connector and call it for the chosen region and VPC network

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v1/{+parent}/connectors | List VPC Access connectors in a project and region |
| GET | /v1/{+name}/locations | List supported VPC Access locations |
| GET | /v1/{+name}/operations | List long-running operations |
| DELETE | /v1/{+name} | Delete a connector or operation by name |

## Key resources

- **Connectors** — Create, list, get, and delete Serverless VPC Access connectors per region
- **Locations** — Enumerate the regions where connectors can be provisioned
- **Operations** — Track long-running connector create and delete operations

## Why Jentic

- **Setup:** Wiring the Serverless VPC Access API by hand means setting up a Google service account, granting the cloud-platform scope, building the project and location parent names, and polling long-running connector operations yourself. Through Jentic you install once, import the Serverless VPC Access API from the API Directory, store the service-account credential once, and your agent calls it.
- **Permission scoping:** Serverless VPC Access carries the project and location parent in the URL path (/v1/{parent}/connectors), so a rule can pin your agent to one project or location: it can list and read connectors there and nothing else. You choose the operations it may call, so connector deletion is not included unless you add it.
- **Credential handling:** Your Serverless VPC Access service-account credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list vpc access connectors' or 'create a vpc access connector', and Jentic returns the matching VPC Access v1 operation with its input schema, including throughput min and max and the CIDR fields, so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cloud Run API** — Attach VPC Access connectors to Cloud Run services for private VPC connectivity
- **Cloud Functions API** — Attach VPC Access connectors to Cloud Functions for private VPC reachability
- **Compute Engine API** — Manage the VPC networks and subnets that VPC Access connectors live in
- **Network Connectivity API** — Hub-and-spoke connectivity for non-serverless workloads, distinct from connector-based VPC access

## FAQ

### What authentication does the Serverless VPC Access API use?

The Serverless VPC Access API uses OAuth 2.0 with the https://www.googleapis.com/auth/cloud-platform scope. Through Jentic, the OAuth token is stored encrypted in your Jentic One instance and only a scoped reference is exposed to the agent at execution time.

### Can I create a VPC Access connector with the Serverless VPC Access API?

Yes. Use POST under /v1/{+parent}/connectors with the network name, ipCidrRange, minThroughput, and maxThroughput. The call returns a long-running operation; track it on /v1/{+name}/operations until done is true and the connector reaches READY state.

### What are the rate limits for the Serverless VPC Access API?

Default project quotas allow 600 requests per minute on control-plane operations. The number of connectors per project per region is also bounded by VPC subnet IP availability for the connector CIDR; verify subnet headroom before creating multiple connectors.

### How do I audit unused VPC Access connectors through Jentic?

Install Jentic with pip install jentic, search for list vpc access connectors, load the schema for GET /v1/{+parent}/connectors, then call it per region. Cross-reference the returned names with Cloud Run and Cloud Functions service configurations to identify connectors with zero attached services before deleting.

### Does the Serverless VPC Access API attach connectors to Cloud Run or Cloud Functions services?

No. The VPC Access API only manages the connector resources. Attaching a connector to a serverless service is done through the Cloud Run or Cloud Functions API on the service configuration. The connector resource name is the link between the two.

### Why is my new VPC Access connector stuck in CREATING state?

Long-running connector creation typically completes within a few minutes. Persistent CREATING usually indicates a CIDR conflict with the chosen subnet or insufficient IAM permissions for the service agent. Check the operation error field on /v1/{+name}/operations and verify the connector subnet has at least a /28 free range.

### Can I limit what my agent is allowed to do with the Serverless VPC Access API?

Yes. Because you self-host Jentic One, your own rules decide which operations and credentials the agent may use, and the Serverless VPC Access API carries the project and location parent in the URL path (/v1/{parent}/connectors), so a rule can pin the agent to a single project or location. You choose the operations it may call, so you can allow it to list and get connectors for a capacity or inventory review while withholding create and delete. Connector deletion is not included unless you explicitly add it, and the encrypted service-account credential is injected only at execution time rather than exposed to the agent.