Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Cloud Infrastructure / Google / Service Networking API
Service Networking API logo

Google Service Networking API

Browse all Google APIs
42
AI ReadinessFoundational (D-)42/100
See full scorecard
Official vendor OpenAPI document · agent-readyCloud InfrastructureNetworkingoauth225 EndpointsREST

For Agents

Configure private VPC peerings, allocated IP ranges, and DNS zones between Google's managed services and a consumer VPC.

Use for: Set up private services access for Cloud SQL on my VPC, Allocate a /16 internal range for a new managed service connection, List all VPC peerings my consumer project has with Google services, Delete a stale producer DNS zone

Not supported: Does not handle VPC creation, public load balancing, or general DNS administration - use for producer-consumer VPC peering, allocated ranges, and producer DNS for managed services only.

Service Networking automates the network plumbing required for managed Google Cloud services that need private connectivity into a customer's VPC, like Cloud SQL, Memorystore, and AlloyDB. The API lets you create and manage VPC peerings between a producer service and a consumer VPC, allocate private IP ranges from the consumer side, manage DNS zones for the producer service, and configure VPC Service Controls. It is the control plane behind 'Private services access' in the GCP UI.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Service Networking API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Service Networking 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%2Fservicenetworking" | sh
2

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%2Fservicenetworking" | 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 Service Networking API.

Create and update private VPC peering connections between a producer service and a consumer VPC

Allocate, list, and delete private IP ranges that producer services can use

Manage producer-side DNS zones and DNS records that resolve inside the consumer network

Configure VPC Service Controls policies on a service connection

Search and enable producer DNS routes for hybrid resolution

Track long-running operations for asynchronous network provisioning

Use Cases

Patterns agents use Service Networking API for, with concrete tasks.

★ Private Services Access for Managed Databases

Provision the VPC peering and reserved IP range that Cloud SQL, Memorystore, AlloyDB, and similar managed services need to reach customer workloads on private IPs. Service Networking creates the producer-side network, peers it with the consumer VPC, and tracks the allocated ranges so the same setup can host many service instances.

Call POST /v1/services/{serviceName}/connections with the consumer VPC network and reservedPeeringRanges set to the allocated range name.

Network Range Lifecycle Management

Allocate, expand, and reclaim private IP ranges as your portfolio of managed services grows. The API exposes addRoles and removePrivateUsedIpRange-style operations under the connections resource, plus IP range management on the consumer side, so operators can extend ranges without manually editing route tables.

Call PATCH /v1/services/{serviceName}/connections/{connectionId} with reservedPeeringRanges updated to include the new range, then poll the long-running operation.

Hybrid DNS Resolution

Configure producer-side DNS zones and records so that consumer workloads resolve managed-service hostnames inside the peered network without leaking through public DNS. Use the dnsRecordSets and dnsZones operations to add CNAMEs, manage forwarding behaviour, and audit records over time.

Call POST /v1/services/{serviceName}/projects/{projectNumber}/global/networks/{network}/dnsZones to create a private zone for the managed service domain.

AI Agent Network Provisioner

An AI agent automates network setup for new managed-service deployments - picking a non-overlapping range, creating the peering, configuring DNS, and reporting back when the long-running operation finishes. Through Jentic the agent searches for the right operation by intent and never holds the customer's GCP service account credentials directly.

Allocate a /20 range that does not collide with existing subnets, call services/{service}/connections to create the peering, then verify with services/{service}/connections.list.

Key Endpoints

25 endpoints — service networking automates the network plumbing required for managed google cloud services that need private connectivity into a customer's vpc, like cloud sql, memorystore, and alloydb.

METHOD

PATH

DESCRIPTION

POST

/v1/services/{serviceName}/connections

Create a VPC peering connection

GET

/v1/services/{serviceName}/connections

List existing connections

PATCH

/v1/services/{serviceName}/connections/{connectionId}

Update a connection's allocated ranges

POST

/v1/services/{serviceName}:addSubnetwork

Add a producer subnetwork to the connection

POST

/v1/services/{serviceName}/dnsZones:add

Add a producer DNS zone

POST

/v1/services/{serviceName}/dnsRecordSets:add

Add a DNS record set inside a producer zone

POST

/v1/services/{serviceName}/connections

