Google Cloud Source Repositories API

Name: Cloud Source Repositories API
Brand: Cloud Source Repositories API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource Controloauth211 Endpoints

Install Jentic One Beta

Connect the Cloud Source Repositories API to your agent

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

Create a new private Git repository under a Google Cloud project

List every repository in a project, paged for large org accounts

Delete a repository when a project is decommissioned

GET STARTED

Start building with Cloud Source Repositories API

Explore with Jentic

View OpenAPI Document

For Agents

Create, list, and delete private Git repositories in Google Cloud, and manage their IAM policies. Suited for agents provisioning developer infrastructure inside a GCP project.

Use for: I want to create a new private Git repo for my GCP project, List all source repositories in a project, Delete a Cloud Source Repository that is no longer needed, Grant a teammate write access to a Cloud Source Repository

Not supported: Does not handle pull requests, code review, issue tracking, or in-browser code editing - use for managing private Git repositories and their IAM in GCP only.

Use Cases

Patterns agents use Cloud Source Repositories API for, with concrete tasks.

★ Project Bootstrap Automation

When a new GCP project is provisioned for a team, an automation creates a default Cloud Source Repository, applies an IAM policy granting the team's group push access, and configures Pub/Sub mirroring so Cloud Build can react to commits. The Cloud Source Repositories API exposes each of these steps as a discrete call, so the bootstrap script completes in under a minute.

Create repo projects/myproj/repos/app, then setIamPolicy granting roles/source.writer to group:devs@example.com, then configure projectConfig with the build-events Pub/Sub topic.

GitHub Mirror for Compliance

Mirror business-critical GitHub repositories into Cloud Source Repositories so that audit logs and IAM controls live alongside other GCP resources. Calling repos.create with a mirrorConfig block establishes the one-way mirror; subsequent IAM and listing operations make the mirrored repo discoverable inside the project.

Call POST /v1/projects/myproj/repos with mirrorConfig.url=https://github.com/org/repo and a deployKeyId.

Access Review Reporting

An access-review job iterates every repository in each project, fetches its IAM policy, and produces a report listing who has roles/source.writer or roles/source.admin. This supports periodic audits required by SOC 2 controls. The repos.list and getIamPolicy endpoints are paginated and IAM-scoped, so the report can run unattended.

List all repos in projects/myproj, then for each call getIamPolicy and emit a row per binding.

AI Agent Repo Provisioning

An AI agent assigned to set up a new microservice asks Jentic for the operation that creates a Google source repository, loads the schema, then creates the repo and grants the requesting team push access - all without human intervention. Jentic handles the OAuth credential exchange so the agent never sees the underlying token.

Search Jentic for 'create a Google Cloud source repository', execute repos.create with the project parent, then setIamPolicy adding the new service team.

Key Endpoints

11 endpoints — the cloud source repositories api manages private git repositories hosted in a google cloud project.

METHOD

PATH

DESCRIPTION

POST

/v1/{+parent}/repos

Create a new repository in a project

GET

/v1/{+parent}/repos

List repositories in a project

GET

/v1/{+name}

Get a single repository or project resource

POST

/v1/{+name}:sync

Synchronise a mirrored repository

POST

/v1/{+resource}:setIamPolicy

Set the IAM policy on a repository

POST

/v1/{+resource}:getIamPolicy

Get the IAM policy on a repository

POST

/v1/{+resource}:testIamPermissions

Test which permissions the caller holds on a repository

POST

/v1/{+parent}/repos

Create a new repository in a project

GET

/v1/{+parent}/repos

List repositories in a project

GET

/v1/{+name}

Get a single repository or project resource

POST

/v1/{+name}:sync

Synchronise a mirrored repository

POST

/v1/{+resource}:setIamPolicy

Set the IAM policy on a repository

Why Jentic?

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

Credential isolation

Your Cloud Source Repositories 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 Cloud Source repository' or 'set IAM policy on a Git repo', and Jentic returns the matching Cloud Source Repositories operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Cloud Source Repositories API through Jentic.

What authentication does the Cloud Source Repositories API use?

The Cloud Source Repositories API uses OAuth 2.0 with the cloud-platform or source.read_write scopes. Through Jentic, OAuth credentials are stored in your Jentic One instance and exchanged for short-lived access tokens, so service-account keys never enter the agent context.

Can I mirror a GitHub repository into Cloud Source Repositories?

Yes. Pass a mirrorConfig block when calling POST /v1/projects/{project}/repos that specifies the source URL plus a deployKeyId and webhookId. Cloud Source Repositories then maintains a one-way mirror of the upstream GitHub or Bitbucket repository.

What are the rate limits for the Cloud Source Repositories API?

Quotas are set at the Google Cloud project level - typically a few hundred read or write requests per minute, with stricter limits on repo creation. Quotas can be inspected and adjusted in the Google Cloud Console under IAM and admin > Quotas.

How do I provision a new repo with IAM bindings through Jentic?

Search Jentic for 'create a Google Cloud source repository', execute the repos.create operation against POST /v1/{+parent}/repos, then call POST /v1/{+resource}:setIamPolicy on the new repo resource with the desired role bindings. Jentic returns the schemas for both calls so the agent can chain them in a single workflow.

Is the Cloud Source Repositories API free?

Cloud Source Repositories includes a free tier of up to 5 project users and 50 GB storage. Beyond that, Google charges per active user per month and per GB of storage. The API itself has no separate per-call charge.

Can I check if a service account can push to a repo before attempting?

Yes. POST /v1/{+resource}:testIamPermissions accepts a list of permissions like source.repos.update or source.repos.create and returns which of those the calling identity holds, which lets agents decide whether to attempt the operation or escalate.

Can I limit what my agent is allowed to do with the Cloud Source Repositories API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. Since Cloud Source Repositories puts the repository in the URL path, such as /v1/{name} and /v1/{resource}:setIamPolicy, you can pin the agent to a single repo and allow only the calls it needs, for example creating, reading, and syncing that repo. Operations like setIamPolicy stay off limits unless you explicitly add them, so the agent cannot change access controls on its own.

Google Cloud Source Repositories API

Connect the Cloud Source Repositories API to your agent

Capabilities

Start building with Cloud Source Repositories API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs