# AX Check: joinhomebase.com Checked 2026-09-19. Pricing is clear upfront, but developer docs are missing. Plans list plainly: Basic $0, Essentials $30, Plus $70, All-in-One $120 per location/month. No API, CLI, or SDK docs were found for deeper integration. ## Onboarding needs a login ## Coding sessions Three independent sessions tried to review the product. DeepSeek V4 Pro and Kimi K3 both completed and correctly reported the per-location pricing tiers and payroll add-on cost. Qwen 3.8 Max did not complete and produced no final output or pricing discussion at all. ### DeepSeek V4 Pro [View public run](https://agents.withgauge.com/p/runs/12c4f098-69c3-414f-8f5a-2fce81053e0e) · [Read transcript](https://www.ax-check.com/joinhomebase.com/sessions/deepseek.json) Final output gives a pricing table (Basic $0, Essentials $30/mo/location, Plus $70/mo/location, All-in-One $120/mo/location, Payroll add-on $49+$6/employee) explicitly sourced 'from the current pricing page' with per-location and add-on assumptions called out. #### End-to-end onboarding - **Onboarding needs a login**: Agent explored Homebase's public docs and API (docs.joinhomebase.com, api.joinhomebase.com) and confirmed a real hosted REST API exists, but never obtained an API key. Homebase requires requesting a key inside the web app and waiting for manual approval before it appears — no self-service token issuance is available via API. The agent wrote a read-only example script but could not execute it against the live API; unauthenticated calls returned 401 invalid_token, and the session ended asking the human to supply a key. Event 72: ```text {"error":"The Authorization header supplied is invalid. The Authorization header should be of the form: \"Bearer \"","error_code":"invalid_token"} ``` Event 80: ```text Request an API Key To access the API, you first need to request an API key. You can do this from the *API Settings* page within the Homebase application. ``` Event 98: ```text 401 {"error":"The Authorization header supplied is invalid. The Authorization header should be of the form: \"Bearer \"","error_code":"invalid_token"} ``` Event 124: ```text I don't have a Homebase API key, and I can't self-serve one — it has to be requested in the app (Settings → Account → API Access) and approved by Homebase. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-service API key issuance**: Homebase's API requires requesting a key from inside the logged-in web app (Settings > Account > API Access) and waiting for manual approval before the key is displayed. This is normal product behavior (a credential gate), not an agent error or environment issue, but it fully prevented any authenticated API call in this session. All unauthenticated requests to api.joinhomebase.com returned 401 invalid_token. Event 72: ```text error_description="The Authorization header supplied is invalid. The Authorization header should be of the form: "Bearer "" ``` Event 80: ```text Request an API Key To access the API, you first need to request an API key. You can do this from the *API Settings* page within the Homebase application. ``` Event 98: ```text 401 {"error":"The Authorization header supplied is invalid. The Authorization header should be of the form: \"Bearer \"","error_code":"invalid_token"} ``` #### Suggested Changes - **Reconcile the two documented API base URLs**: The Authentication page's curl example and the runtime 401 responses point to https://api.joinhomebase.com, while the OpenAPI 'servers' block embedded in each reference page (e.g., getlocations.md) lists https://app.joinhomebase.com/api/public as the Production server. Fix by aligning the servers.url field in the OpenAPI spec on docs.joinhomebase.com/reference/getlocations.md with the curl example on docs.joinhomebase.com/reference/authentication-1.md, then verify a fresh reader would hit the same host either way. Event 91: ```text curl -H 'Authorization: Bearer YOUR_API_KEY' \ -H 'Accept: application/vnd.homebase-v1+json' \ https://api.joinhomebase.com/locations ``` Event 107: ```text "servers": [ { "url": "https://app.joinhomebase.com/api/public", "description": "Production" } ], ``` ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/1feb0e88-786e-48a0-9c83-a71cc652430a) · [Read transcript](https://www.ax-check.com/joinhomebase.com/sessions/kimi.json) Final output states homebase-react is free/MIT with no hosted service to charge for, and separately quotes the HR SaaS's per-location tiers (~$0-$80/location/month plus payroll) while flagging that's seat pricing not developer pricing — cost tied to explicit basis. #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: No hosted Homebase product credentials were obtained or used. The agent identified that the npm package homebase-react is a pure client-side library with no server, account system, or API keys, and separately found that the HR/scheduling SaaS at joinhomebase.com requires an approved partner/OAuth application it could not self-serve. The only 'workflow' executed was a local Node.js script using a library, not an authenticated call to any hosted product. Event 71: ```text its developer API requires approved partner/OAuth credentials issued after a business application. I'm blocked there; I can't self-serve an account, so nothing to act on. ``` Event 71: ```text The "database" is an embedded Datalog store living in your app's memory — there is **no server, no account, no API key**. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **HR SaaS Homebase requires partner approval to get API access**: The joinhomebase.com developer API needs business/partner application and OAuth credentials rather than self-service signup. This is a normal credential/login limitation of that product, not a defect, and the agent correctly stopped rather than trying to work around it. Event 71: ```text its developer API requires approved partner/OAuth credentials issued after a business application. I'm blocked there; I can't self-serve an account, so nothing to act on. ``` - **homebase-react npm package is browser-only, breaking headless Node execution**: Running the library's code in plain Node.js repeatedly failed because the bundle expects browser globals (document, window, addEventListener). This is a library/environment mismatch, not a hosted-product issue; the agent worked around it locally with jsdom stubs rather than being blocked long-term. Event 36: ```text ReferenceError: document is not defined ``` Event 51: ```text ReferenceError: window is not defined ``` Event 57: ```text TypeError: window.addEventListener is not a function ``` - **homebase.io domain does not resolve**: The primary homebase.io domain referenced in the npm package's homepage field failed DNS resolution, indicating the docs/marketing site for this library is dead. This reflects the product/project's abandoned state rather than agent error. Event 8: ```text curl: (6) Could not resolve host: homebase.io 000 200 ``` #### Suggested Changes None identified in this transcript. ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/7d67c088-6f99-476b-990f-b75294f69384) · [Read transcript](https://www.ax-check.com/joinhomebase.com/sessions/qwen.json) get_final_output returns 'no final message captured' and there is no pricing discussion anywhere in the trace. #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: The transcript supplied contains only a single run_meta event with configuration/session metadata. There is no evidence of any agent action, tool call, credential acquisition, or product operation taking place. No onboarding steps, API calls, or product interactions were observed. Event 0: ```text Help me build a simple example using Homebase. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No session activity captured beyond initial setup**: The only event present is the run_meta configuration event describing the session's model, sandbox, and prompt setup. No subsequent agent turns, tool calls, or outputs were included in the transcript, so it is impossible to determine whether the agent attempted to use Homebase, encountered errors, or made progress. This is a limitation of the supplied transcript/test environment rather than a product defect. Event 0: ```text "seedPrompt":"Help me build a simple example using Homebase. 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." ``` #### Suggested Changes None identified in this transcript. ### Task given to each agent Help me build a simple example using Homebase. 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: B · 73/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. ``` - **Pass** — llms.txt provides an actionable documentation index ```text llms.txt lists solutions, industries, tools, reference, data, pricing and support with descriptive links. ``` - **Pass** — llms.txt provides navigation guidance ```text llms.txt groups links under clear headings and gives citation and usage guidance for assistants. ``` - **Skipped** — llms.txt mentions offered API, MCP, and skills ```text llms.txt mentions no API, MCP server, or skills surface to assess. ``` - **Pass** — A compact guide representation exists ```text llms.txt is a compact Markdown guide covering solutions, tools, data, pricing and support. ``` - **Pass** — A focused guide is directly retrievable ```text llms.txt fetched directly at /llms.txt as text/plain Markdown, 2249 tokens. ``` - **Pass** — Equivalent instructions fit a token budget ```text llms.txt is 2249 tokens, well under the 8000-token budget. ``` - **Skipped** — Product-docs links survive format changes ```text Homepage Markdown unsupported, so link preservation across formats cannot be measured. ``` - **Skipped** — The compact guide is independently actionable ```text No compact agent guide was fetched; only llms.txt and homepage, so independent actionability is untested. ``` - **Pass** — Install and next-step links resolve ```text Sign-up links from homepage and pricing returned HTTP 200, so sampled install/next-step links resolve. ``` ### Onboarding - **Skipped** — Docs lead to a relevant quickstart ```text llms.txt links only marketing solution pages; no developer docs or quickstart fetched. ``` - **Skipped** — Installation commands are extractable ```text No installation or setup commands appear in any fetched Homebase document. ``` - **Skipped** — Code examples are available without interaction ```text No code examples found; fetched pages are marketing and sign-up only. ``` - **Skipped** — Prerequisites and auth boundaries are explicit ```text No developer API or auth documentation was fetched for Homebase. ``` ### Pricing - **Pass** — Pricing is readable without interaction ```text Pricing page renders plan tiers and prices directly in fetched HTML, no interaction needed. ``` - **Pass** — Prices are stated, not gated ```text Prices stated: Basic $0, Essentials $30, Plus $70, All-in-One $120 per location/month. ``` - **Pass** — Pricing units and limits are explicit ```text Units explicit: per location/month, employee caps, payroll $49 base + $6/employee. ``` - **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 (Basic $0, Essentials $30/mo/location, Plus $70/mo/location, All-in-One $120/mo/location, Payroll add-on $49+$6/employee) explicitly sourced 'from the current pricing page' with per-location and add-on assumptions called out. Kimi K3: Final output states homebase-react is free/MIT with no hosted service to charge for, and separately quotes the HR SaaS's per-location tiers (~$0-$80/location/month plus payroll) while flagging that's seat pricing not developer pricing — cost tied to explicit basis. This behavioural item does not affect the fast grade. ``` ### Activation - **Skipped** — An API reference or OpenAPI spec is reachable ```text No API reference or OpenAPI spec appears in the fetched Homebase documents. ``` - **Skipped** — An MCP server is documented and well-formed ```text No MCP server is documented in the fetched Homebase pages. ``` - **Skipped** — A CLI install path is documented ```text No CLI install path is documented in the fetched Homebase pages. ``` - **Skipped** — SDK packages resolve on their registries ```text No SDK or developer package registry result was fetched for Homebase. ``` - **Skipped** — Agent skills are published ```text No agent skills are published in the fetched Homebase documents. ``` [Full report data](https://www.ax-check.com/joinhomebase.com/report.json)