Create a VPC peering connection

GET

/v1/services/{serviceName}/connections

List existing connections

PATCH

/v1/services/{serviceName}/connections/{connectionId}

Update a connection's allocated ranges

POST

/v1/services/{serviceName}:addSubnetwork

Add a producer subnetwork to the connection

POST

/v1/services/{serviceName}/dnsZones:add

Add a producer DNS zone

POST

/v1/services/{serviceName}/dnsRecordSets:add

Add a DNS record set inside a producer zone

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

Service Networking API

- Foundational (D-)
42/100
47
Foundational Compliance
56
Developer Experience & Jentic Compatibility
20
AI-Readiness & Agent Experience
94
Agent Usability
63
Security
64
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
47

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4
65%

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

25%

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.

20

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
82%

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

64

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1
64%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Google Service Networking by hand means configuring a service account, minting OAuth access tokens against servicenetworking.googleapis.com, and mapping its producer-consumer peering model yourself. Through Jentic you install once, import the Service Networking API from the API Directory, store the OAuth credential once, and your agent calls it.

Permission scoping

Service Networking puts the service name in the URL path (/v1/services/{serviceName}/connections), so a rule can pin your agent to one peered service: it can create and read connections for that service and nothing else. You choose the operations it may call, so adding subnetworks or DNS zones is not included unless you add it.

Credential isolation

Your Service Networking OAuth 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 'create a private services access connection' or 'add an allocated range', and Jentic returns the matching Service Networking operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Google Compute Engine API

→

Owns the consumer VPC networks and IP ranges that Service Networking peers into.

Use Compute Engine to create and inspect the VPC. Use Service Networking to peer it with managed services.

Complementary

Google Cloud DNS API

→

Manages broader DNS zones and records that complement Service Networking's producer-side DNS.

Use Cloud DNS for general DNS administration. Use Service Networking for DNS specific to managed-service connections.

Complementary

Google Service Management API

→

Publishes the service definitions that then use Service Networking for private connectivity.

Use Service Management to publish a service. Use Service Networking to plumb its private network access.

Alternative

Google Service Usage API

→

Manages whether services are enabled on a project, an alternative entry point for service-level admin.

Use Service Usage to flip APIs on or off. Use Service Networking when the next step is private connectivity.

FAQs

Specific to using Service Networking API through Jentic.

What authentication does the Service Networking API use?

It uses OAuth 2.0 with the cloud-platform or service.management scope and IAM permissions like roles/servicenetworking.networksAdmin on the consumer project. Through Jentic the credentials are stored encrypted in your Jentic One instance and a scoped token is provided at execution.

Which Google services use Service Networking under the hood?

Cloud SQL private IP, Memorystore for Redis, AlloyDB, Filestore, and several other managed services rely on Service Networking peerings to reach customer VPCs. The same API provisions all of them through the servicenetworking.googleapis.com producer.

What are the rate limits for the Service Networking API?

Google enforces a default per-project quota of 600 read requests per minute and 60 write requests per minute. Most write actions are long-running operations because peering and IP allocation involve VPC programming.

How do I create a private services access connection through Jentic?

Run the Jentic search query 'create a service networking connection', load POST /v1/services/{service}/connections, and execute it with the consumer network and reservedPeeringRanges. Jentic handles the OAuth token and operation polling.

Can I expand an allocated range without recreating the connection?

Yes. PATCH the connection with an updated reservedPeeringRanges list that includes the additional range. Service Networking widens the peering in place; existing service instances continue to work.

Does the API support VPC Service Controls?

Yes. The vpcServiceControls subresource on a connection lets you read and write the VPC-SC policy that governs traffic between the producer and consumer networks for that managed service.

Can I limit what my agent is allowed to do with the Service Networking API?

Yes. Because Service Networking puts the service name in the URL path, such as /v1/services/{serviceName}/connections, your self-hosted Jentic One instance can pin the agent to one peered service so it only creates and reads connections for that service. You decide which operations the agent may call, so actions like adding a subnetwork or a producer DNS zone stay off unless you allow them. The OAuth credential is stored encrypted by your own Jentic One and injected at execution, never entering the agent's prompt or logs.

GET STARTED

Start building with Service Networking API

Explore with Jentic One
View OpenAPI Document