Google Firebase Hosting API
41
AI ReadinessFoundational (D-)41/100
Community OpenAPI document · agent-readyCloud InfrastructureComputeoauth217 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically deploy static sites to Firebase Hosting - create versions, upload files, manage preview channels, and roll out releases.
Use for: Deploy the latest build to my Firebase Hosting site, Create a preview channel for the feature branch, I want to roll back to the previous release, List all releases on the production site
Not supported: Does not handle Firestore, Cloud Functions deploys, or Firebase Authentication - use for static site versions, releases, channels, and domain management only.
The Firebase Hosting REST API enables programmatic management and deployment of Firebase-hosted sites. It lets developers and agents create sites, manage preview channels, upload file versions, populate file content, and roll out releases. The 17 endpoints cover the full deploy lifecycle - versions, files, releases, channels, domains - and are the same surface used by the firebase-tools CLI, suitable for custom CI/CD agents and preview-environment automation.
Install Jentic One Beta
Connect the Firebase Hosting API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Firebase Hosting 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%2Ffirebasehosting.googleapis.com%2Ffirebase-hosting" | sh2
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%2Ffirebasehosting.googleapis.com%2Ffirebase-hosting" | 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 Firebase Hosting API.
Create and list Firebase Hosting sites under a project via /v1beta1/{parent}/sites
Create new versions and populate them with hashed file content via /v1beta1/{parent}:populateFiles
Roll out a version by creating a release on a site or preview channel
Manage preview channels with TTLs to share PR-style previews with stakeholders
List file manifests for a version via /v1beta1/{parent}/files
Manage custom domains attached to a site through /v1beta1/{parent}/domains
Clone an existing version into a new version for safe rollback or branching
Use Cases
Patterns agents use Firebase Hosting API for, with concrete tasks.
★ Custom CI/CD Deploys
Replace the firebase-tools CLI in CI with direct REST calls when you need fine-grained control. Create a version via POST /v1beta1/{parent}/versions, populate file hashes via /v1beta1/{parent}:populateFiles, upload missing files, finalize, then create a release. The flow integrates cleanly into bespoke pipelines and agent-driven deploys.
Create a new version for site 'my-app', populate files with the SHA256 manifest, upload missing files, finalize the version, and create a release on the live channel
Preview Channels for PR Reviews
Spin up isolated preview URLs per pull request via POST /v1beta1/{parent}/channels with a TTL. Each channel has its own release stream so reviewers see exactly the build under review without affecting production. Channels are auto-expired when their TTL elapses, removing manual cleanup.
POST /v1beta1/{parent}/channels with channelId='pr-482' and ttl='604800s', then create a release on that channel pointing to the PR build version
Safe Rollback via Version Clone
Use POST /v1beta1/{parent}/versions:clone to copy a known-good version into a new editable version, then create a release pointing to it. This avoids re-uploading files and gives rollback in seconds. Useful for incident response runbooks an agent can execute end-to-end.
POST /v1beta1/{parent}/versions:clone targeting the last known-good version, then create a release on the live channel using the cloned version
AI Agent Deploy Operations
Use Firebase Hosting through Jentic so a release agent can ship builds, open preview channels, and roll back without invoking firebase-tools. Jentic exposes the 17 REST endpoints as discoverable tools while keeping the OAuth2 access token in the vault, suitable for ChatOps deploy bots. Get started with Jentic One, the self-hosted execution layer
Through Jentic, search 'create a Firebase Hosting preview channel', load the /v1beta1/{parent}/channels schema, and execute with channelId='preview-feature-x' and ttl='86400s'
Key Endpoints
17 endpoints — the firebase hosting rest api enables programmatic management and deployment of firebase-hosted sites.
METHOD
PATH
DESCRIPTION
GET
/v1beta1/{parent}/sites
List sites under a project
POST
/v1beta1/{parent}/versions
Create a new version
POST
/v1beta1/{parent}:populateFiles
Populate file hashes for a version
POST
/v1beta1/{parent}/releases
Create a release on a channel
POST
/v1beta1/{parent}/channels
Create a preview channel
POST
/v1beta1/{parent}/versions:clone
Clone a version for rollback or branching
POST
/v1beta1/{parent}/domains
Add a custom domain to a site
GET
/v1beta1/{parent}/sites
List sites under a project
POST
/v1beta1/{parent}/versions
Create a new version
POST
/v1beta1/{parent}:populateFiles
Populate file hashes for a version
POST
/v1beta1/{parent}/releases
Create a release on a channel
POST
/v1beta1/{parent}/channels
Create a preview channel
POST
/v1beta1/{parent}/versions:clone
Clone a version for rollback or branching
POST
/v1beta1/{parent}/domains
Add a custom domain to a site
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.
F
Firebase Hosting API
- Foundational (D-)41/100
87
Foundational Compliance56
Developer Experience & Jentic Compatibility18
AI-Readiness & Agent Experience94
Agent Usability63
Security64
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
87
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
50%
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.
18
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
71%
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.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Firebase Hosting API by hand means running the Google OAuth2 flow for the right cloud-platform or firebase scope, spreading calls across 17 versioned site, version, release, and channel endpoints, and handling retries yourself. Through Jentic you install once, import Firebase Hosting from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Firebase Hosting puts the parent resource in the URL path (/v1beta1/{parent}/...), so a rule can pin your agent to one site: it can create versions and releases for that site and nothing else. You choose the operations it may call, so actions like domain creation are not included unless you add them.
Credential isolation
Your Google OAuth2 credential is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header 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 Firebase Hosting release' or 'create a preview channel', and Jentic returns the matching 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.
FAQs
Specific to using Firebase Hosting API through Jentic.
What authentication does the Firebase Hosting API use?
The API uses OAuth 2.0 (both implicit and authorization-code flows are supported in the spec). Most server agents use a service account with scopes that include `https://www.googleapis.com/auth/firebase`. Through Jentic, the access token is held in the vault and injected at execution time.
Can I create preview channels with the Firebase Hosting API?
Yes. POST /v1beta1/{parent}/channels creates a named channel with an optional TTL, and POST /v1beta1/{parent}/releases pins a version to that channel. Preview URLs are returned in the channel resource.
What are the rate limits for the Firebase Hosting API?
Firebase Hosting applies per-project quotas - typical defaults allow several deploys per minute per site. The API returns standard 429 responses; project-specific quotas are visible in the Google Cloud console under the firebasehosting.googleapis.com service.
How do I deploy a build through Jentic?
Search Jentic for 'create a Firebase Hosting version', load the /v1beta1/{parent}/versions schema, and execute against your site. Then call /v1beta1/{parent}:populateFiles, upload any missing files, finalize the version, and create a release on the live channel.
Can I rollback a Firebase Hosting deploy via the API?
Yes. Use POST /v1beta1/{parent}/versions:clone to clone a previous good version, then create a release on the live channel pointing to the cloned version. The rollback applies near-instantly.
Does the Firebase Hosting API support custom domains?
Yes. /v1beta1/{parent}/domains lists, creates, and updates custom domain mappings on a site. SSL certificates are provisioned automatically by Firebase.
Can I limit what my agent is allowed to do with the Firebase Hosting API?
Yes. Because you run Jentic One yourself, your own rules decide which of the 17 operations and which credential your agent may use. Since Firebase Hosting puts the parent resource in the URL path (/v1beta1/{parent}/...), you can pin the agent to a single site so it only creates versions and releases there, and you pick the exact operations it may call, so actions like custom domain creation via /v1beta1/{parent}/domains stay off unless you add them.
GET STARTED