Google Looker (Google Cloud core) API

Name: Looker (Google Cloud core) API
Brand: Looker (Google Cloud core) API
Availability: InStock

✓ Official Vendor SpecAnalyticsBusiness Intelligenceoauth211 Endpoints

Install Jentic One Beta

Connect the Looker (Google Cloud core) API to your agent

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

Provision and delete Looker instances within a Google Cloud project location

Restart a running Looker instance to apply configuration changes

Export instance configuration for backup or migration via the export operation

GET STARTED

Start building with Looker (Google Cloud core) API

Explore with Jentic

View OpenAPI Document

For Agents

Provision and manage Looker (Google Cloud core) instance lifecycle: create instances, restart them, export and import configuration, and track long-running operations.

Use for: Provision a new Looker (Google Cloud core) instance in europe-west1, Restart an existing Looker instance to apply pending changes, Export the configuration of a Looker instance for backup, Import a previously exported Looker configuration into a fresh instance

Not supported: Does not handle Looker dashboards, queries, looks, or user content — use for instance provisioning, restart, export, import, and deletion only.

Use Cases

Patterns agents use Looker (Google Cloud core) API for, with concrete tasks.

★ Looker instance provisioning

Provision Looker (Google Cloud core) instances as part of an infrastructure-as-code workflow, specifying the region, OAuth client credentials, and platform edition. The API returns a long-running operation handle that resolves to the new instance once setup completes, typically taking 30-60 minutes.

Create a Looker instance named bi-prod in projects/acme/locations/europe-west1 with the LOOKER_CORE_STANDARD platform edition and poll the returned operation until done

Configuration export and migration

Export a Looker instance's configuration to Cloud Storage and import it into another instance to clone environments, migrate between regions, or seed a disaster-recovery instance. The export and import operations are long-running and surface their progress through the operations resource.

Trigger export on instance bi-staging targeting gs://acme-bi-backups/looker/2026-06.tar.gz and wait for the operation to complete

Lifecycle automation in CI/CD

Automate Looker instance restarts and deletions from a CI/CD pipeline so that ephemeral test environments are torn down on schedule and production instances are restarted for maintenance windows. The operations resource lets pipelines cancel runs that exceed their budget.

Restart instance projects/acme/locations/us-central1/instances/bi-prod and abort if the returned operation has not finished within 20 minutes

Agent integration via Jentic

AI agents managing Google Cloud analytics estates can use the Looker control-plane API through Jentic to spin up review instances, restart them after configuration changes, or clean up unused instances on a schedule, without holding the underlying OAuth refresh token in their prompt.

List all Looker instances in projects/acme older than 30 days with no recent operations and queue a delete request for each

Key Endpoints

11 endpoints — the looker (google cloud core) api manages the lifecycle of looker instances hosted as a google cloud service, including provisioning, restart, import, export, and deletion.

METHOD

PATH

DESCRIPTION

GET

/v1/{+parent}/instances

List Looker instances in a project location

DELETE

/v1/{+name}

Delete a Looker instance

POST

/v1/{+name}:restart

Restart a Looker instance

POST

/v1/{+name}:export

Export instance configuration

POST

/v1/{+name}:import

Import instance configuration

POST

/v1/{+name}:cancel

Cancel a long-running operation

GET

/v1/{+name}/locations

List supported locations

GET

/v1/{+name}/operations

List long-running operations

GET

/v1/{+parent}/instances

List Looker instances in a project location

DELETE

/v1/{+name}

Delete a Looker instance

POST

/v1/{+name}:restart

Restart a Looker instance

POST

/v1/{+name}:export

Export instance configuration

POST

/v1/{+name}:import

Import instance configuration

Why Jentic?

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

Credential isolation

Google Cloud OAuth 2.0 client credentials and refresh tokens are stored encrypted in the Jentic vault. Agents receive short-lived bearer tokens scoped to cloud-platform; raw secrets never enter the agent's context.

Intent-based discovery

Agents search by intent such as provision looker instance or restart looker and Jentic returns the matching control-plane operations with input schemas, so the agent does not have to read Google Cloud's discovery documents.

Time to first call

Direct integration takes a day or more for OAuth setup, long-running operation polling, and error handling. Through Jentic the same calls take under an hour: search, load schema, execute, poll the returned operation.

FAQs

Specific to using Looker (Google Cloud core) API through Jentic.

What authentication does the Looker (Google Cloud core) API use?

The control-plane API uses Google OAuth 2.0 with the https://www.googleapis.com/auth/cloud-platform scope. Through Jentic, the OAuth credentials are held in the encrypted vault and the agent receives only a scoped bearer token, so the refresh token never enters the agent's context.

Can I provision a Looker instance through this API?

Yes, instances are created as a long-running operation under projects/{project}/locations/{location}/instances. The call returns an operation handle which you poll on /v1/{+name}/operations until the new instance is ready.

What are the rate limits for the Looker (Google Cloud core) API?

Quotas are managed per Google Cloud project under the Looker API service in the Cloud Console quotas page. Most lifecycle calls are subject to default per-minute and per-day quotas; concurrent long-running operations per project are also capped.

How do I restart a Looker instance through Jentic?

Search Jentic for restart looker instance, load the operation that maps to /v1/{+name}:restart, and execute with the instance resource path. Jentic injects the OAuth bearer token and returns the long-running operation that you can poll until done.

Is the Looker (Google Cloud core) API free?

The control-plane API itself does not have separate charges, but Looker (Google Cloud core) instances are billed per platform edition and per active user. See Google Cloud's Looker pricing page for current rates.

Does this API let me run Looker queries or load dashboards?

No, this is the control-plane API for instance lifecycle only. Running queries, fetching dashboards, and managing looks happen via the in-instance Looker SDK on the running instance, not through this API.

Google Looker (Google Cloud core) API

Connect the Looker (Google Cloud core) API to your agent

Capabilities

Start building with Looker (Google Cloud core) API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs