Google Serverless VPC Access API

Name: Serverless VPC Access API
Brand: Serverless VPC Access API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureNetworkingoauth27 Endpoints

Install Jentic One Beta

Connect the Serverless VPC Access API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Serverless VPC Access API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Serverless VPC Access API.

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

GET STARTED

Start building with Serverless VPC Access API

Explore with Jentic

View OpenAPI Document

For Agents

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

Use for: I need to create a VPC Access connector in us-central1, List every VPC Access connector in our project, Get the IP range and throughput of an existing connector, Delete an unused VPC Access connector

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

Use Cases

Patterns agents use Serverless VPC Access API for, with concrete tasks.

★ 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.

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.

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.

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 the MAXsystem vault and exposes only a scoped reference.

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

Key Endpoints

7 endpoints — 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.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Serverless VPC Access OAuth tokens with the cloud-platform scope are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw OAuth tokens never enter the agent's context, which matters because the cloud-platform scope grants broad project-level networking access.

Intent-based discovery

Agents search Jentic with intents like 'create a vpc access connector' and Jentic returns the create-connector operation with its full input schema, including throughput min/max and CIDR fields, so the agent can construct a valid request without reading Google's discovery doc.

Time to first call

Direct VPC Access integration: 1-2 days for OAuth setup, region and CIDR planning, and long-running operation handling. Through Jentic: under 1 hour — search, load schema, execute and poll.

FAQs

Specific to using Serverless VPC Access API through Jentic.

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 the MAXsystem vault 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.