Google Serverless VPC Access API
Browse all Google APIs41
AI ReadinessFoundational (D-)41/100
Official vendor OpenAPI document · agent-readyCloud InfrastructureNetworkingoauth27 EndpointsREST
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.
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.
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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fvpcaccess" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fvpcaccess" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
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
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 your Jentic One instance 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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
S
Serverless VPC Access API
- Foundational (D-)41/100
71
Foundational Compliance56
Developer Experience & Jentic Compatibility18
AI-Readiness & Agent Experience94
Agent Usability63
Security68
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
71
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
85%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
18
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
71%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
68
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B+Signals: 1
68%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
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 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.
GET STARTED