# AX Check: firebase.google.com Checked 2026-09-18. Firebase setup and pricing are clear, but no quick-read guide exists Docs, CLI, MCP server and pricing tables are all directly usable. But there's no llms.txt or Markdown version of the homepage for fast agent scanning. ## Onboarding needs a login ## Coding sessions Two of three independent agent sessions finished the task: both found clear Firestore pricing, citing Spark's free quotas versus Blaze's pay-as-you-go rates with regional caveats. The third session did not complete. ### DeepSeek V4 Pro [View public run](https://agents.withgauge.com/p/runs/451e75a5-7820-4e88-9770-e2f0164703bc) · [Read transcript](https://www.ax-check.com/firebase.google.com/sessions/deepseek.json) Final output gives a pricing table (reads/writes/deletes/storage) fetched from cloud.google.com/firestore/pricing (seq 18) and names assumptions: Standard edition, us-central1 default region, Spark vs Blaze plan, free daily quota. #### End-to-end onboarding - **Onboarding needs a login**: Agent scaffolded a Firebase Admin SDK example and installed dependencies successfully, but never obtained real Firebase/Google Cloud credentials. Running the app exited at a self-authored credential check since GOOGLE_APPLICATION_CREDENTIALS was never set. No Firestore project, service account, or authenticated operation against the hosted product was created or executed; the agent states it has no Google Cloud/Firebase credentials and that creating a project/service-account key requires the user's Google account in the console. Event 44: ```text Missing GOOGLE_APPLICATION_CREDENTIALS. Export it to the path of a Firebase Admin service-account JSON key. Example: export GOOGLE_APPLICATION_CREDENTIALS="./service-account.json" exit code: 1 ``` Event 46: ```text I **cannot run this against the hosted product from here**: Firebase has no unauthenticated hosted sandbox, and I have no Google Cloud/Firebase credentials in this environment. Creating a project and a service-account key requires your Google account in the console, which I can't do for you. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-service way to create a Firebase project or service account**: Firebase/Firestore requires a Google account login through the console to create a project, enable Firestore, and generate a service-account key. This is normal product authentication behavior, not a defect — the agent correctly identified it cannot complete this step without human/browser-based Google login, and stopped rather than faking success. Event 46: ```text Creating a project and a service-account key requires your Google account in the console, which I can't do for you. ``` - **Example never actually ran against Firestore**: The written index.js exits at a manual credential check the agent itself added, because no GOOGLE_APPLICATION_CREDENTIALS were available. This is a direct consequence of the credential blocker above, not a separate agent or product error — the agent disclosed this plainly instead of claiming success. Event 44: ```text Missing GOOGLE_APPLICATION_CREDENTIALS. Export it to the path of a Firebase Admin service-account JSON key. ``` #### Suggested Changes - **Add a CLI-based path to provision a Firestore project without the web console**: The agent needed to visit console.firebase.google.com manually to create a project, enable Firestore, and download a service-account key, per the setup steps it wrote into README.md. If a CLI command (firebase CLI login/init or gcloud) could provision a minimal test project and key non-interactively, agent-driven onboarding could complete end-to-end. Verify by having an agent run that CLI flow and confirm it can reach an authenticated Firestore read/write without console clicks. Event 26: ```text 1. Create a Firebase project at . 2. Create a Firestore database: **Build > Firestore Database > Create database** ``` ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/de68f5f1-0048-4f9e-81ac-3d11274e8e99) · [Read transcript](https://www.ax-check.com/firebase.google.com/sessions/kimi.json) Final output gives Spark (free, quota-based) vs Blaze (pay-as-you-go, ~cents/100K ops + $0.18/GiB-month) figures and flags they vary by region/time, tying the $0 figure to the Spark plan for this demo. #### End-to-end onboarding - **Onboarding needs a login**: Agent checked the sandbox for gcloud/firebase CLI and any Google/Firebase credentials, found none, and could not self-provision a Firebase project (which requires Google account sign-in). It wrote a Firestore example locally but never obtained real credentials or ran an authenticated operation against a hosted Firebase project. It explicitly asked the human to create a project and supply config values before it could proceed. Event 5: ```text which gcloud firebase node npm 2>/dev/null; echo "---"; gcloud auth list 2>&1 | head -5; echo "---"; env | grep -iE 'google|gcp|firebase|gcloud' | sed 's/=.*/=/' ``` Event 9: ```text ls ~/.config/gcloud 2>/dev/null; ls ~/.firebase* 2>/dev/null; find / -maxdepth 3 -name "*.json" -path "*key*" 2>/dev/null | head; echo "done" ``` Event 12: ```text this sandbox has Node/npm but no `gcloud`/`firebase` CLI and, critically, no Google credentials (no OAuth token, no service account key, no Firebase project config)... There's no unauthenticated entry point, so I can't run anything end-to-end here. ``` Event 21: ```text To unblock me: create a project at console.firebase.google.com, register a web app, enable Firestore in test mode, and paste the config into `/sandbox/repo/firebase-example/.env`. Then I can run and extend the example. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No Google/Firebase credentials available in sandbox**: The sandbox had no gcloud or firebase CLI installed and no Google OAuth token, service account key, or Firebase project config present. This is a missing-credentials blocker inherent to Firebase's provisioning model (project creation requires a human Google account sign-in), not a product defect. The agent correctly identified this and stopped short of running the example end-to-end, instead scaffolding the code and instructions for a human to finish setup. Event 6: ```text /usr/local/bin/node /usr/local/bin/npm --- /bin/bash: line 1: gcloud: command not found --- ``` Event 10: ```text done ``` Event 12: ```text no Google credentials (no OAuth token, no service account key, no Firebase project config). Every Firebase developer workflow — even the hosted SDK path — starts with a Google account ``` #### Suggested Changes - **Add a self-service/CLI path for provisioning a demo Firebase project without console sign-in**: Observed friction: the agent could not proceed past project creation because Firebase requires human sign-in at console.firebase.google.com to get an apiKey/projectId, even for a minimal Firestore demo. If a scripted or service-account based project bootstrap flow exists, surface it more prominently in quickstart docs so agentic/CI workflows can self-provision. Verify by having a fresh agent session attempt project creation via CLI/API using only a service account credential and confirming it can reach an authenticated Firestore read/write without a browser step. Event 12: ```text you create a project in the Firebase console (or via the Firebase Management API with an OAuth token), register an app, and get an `apiKey`/`projectId` config. There's no unauthenticated entry point ``` ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/0a4a662a-a992-42e6-a1d8-83dfc4167167) · [Read transcript](https://www.ax-check.com/firebase.google.com/sessions/qwen.json) #### End-to-end onboarding - **Onboarding needs a login**: The agent scanned the sandbox for existing Firebase/GCP credentials, service account files, and environment variables and found none. There is no self-service flow shown to create a Firebase project or obtain an API key from within the sandbox (this would require a human to sign into the Firebase console). The agent built the SDK wiring and confirmed it locally, but the live demo path explicitly failed with 'Missing Firebase config' because no real project credentials exist, so no authenticated operation against the hosted Firestore service was ever performed. Event 5: ```text ls -a ~ 2>&1; echo "--- credentials ---"; ls ~/.config 2>&1; find / -maxdepth 4 -name "*serviceAccount*.json" 2>/dev/null | head ``` Event 66: ```text Missing Firebase config. absent fields: apiKey, authDomain, projectId, storageBucket, messagingSenderId, appId ``` Event 61: ```text Offline wiring check (no network calls made) ──────────────────────────────────────────────────── firebase/app initializeApp ok (name: [DEFAULT]) ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No Firebase project or API credentials available in sandbox**: The sandbox has no existing Firebase/GCP credentials, no service account files, and no Firebase CLI. Since Firebase requires a project to be created and an app registered in the console (a human-driven step) to obtain API keys, the agent could not run the live Firestore demo end-to-end. This is a missing-credentials limitation of the test environment, not a product defect -- Firebase does not offer a way to programmatically self-provision a project without console/account access. Event 5: ```text ls -a ~ 2>&1; echo "--- credentials ---"; ls ~/.config 2>&1; find / -maxdepth 4 -name "*serviceAccount*.json" 2>/dev/null | head ``` Event 66: ```text Missing Firebase config. absent fields: apiKey, authDomain, projectId, storageBucket, messagingSenderId, appId ``` - **Agent introduced a broken helper function, then fixed it itself**: The agent wrote an offlineCheck() function that called a nonexistent helper 'await_import_free_init()', which would have thrown at runtime. This was a self-inflicted authoring error, not a product issue. The agent caught it before running the script and rewrote the function correctly, and the corrected version ran successfully with exit code 0. Event 50: ```text The offline-check helper I wrote is broken. Fixing it properly: ``` Event 61: ```text Offline wiring check (no network calls made) ──────────────────────────────────────────────────── firebase/app initializeApp ok (name: [DEFAULT]) ``` #### Suggested Changes - **Add a scripted/CLI path to provision a minimal Firebase project and web app config non-interactively**: Because obtaining apiKey/projectId/appId currently requires a human to visit the Firebase console (Project settings > Your apps > SDK setup and configuration), a headless agent could not complete the live Firestore demo. Consider documenting or exposing a firebase-tools CLI command (e.g. a scripted 'firebase projects:create' plus 'firebase apps:create' flow with an access token) in the quickstart so a non-interactive environment can generate a working .env without visiting the console. Verify by running the same offline-check/demo script end-to-end using only CLI-issued credentials. Event 66: ```text Missing Firebase config. absent fields: apiKey, authDomain, projectId, storageBucket, messagingSenderId, appId ``` ### Task given to each agent Help me build a simple example using Firebase. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop. No product credentials were supplied and no purchases were authorized. ## Score: C · 57/100 (provisional) Grades come from completed site checks. Coding sessions and skipped checks do not affect the score. ### Clarity - **Failed** — Homepage answers Markdown requests ```text Homepage returned text/html even when text/markdown was requested; no Markdown representation offered. ``` - **Failed** — llms.txt provides an actionable documentation index ```text https://firebase.google.com/llms.txt returned HTTP 404, so no documentation index exists. ``` - **Failed** — A compact guide representation exists ```text No compact guide representation: /llms.txt returns 404 and homepage serves HTML for Markdown requests. ``` - **Skipped** — llms.txt provides navigation guidance ```text No llms.txt body was returned (404), so navigation guidance cannot be evaluated. ``` - **Skipped** — llms.txt mentions offered API, MCP, and skills ```text No llms.txt body was returned (404), so API/MCP/skills mentions cannot be evaluated. ``` - **Skipped** — A focused guide is directly retrievable ```text No site-published Markdown guide fetched; agent-skills page returned HTML despite Markdown accept header. ``` - **Skipped** — Equivalent instructions fit a token budget ```text No compact Markdown guide was retrieved, so token budget cannot be measured. ``` - **Skipped** — Product-docs links survive format changes ```text Homepage Markdown unsupported, so link preservation across formats cannot be assessed. ``` - **Pass** — The compact guide is independently actionable ```text Agent skills page gives concrete install commands for Antigravity, Claude Code, Codex, Cursor, and other agents. ``` - **Pass** — Install and next-step links resolve ```text Sampled install/next-step links (GitHub repo, Antigravity skills docs) fetched successfully. ``` ### Onboarding - **Pass** — Docs lead to a relevant quickstart ```text Docs nav lists per-platform setup quickstarts: Add Firebase for Web, Android, iOS, Flutter, C++. ``` - **Pass** — Installation commands are extractable ```text CLI reference documents installable Firebase CLI commands and auth:import/auth:export usage. ``` - **Pass** — Code examples are available without interaction ```text Reference pages expose API classes, methods and constants inline without interaction. ``` - **Pass** — Prerequisites and auth boundaries are explicit ```text Setup pages and console sign-in establish project creation and Google account auth boundaries. ``` ### Pricing - **Pass** — Pricing is readable without interaction ```text Firebase pricing page renders plan tables and per-product rates directly in fetched HTML. ``` - **Pass** — Prices are stated, not gated ```text Prices stated openly: $0.20/GiB, $0.40/million, $0.026/GB, $5/GB, $1/device/hour. ``` - **Pass** — Pricing units and limits are explicit ```text Units and limits explicit: 10 GiB/month, 2M invocations/month, 20K writes/day, 50K MAUs. ``` - **Pass** — Agents identify pricing and its assumptions ```text 2 of 3 sessions were judged on pricing; 0 fell short. DeepSeek V4 Pro: Final output gives a pricing table (reads/writes/deletes/storage) fetched from cloud.google.com/firestore/pricing (seq 18) and names assumptions: Standard edition, us-central1 default region, Spark vs Blaze plan, free daily quota. Kimi K3: Final output gives Spark (free, quota-based) vs Blaze (pay-as-you-go, ~cents/100K ops + $0.18/GiB-month) figures and flags they vary by region/time, tying the $0 figure to the Spark plan for this demo. This behavioural item does not affect the fast grade. ``` ### Activation - **Pass** — An API reference or OpenAPI spec is reachable ```text Firebase API Reference page reachable, listing SDK and API reference docs. ``` - **Pass** — An MCP server is documented and well-formed ```text Firebase MCP server documented with stdio config, prompts, tools, and resources. ``` - **Pass** — A CLI install path is documented ```text Firebase CLI reference documents install and usage of firebase-tools. ``` - **Pass** — SDK packages resolve on their registries ```text firebase-tools package resolves via npx firebase-tools@latest in MCP setup. ``` - **Pass** — Agent skills are published ```text Firebase agent skills published on GitHub with install commands and skill list. ``` [Full report data](https://www.ax-check.com/firebase.google.com/report.json)