Google Cloud Storage for Firebase API
Browse all Google APIs✓ Official Vendor SpecStorageObject Storageoauth26 EndpointsREST
For Agents
Link, list, and unlink Google Cloud Storage buckets for use in Firebase projects, and provision a default bucket. Designed for project-level configuration of Firebase storage.
Use for: Link an existing Cloud Storage bucket to my Firebase project, Provision the default storage bucket for a new Firebase app, List all Cloud Storage buckets attached to a Firebase project, Get metadata for a Firebase-linked bucket
Not supported: Does not handle file uploads, downloads, or object-level ACLs — use the Cloud Storage API for object operations and this API only for Firebase project linkage.
The Cloud Storage for Firebase API enables programmatic management of Cloud Storage buckets used by Firebase projects. It links existing Google Cloud Storage buckets to a Firebase project, creates default buckets, and removes Firebase access from buckets when needed. This management API complements the client SDKs that perform actual upload and download operations against linked buckets.
Install Jentic One Beta
Connect the Cloud Storage for Firebase API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Storage for Firebase 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 Cloud Storage for Firebase API.
Link an existing Cloud Storage bucket to a Firebase project with addFirebase
Provision a default storage bucket for a Firebase project
List Cloud Storage buckets linked to a given Firebase project
Retrieve metadata for a single linked bucket
Remove Firebase access from a Cloud Storage bucket with removeFirebase
Use Cases
Patterns agents use Cloud Storage for Firebase API for, with concrete tasks.
★ Provision Storage for a New Firebase App
When standing up a new Firebase project, provision the default Cloud Storage bucket so the Firebase client SDKs can upload user content immediately. This API call creates the default bucket binding so mobile and web SDKs can write images, videos, and files without additional setup. The whole step takes a single POST and is typically scripted as part of project bootstrap.
Call POST /v1beta/projects/{project}/defaultBucket on a freshly created Firebase project and confirm the default bucket name in the response.
Link Additional Buckets to a Firebase Project
Teams often have multiple Cloud Storage buckets for different content classes (user uploads, public assets, backups). Use addFirebase to link any existing bucket to a Firebase project so Firebase Security Rules and client SDKs can access it. The bucket data itself is unchanged; only the Firebase association is added.
Call POST /v1beta/projects/{project}/buckets/{bucket}:addFirebase to link a named GCS bucket to the Firebase project and verify it appears in the buckets list.
Audit Firebase-Linked Storage
Security and compliance reviews need an inventory of which buckets are linked to which Firebase projects. List buckets per project to produce that inventory and detect drift. The GET buckets endpoint returns every bucket associated with a project, supporting audit workflows without scraping the Firebase console.
Call GET /v1beta/projects/{project}/buckets, paginate through results, and produce a list of bucket names linked to the project.
Agent-Managed Firebase Storage Configuration
An AI agent triggered by an internal platform request can provision and link Cloud Storage buckets for new Firebase projects through Jentic. The agent searches for the operation, loads its schema, and executes addFirebase or defaultBucket calls without the developer ever holding the underlying OAuth credentials. This converts a multi-step Cloud Console workflow into a single agent invocation.
Use Jentic to search 'link a cloud storage bucket to firebase', load the addFirebase operation schema, and execute it for a target project and bucket pair.
Key Endpoints
6 endpoints — the cloud storage for firebase api enables programmatic management of cloud storage buckets used by firebase projects.
METHOD
PATH
DESCRIPTION
POST
/v1beta/{+bucket}:addFirebase
Link an existing Cloud Storage bucket to a Firebase project
POST
/v1beta/{+bucket}:removeFirebase
Remove Firebase access from a bucket
GET
/v1beta/{+parent}/buckets
List buckets linked to a Firebase project
GET
/v1beta/{+name}
Get a single linked bucket
POST
/v1beta/{+parent}/defaultBucket
Create the default bucket for a Firebase project
POST
/v1beta/{+bucket}:addFirebase
Link an existing Cloud Storage bucket to a Firebase project
POST
/v1beta/{+bucket}:removeFirebase
Remove Firebase access from a bucket
GET
/v1beta/{+parent}/buckets
List buckets linked to a Firebase project
GET
/v1beta/{+name}
Get a single linked bucket
POST
/v1beta/{+parent}/defaultBucket
Create the default bucket for a Firebase project
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Google OAuth 2.0 service account credentials live encrypted in the Jentic vault. Agents receive scoped access tokens with the cloud-platform scope, never raw keys.
Intent-based discovery
Agents search by intent ('link a bucket to firebase') and Jentic returns the addFirebase or defaultBucket operation with its schema, so the call can be executed without reading the Firebase docs.
Time to first call
Direct setup of Google OAuth, scopes, and the firebasestorage discovery client takes 1-2 days. Through Jentic: under 30 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Cloud Storage for Firebase API through Jentic.
What authentication does the Cloud Storage for Firebase API use?
It uses Google OAuth 2.0 with the Cloud Platform scope. Through Jentic, the OAuth credentials are stored encrypted in the Jentic vault and the agent receives a scoped access token, so raw service account keys never enter the agent context.
Can I upload files with this API?
No. This API only manages the link between Cloud Storage buckets and Firebase projects. File uploads and downloads happen through the Firebase client SDKs or the underlying Cloud Storage JSON API against the linked bucket.
What are the rate limits for the Cloud Storage for Firebase API?
Google enforces standard per-project quotas on Firebase management APIs, typically a few hundred requests per minute. These management calls are infrequent compared to runtime traffic, so the limits rarely bind in practice.
How do I link an existing bucket to Firebase through Jentic?
Search Jentic for 'link a cloud storage bucket to firebase', load the schema for POST /v1beta/{bucket}:addFirebase, and execute it with the project and bucket identifiers. Jentic handles OAuth and returns the linked bucket resource.
Is the Cloud Storage for Firebase API free?
The management API itself has no charge. Storage and bandwidth on the linked Cloud Storage buckets are billed under Firebase Storage and Google Cloud Storage pricing.
What happens when I call removeFirebase on a bucket?
The bucket is unlinked from the Firebase project so Firebase Security Rules and client SDKs can no longer access it. The bucket and its objects remain intact in Google Cloud Storage.
GET STARTED