# AX Check: genhealth.ai
Checked 2026-10-22.

Quickstart works well, but pricing is sales-quote only
Quickstart, API reference, and MCP docs are all directly usable. Pricing page 404s; homepage only says "contact us," so agents can't get a number.

## Onboarding needs a login

## Coding sessions
All three independent sessions completed. Each found the API quickstart and docs usable with curl/Python examples, but none found a published price: the pricing page 404s, and the homepage FAQ directs to contact sales. Sessions noted a free sandbox needs no credit card, though one session speculated about usage-based pricing without evidence.

### DeepSeek V4.1 Flash
[View public run](https://agents.withgauge.com/p/runs/653732a4-511a-426f-a215-1bf6c28efc4e) · [Read transcript](https://www.ax-check.com/genhealth.ai/sessions/deepseek.json)
Said no public price exists (/pricing is a 404, the FAQ says contact sales), so pricing is a custom sales quote. Also noted the free sandbox with no credit card required. (seq 46, seq 75, README.md)
#### End-to-end onboarding
- **Onboarding needs a login**: The agent explored GenHealth's hosted docs, OpenAPI spec, and Swagger UI (all publicly reachable without auth), and wrote a working example client. It confirmed the live API is reachable by hitting the real hosted endpoint with a dummy key and getting a clean 401. However, it never obtained a real API key: the docs state sign-up happens through an external signup/login flow, and the agent explicitly says it did not create an account. No authenticated operation against the real product was demonstrated — only an auth failure with a placeholder credential.
  Event 44:

  ```text
  You need a GenHealth-issued API key with read access. [Sign up for GenHealth](https://umpa.genhealth.ai/api/auth/login?screen_hint=signup) to request access.
  ```
  Event 68:

  ```text
  Request failed: HTTP 401 from https://api.umpa.genhealth.ai/v2/cases?page=1&limit=10: {"detail":"Requires authentication"}
  ```
  Event 75:

  ```text
  Only on **credentials**. Every authenticated endpoint needs a GenHealth-issued API key, and there's no self-serve key issuance — you request access via signup and scopes
  ```

#### Hallucinated URLs
None identified in this transcript.

#### Blockers
- **No self-serve API key issuance**: GenHealth requires a GenHealth-issued API key for every authenticated endpoint (cases, policies, workflows). There is no way to generate one without going through an external signup/login flow which requires human action outside the agent's reach in this session. This is normal product gating (login/account provisioning), not a product defect — the agent correctly identified it and stopped rather than attempting to bypass it.
  Event 44:

  ```text
  Sign up for GenHealth](https://umpa.genhealth.ai/api/auth/login?screen_hint=signup) to request access. Keep the key on the server and never commit it to source control.
  ```
  Event 68:

  ```text
  Request failed: HTTP 401 from https://api.umpa.genhealth.ai/v2/cases?page=1&limit=10: {"detail":"Requires authentication"}
  ```

#### Suggested Changes
- **Add a pricing page or self-serve tier summary to the site nav**: The homepage FAQ and /pricing both resolve with no concrete numbers — /pricing 404s and the FAQ only says to contact sales. Add a /pricing route (or redirect it to the FAQ anchor) summarizing at least the free sandbox tier and how custom/enterprise pricing is structured, so first-time developers don't have to parse ROI calculators and sales copy to learn pricing is fully custom. Verify by checking that https://genhealth.ai/pricing returns 200 instead of 404.
  Event 16:

  ```text
  === /pricing ===
  404 -> 
  ```
  Event 46:

  ```text
  How much does GenHealth cost? Contact us to discuss your workflows and request pricing for your team.
  ```

### Kimi K3
[View public run](https://agents.withgauge.com/p/runs/db63bbfb-5b91-4d27-9d19-30191ad83a95) · [Read transcript](https://www.ax-check.com/genhealth.ai/sessions/kimi.json)
Gave no cost figure or plan/workload assumptions; said pricing is unpublished (pricing page 404) and guessed 'likely per workflow/volume' contract pricing without basis. (seq 33, seq 53, seq 56)
#### End-to-end onboarding
- **End-to-end onboarding not demonstrated**: No credential acquisition was attempted or possible. The agent found no self-serve signup, no SDK on npm/PyPI, a docs login that redirects to a 404 auth endpoint, and release notes stating the platform API was sunset. The agent correctly stopped without ever obtaining or using credentials against the live product.
  Event 44:

  ```text
  404
  000
  location: https://genhealth.ai/api/auth/login
  
  ```
  Event 43:

  ```text
  Sunset platform API and Gmode
  ```
  Event 56:

  ```text
  No self-serve credentials: docs login redirects to an auth endpoint that 404s; there's no signup flow.
  ```

#### Hallucinated URLs
None identified in this transcript.

#### Blockers
- **No self-serve signup or API key flow exists**: Product behavior, not agent error: docs login redirects to an auth endpoint returning 404, and there is no visible signup/API-key page. This is an enterprise demo-gated product rather than a missing credential on the agent's part.
  Event 44:

  ```text
  location: https://genhealth.ai/api/auth/login
  
  ```
  Event 52:

  ```text
  404 https://genhealth.ai/api/auth/login
  ```
- **Platform API reportedly sunset and no SDK published**: Product behavior: release notes explicitly state the platform API was sunset, api.genhealth.ai does not resolve, and no package exists on npm or PyPI, leaving no functional API surface for a developer to call.
  Event 43:

  ```text
  Sunset platform API and Gmode
  ```
  Event 44:

  ```text
  000
  
  ```
  Event 18:

  ```text
  npm error 404
  npm error 404 Note that you can also install from a
  ```
  Event 54:

  ```text
  ERROR: No matching distribution found for genhealth
  ```
- **Documentation is a single page pointing to a human sales contact**: Product behavior: the only technical doc (HL7 DaVinci FHIR integration) ends by directing developers to email a contact rather than providing a sandbox, API key, or quickstart, which blocked any hosted-API exercise.
  Event 24:

  ```text
  For more information on how to implement these integrations in your FHIR server, please reach out [email protected]
  ```

#### Suggested Changes
- **Publish a self-serve API key or sandbox signup page**: On docs.genhealth.ai, add a signup/API-key flow instead of redirecting /login to an endpoint that 404s (observed at https://genhealth.ai/api/auth/login). Verify by confirming a new account can generate a live key without emailing sales.
  Event 44:

  ```text
  location: https://genhealth.ai/api/auth/login
  
  ```
- **Publish pricing details on the website**: The genhealth.ai site shows only customer ROI case-study numbers, no actual pricing; add a pricing page or tier breakdown so prospective developers/buyers do not have to book a demo to learn cost structure. Verify by checking that /pricing (currently 404) returns real content.
  Event 33:

  ```text
  404
  
  ```
  Event 53:

  ```text
  $1.2M
  $1.2M this year…
  $1.2M.
  
  ```
- **Expand developer docs beyond the single DaVinci FHIR page**: docs.genhealth.ai/llms.txt currently lists only one integration guide and release notes; add a quickstart with authentication steps and example requests so the API as payer interface (e.g., /preauth/codes) can be tried without contacting support first.
  Event 34:

  ```text
  # GenHealth.ai Documentation
  
  > GenHealth's API provides access to predictive analytics API's for healthcare
  
  ## Guides: Documentation
  - Prior Authorization Automation
    - [FHIR API: HL7 DaVinci](https://docs.genhealth.ai/docs/integration-with-hl7-davinci-fhir-apis.md)
  ```

### Qwen 3.8 Max
[View public run](https://agents.withgauge.com/p/runs/96ae377c-77f0-4a84-8609-30ff98326ec3) · [Read transcript](https://www.ax-check.com/genhealth.ai/sessions/qwen.json)
Gave a sourced cost picture without inventing a number: free sandbox with no credit card, production is a quote-only sales subscription (/pricing returns 404), access depends on the workflows plan, and no per-event rate is published. (seq 35, seq 41, seq 30, seq 87)
#### End-to-end onboarding
- **Onboarding needs a login**: The agent never obtained a GenHealth API key. It explored the public docs/site extensively and wrote a stdlib Python client, but every live API call it made (doctor probe, bogus-key test) returned 401/403 because no real credential was available. The quickstart.py script explicitly detects the missing key and prints a message directing a human to sign up interactively. No authenticated product operation (listing cases, creating/running a workflow) was ever demonstrated — only unauthenticated/failed-auth probes and local script tests with a known-bad dummy key.
  Event 36:

  ```text
  401
  {"detail":"Requires authentication"}
  403
  {"detail":"Not authenticated"}
  ```
  Event 65:

  ```text
  === 2) bogus key (expect clean 401) ===
  error: HTTP 401 on GET /capabilities/v2 -> GENHEALTH_API_KEY missing/expired/invalid - check the bearer token. (no automatic write retry attempted)
  exit=1
  ```
  Event 60:

  ```text
  GENHEALTH_API_KEY is not set. Get an organization-bound key:\n  1. sign up at https://umpa.genhealth.ai/api/auth/login?screen_hint=signup\n  2. create a key at https://genhealth.ai/account/api-keys\n  3. export GENHEALTH_API_KEY=...   (never commit it)
  ```
  Event 87:

  ```text
  `doctor` exits 1: **no `GENHEALTH_API_KEY`**, and self-provisioning one requires interactive signup + a real org + the workflows plan feature — I can't do that.
  ```

#### Hallucinated URLs
None identified in this transcript.

#### Blockers
- **No self-serve way to obtain a GenHealth API key**: The developer quickstart and the agent's own client both require a GENHEALTH_API_KEY, but acquiring one needs an interactive signup flow (umpa.genhealth.ai login/signup) plus a provisioned organization and the 'workflows plan feature.' This is a normal authentication requirement, not a product defect — but it fully blocked any authenticated call (workflow validate/import/run, case listing) for the rest of the session.
  Event 30:

  ```text
  You need a GenHealth-issued API key with read access. [Sign up for GenHealth](https://umpa.genhealth.ai/api/auth/login?screen_hint=signup) to request access.
  ```
  Event 36:

  ```text
  401
  {"detail":"Requires authentication"}
  403
  {"detail":"Not authenticated"}
  ```
  Event 87:

  ```text
  self-provisioning one requires interactive signup + a real org + the workflows plan feature — I can't do that.
  ```
- **No public pricing page**: genhealth.ai/pricing returns a 404, and no page on the site states a dollar figure; pricing is gated behind sales contact ('Book Demo'/'Contact us'). This is product/business-model behavior (sales-led pricing), not an agent error, and forced the agent to infer pricing structure indirectly from the ROI calculator and docs language rather than quoting a rate.
  Event 18:

  ```text
  --- https://genhealth.ai/pricing
  404 https://genhealth.ai/pricing
  ```
  Event 41:

  ```text
  Net Annual Benefit
  Your total annual benefit after accounting for GenHealth.ai subscription costs.
  ```

#### Suggested Changes
- **Publish a pricing or plan-tier summary page**: Add a basic pricing/plans page (even a tiered-estimate or 'contact for enterprise, free sandbox for dev' breakdown) at genhealth.ai/pricing, which currently 404s. Verify by curling https://genhealth.ai/pricing and confirming it returns 200 with at least indicative pricing or plan-feature information instead of requiring a sales conversation for any cost figure.
  Event 18:

  ```text
  --- https://genhealth.ai/pricing
  404 https://genhealth.ai/pricing
  ```
- **Add a direct API-key creation link into the quickstart doc**: The quickstart at genhealth.ai/docs/quickstart only links to the signup screen (umpa.genhealth.ai/api/auth/login?screen_hint=signup); it does not mention or link account/api-keys until a user is already signed in. Cross-link the dedicated key-management page (genhealth.ai/account/api-keys) directly in the 'Before you begin' callout so developers know exactly where keys live post-signup. Confirm by checking that the quickstart page text includes both the signup URL and the api-keys URL together.
  Event 30:

  ```text
  You need a GenHealth-issued API key with read access. [Sign up for GenHealth](https://umpa.genhealth.ai/api/auth/login?screen_hint=signup) to request access.
  ```

### Task given to each agent
Help me build a simple example using GenHealth.ai. 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 · 81/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 for a text/markdown request; no Markdown representation served.
  ```

- **Pass** — llms.txt provides an actionable documentation index

  ```text
  llms.txt links products, automations, docs, quickstart, API reference, OpenAPI and code JSON API.
  ```

- **Pass** — llms.txt provides navigation guidance

  ```text
  llms.txt organizes links under clear headings with descriptions and starting guidance.
  ```

- **Pass** — llms.txt mentions offered API, MCP, and skills

  ```text
  llms.txt mentions the JSON code API, OpenAPI document, and developer docs; MCP not offered.
  ```

- **Pass** — A compact guide representation exists

  ```text
  llms.txt and .md pages provide compact Markdown guides for agents.
  ```

- **Pass** — A focused guide is directly retrievable

  ```text
  quickstart.md and agent-quickstart.md are directly retrievable Markdown guides.
  ```

- **Pass** — Equivalent instructions fit a token budget

  ```text
  Quickstart is 477 tokens; agent quickstart 1487, both well under budget.
  ```

- **Skipped** — Product-docs links survive format changes

  ```text
  Homepage Markdown unsupported, so link preservation across formats cannot be measured.
  ```

- **Pass** — The compact guide is independently actionable

  ```text
  Agent quickstart gives concrete steps: capabilities, validate, import, publish, run, inspect with commands.
  ```

- **Pass** — Install and next-step links resolve

  ```text
  Quickstart next-step links to get-case and list-policies Markdown both fetched successfully.
  ```


### Onboarding
- **Pass** — Docs lead to a relevant quickstart

  ```text
  llms.txt and docs link a quickstart with concrete auth and first-request steps.
  ```

- **Pass** — Installation commands are extractable

  ```text
  Quickstart gives extractable bash: export key, curl cases, plus Python client commands.
  ```

- **Pass** — Code examples are available without interaction

  ```text
  Quickstart shows curl, JSON response, and workflow JSON/Python examples without interaction.
  ```

- **Pass** — Prerequisites and auth boundaries are explicit

  ```text
  Quickstart states API key with read access, signup link, and bearer auth boundary.
  ```


### Pricing
- **Failed** — Agents identify pricing and its assumptions

  ```text
  3 of 3 sessions were judged on pricing; 1 fell short. DeepSeek V4.1 Flash: Said no public price exists (/pricing is a 404, the FAQ says contact sales), so pricing is a custom sales quote. Also noted the free sandbox with no credit card required. (seq 46, seq 75, README.md) Kimi K3: Gave no cost figure or plan/workload assumptions; said pricing is unpublished (pricing page 404) and guessed 'likely per workflow/volume' contract pricing without basis. (seq 33, seq 53, seq 56) Qwen 3.8 Max: Gave a sourced cost picture without inventing a number: free sandbox with no credit card, production is a quote-only sales subscription (/pricing returns 404), access depends on the workflows plan, and no per-event rate is published. (seq 35, seq 41, seq 30, seq 87) This behavioural item does not affect the fast grade.
  ```

- **Skipped** — Pricing is readable without interaction

  ```text
  Homepage FAQ says contact us for pricing; no pricing page fetched.
  ```

- **Skipped** — Prices are stated, not gated

  ```text
  No pricing page fetched; homepage only says contact us to request pricing.
  ```

- **Skipped** — Pricing units and limits are explicit

  ```text
  No pricing units or limits evidence fetched for GenHealth.
  ```


### Activation
- **Pass** — An API reference or OpenAPI spec is reachable

  ```text
  API reference and OpenAPI contract documented; endpoint pages fetched successfully.
  ```

- **Pass** — An MCP server is documented and well-formed

  ```text
  MCP server documented with Streamable HTTP endpoint, bearer auth, and tool discovery.
  ```

- **Skipped** — A CLI install path is documented

  ```text
  No CLI install path documented; only curl and Python client examples offered.
  ```

- **Skipped** — SDK packages resolve on their registries

  ```text
  No SDK or packaged CLI registry lookup supplied for GenHealth packages.
  ```

- **Skipped** — Agent skills are published

  ```text
  No agent skills published or documented in the fetched evidence.
  ```



[Full report data](https://www.ax-check.com/genhealth.ai/report.json)