Google Firebase Hosting API
Browse all Google APIs40
AI ReadinessNon-Ready (F)40/100
Official vendor OpenAPI document · agent-readyCloud InfrastructureNetworkingoauth23 EndpointsREST
For Agents
Track and clean up long-running Firebase Hosting operations such as custom domain provisioning so an agent can manage Hosting deploys without manual console work.
Use for: List Firebase Hosting long-running operations under a site, Cancel a stuck custom domain provisioning operation, Find all completed Firebase Hosting operations for a custom domain, Check whether a Hosting operation has finished
Not supported: Does not deploy releases, finalise versions, or manage channels directly in this v1 surface - use for tracking, cancelling, and pruning Firebase Hosting long-running operations only.
The Firebase Hosting REST API enables programmatic management of long-running operations behind Firebase Hosting sites and channels, including custom domain provisioning workflows. The v1 surface exposes operations to list, cancel, and delete the long-running operation resources spawned by deploys, channel creation, and custom domain setup. Use it to monitor and tidy up asynchronous Hosting jobs from automation pipelines.
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%2Fgoogleapis.com%2Ffirebasehosting" | 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%2Fgoogleapis.com%2Ffirebasehosting" | 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.
List long-running Firebase Hosting operations under a site or custom domain
Cancel an in-flight Firebase Hosting custom domain operation
Delete a completed Firebase Hosting operation resource
Monitor the state of asynchronous custom domain provisioning jobs
Reconcile Hosting operation history during pipeline troubleshooting
Use Cases
Patterns agents use Firebase Hosting API for, with concrete tasks.
★ Custom Domain Provisioning Monitoring
Provisioning a custom domain on Firebase Hosting kicks off a long-running operation. The Hosting v1 API lets pipelines list and inspect those operations under projects/{project}/sites/{site}/customDomains/{domain}/operations to confirm SSL issuance and DNS verification have completed before flipping traffic. Polling integration with a deploy pipeline takes a few hours.
Call GET /v1/{+name} on a Hosting custom-domain operation resource and check that done is true and error is unset before proceeding to flip DNS to the Hosting site.
Cancelling Stuck Custom Domain Setup
When a Firebase Hosting custom domain operation hangs because of DNS misconfiguration or repeated SSL issuance failures, the API supports cancelling the operation via POST /v1/{+name}:cancel. This frees up the underlying resource so engineers can retry the operation cleanly with the corrected DNS records.
Call POST /v1/{+name}:cancel on the in-flight custom domain operation and verify via GET /v1/{+name} that the operation now reports done with a cancellation status.
Operation History Cleanup
Old Firebase Hosting operation resources accumulate as deploys and domain changes happen over time. DELETE /v1/{+name} removes a completed operation record to keep the operations list focused on recent activity. This is a low-frequency hygiene task suited to weekly maintenance runs.
Call DELETE /v1/{+name} on an operation that has been done=true for over 30 days to prune the operation history under a customDomains resource.
Agent-Driven Hosting Pipeline Monitoring via Jentic
An AI agent connected through Jentic can watch Firebase Hosting deploys and custom domain operations on behalf of a release engineer, surfacing failures and cancelling stuck operations as needed. Jentic exposes the 3 Hosting v1 operation endpoints, the agent strings them together, and OAuth credentials stay sealed inside your Jentic One instance.
Through Jentic, search for monitor firebase hosting operations, load the operations.list endpoint, and execute it for projects/PROJECT/sites/SITE/customDomains/DOMAIN to surface any operations whose done flag is still false after one hour.
Key Endpoints
3 endpoints — the firebase hosting rest api enables programmatic management of long-running operations behind firebase hosting sites and channels, including custom domain provisioning workflows.
METHOD
PATH
DESCRIPTION
GET
/v1/{+name}
List Firebase Hosting operations under a resource
POST
/v1/{+name}:cancel
Cancel a Firebase Hosting long-running operation
DELETE
/v1/{+name}
Delete a Firebase Hosting operation resource
GET
/v1/{+name}
List Firebase Hosting operations under a resource
POST
/v1/{+name}:cancel
Cancel a Firebase Hosting long-running operation
DELETE
/v1/{+name}
Delete a Firebase Hosting operation resource
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
- Non-Ready (F)40/100
71
Foundational Compliance56
Developer Experience & Jentic Compatibility18
AI-Readiness & Agent Experience94
Agent Usability63
Security38
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
71
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
85%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
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
74%
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).
38
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: FSignals: 1
38%
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 standing up Google OAuth 2.0 with a service account and polling the long-running operation resources to track, cancel, and prune them. Through Jentic you install once, import the Firebase Hosting API from the API Directory, store the service-account credential once, and your agent calls it.
Permission scoping
This v1 surface acts on operation resources named in the URL path (/v1/{name}, /v1/{name}:cancel), so a rule can pin your agent to one operation and nothing else. You choose the operations it may call, so ones like cancel or delete are not included unless you add them.
Credential isolation
Your Google service-account 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 'monitor a Firebase Hosting operation' or 'cancel a hosting operation', 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 Google OAuth 2.0 with the firebase or cloud-platform scope. Through Jentic the OAuth credentials are stored in the encrypted vault and a scoped access token is supplied per request without exposing the underlying service-account key.
Can I deploy a new release with the v1 Firebase Hosting API endpoints exposed here?
No. The v1 endpoints in this spec cover long-running operation management only - list, cancel, and delete. Release deployment, version finalisation, and channel creation are handled in the broader Firebase Hosting REST surface and the firebase CLI; this spec is the operations-monitoring surface.
What are the rate limits for the Firebase Hosting API?
Google enforces standard googleapis.com per-project read and write quotas. Operation listing is a low-cost read endpoint, and pipelines that poll frequently should respect the per-minute project quota with backoff between polls.
How do I monitor a Firebase Hosting custom domain operation through Jentic?
Run pip install jentic, search for monitor firebase hosting operations, load the operations.list endpoint, and execute it for projects/PROJECT/sites/SITE/customDomains/DOMAIN/operations. Get started with Jentic One, the self-hosted execution layer.
Does the Firebase Hosting API support cancelling stuck custom domain operations?
Yes. POST /v1/{+name}:cancel on the operation resource cancels the in-flight job. After cancellation the operation reports done=true with a cancellation status, allowing pipelines to retry custom domain setup with corrected DNS or verification records.
Is the Firebase Hosting API free?
Firebase Hosting is included with Firebase under standard free-tier limits. Bandwidth and storage above those limits are billed under the Hosting price list; the operations endpoints themselves do not incur additional charges.
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 this API's operations the agent may call, so you can grant read-only listing of long-running operations while withholding the cancel and delete actions. Each operation acts on a resource named in the URL path, such as /v1/{name} or /v1/{name}:cancel, so a rule can pin the agent to a single operation resource and nothing else. Your Google service-account credential stays with your own instance and is supplied per request, never entering the agent's prompt or context.
GET STARTED