Google Cloud SQL Admin API

Name: Cloud SQL Admin API
Brand: Cloud SQL Admin API
Availability: InStock

✓ Official Vendor SpecStorageDatabaseoauth268 EndpointsREST

For Agents

Provision and operate managed MySQL, PostgreSQL, and SQL Server instances on Google Cloud. Run backups, manage databases and users, and orchestrate import and export from the v1 admin surface.

Install Jentic One Beta

Connect the Cloud SQL Admin API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud SQL Admin 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 Cloud SQL Admin API.

Create, list, update, and delete managed Cloud SQL instances across MySQL, PostgreSQL, and SQL Server

Take on-demand backups and list scheduled backup runs for an instance

Manage databases, users, and SSL certificates on each instance

GET STARTED

Start building with Cloud SQL Admin API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Cloud SQL Admin API for, with concrete tasks.

★ Postgres Instance Provisioning

Provision a new Cloud SQL Postgres instance with a chosen tier, region, HA setting, and backup window for a service team. The Admin v1 API exposes instance creation as a long-running operation under /v1/projects/{project}/instances. Combined with calls to create the initial database and an application user, the full setup completes in a few minutes.

POST /v1/projects/myproj/instances with databaseVersion=POSTGRES_15, settings.tier=db-custom-2-7680, settings.availabilityType=REGIONAL.

Nightly Logical Export

Run nightly logical exports of a production Cloud SQL database to a Cloud Storage bucket for offsite retention. The export endpoint accepts a gs:// URI, a list of databases, and SQL or CSV format. Each export is a long-running operation that can be polled until done.

POST /v1/projects/myproj/instances/prod/export with exportContext.uri=gs://backups/prod-2026-06-10.sql.gz and databases=['app_db'].

Failover Drill

Trigger a controlled failover from the primary instance to its replica to validate the recovery path. The Admin v1 API exposes failover and switchover endpoints that return long-running operations, letting the agent confirm completion before redirecting application traffic.

POST /v1/projects/myproj/instances/prod/failover, then poll the returned operation until done.

AI Agent Database Onboarding

An AI agent setting up a new microservice creates a Cloud SQL instance, then a database and an application-scoped user. Through Jentic, the agent searches for the create operations, loads each schema, and executes them in order — the entire onboarding fits inside a single agent reasoning loop.

Search Jentic for 'create a Cloud SQL instance', execute the create call, then chain databases.insert and users.insert against the new instance.

Key Endpoints

68 endpoints — the cloud sql admin api (v1) is the generally available administration surface for managed mysql, postgresql, and sql server instances on google cloud.

METHOD

PATH

DESCRIPTION

GET

/v1/projects/{project}/instances

List Cloud SQL instances in a project

GET

/v1/projects/{project}/instances/{instance}

Get a single Cloud SQL instance

POST

/v1/projects/{project}/instances/{instance}/clone

Clone an instance, optionally to a point in time

GET

/v1/projects/{project}/instances/{instance}/backupRuns

List backup runs for an instance

POST

/v1/projects/{project}/instances/{instance}/acquireSsrsLease

Acquire an SSRS lease on a SQL Server instance

GET

/v1/projects/{project}/instances/{instance}/connectSettings

Read connection settings for an instance

GET

/v1/flags

List supported instance flags

GET

/v1/projects/{project}/instances

List Cloud SQL instances in a project

GET

/v1/projects/{project}/instances/{instance}

Get a single Cloud SQL instance

POST

/v1/projects/{project}/instances/{instance}/clone

Clone an instance, optionally to a point in time

GET

/v1/projects/{project}/instances/{instance}/backupRuns

List backup runs for an instance

POST

/v1/projects/{project}/instances/{instance}/acquireSsrsLease

Acquire an SSRS lease on a SQL Server instance

Why Jentic?

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

Credential isolation

Cloud SQL Admin OAuth credentials are stored in the Jentic vault (MAXsystem) and exchanged for scoped, short-lived access tokens on each call. Service-account JSON keys never enter the agent context.

Intent-based discovery

Agents search Jentic with intents like 'create a Cloud SQL instance' or 'export a Cloud SQL database', and Jentic returns the matching v1 operation along with its request schema.

Time to first call

Direct Cloud SQL Admin v1 integration: 1-2 days to wire OAuth, long-running operation polling, and the instance settings schema. Through Jentic: under 1 hour for discover, schema-load, and execute.

FAQs

Specific to using Cloud SQL Admin API through Jentic.

What authentication does the Cloud SQL Admin API use?

The Cloud SQL Admin API uses OAuth 2.0 with the cloud-platform or sqlservice.admin scope. Through Jentic, OAuth credentials are stored in the Jentic vault (MAXsystem) and exchanged for short-lived access tokens, so service-account JSON keys never enter the agent context.

Can I create a SQL Server instance with this API?

Yes. POST /v1/projects/{project}/instances accepts databaseVersion values including SQLSERVER_2019_STANDARD and SQLSERVER_2019_ENTERPRISE. SQL Server-specific operations like acquireSsrsLease are exposed at /v1/projects/{project}/instances/{instance}/acquireSsrsLease.

What is the difference between this v1 surface and v1beta4?

The v1 path (/v1) is the generally available admin surface and is the recommended target for new integrations. The /sql/v1beta4 surface remains supported for tooling that already calls it but receives slower feature updates than v1.

What are the rate limits for the Cloud SQL Admin API?

Admin API quotas default to a few hundred requests per minute per project, with stricter limits on instance creation and import/export operations. Quotas are visible and adjustable in the Google Cloud Console under IAM and admin > Quotas.

How do I take a backup through Jentic?

Search Jentic for 'back up a Cloud SQL instance', load the backupRuns.insert schema, and execute POST /v1/projects/{project}/instances/{instance}/backupRuns. Jentic returns the long-running operation handle so the agent can poll until the backup is done.

Is the Cloud SQL Admin API free?

The Admin API itself has no per-call charge. Cloud SQL costs come from the underlying instance compute, storage, and backup retention, billed per hour and per GB.

Google Cloud SQL Admin API

Connect the Cloud SQL Admin API to your agent

Capabilities

Start building with Cloud SQL Admin API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs