# Verily Life Sciences > Verily Life Sciences is Alphabet's precision health company. Its developer-facing surface is > Verily Workbench, an enterprise Trusted Research Environment for biomedical data, backed by a > control-plane REST API at https://workbench.verily.com/api, a first-party `wb` command line > interface, and a published Terraform provider. Verily's data layer, Syntax, is FHIR-native, and > Verily publishes open-source FHIRPath and FHIR Shorthand tooling. Generated by API Evangelist on 2026-09-02 from Verily's public documentation, GitHub organizations, package registries and live endpoint probes. Verily does not publish an llms.txt of its own (https://verily.com/llms.txt and https://support.workbench.verily.com/llms.txt both return 404), so this file is generated, not harvested. ## What an agent can and cannot do here - There is **no public OpenAPI**. The Workbench API is described by OpenAPI internally — Verily's own Terraform provider ships oapi-codegen generated clients for it — but every spec path (`/v3/api-docs`, `/openapi.json`, `/openapi.yml`, `/api-docs`, swagger-ui) returns **HTTP 403** to anonymous callers on all three services. - There is **no MCP server** and **no A2A agent card**. - There is **no API key**. Every call authenticates as a Google identity or an impersonated Google service account, and a human must complete an interactive login first. - The practical integration paths today are the **Terraform provider** and the **`wb` CLI**. ## API - [Verily Workbench API](https://support.workbench.verily.com/docs/): control-plane REST API. Base `https://workbench.verily.com/api`, with three services: `wsm` (workspaces, folders, controlled and referenced cloud resources, IAM), `axon` (orchestration, CLI distribution), `user` (users, groups, organizations). - [Service health](https://workbench.verily.com/api/wsm/status): unauthenticated. Also `/api/axon/status` and `/api/user/status`. - [Service versions](https://workbench.verily.com/api/wsm/version): unauthenticated JSON build info. Also `/api/axon/version` and `/api/user/version`. - [Supported CLI window](https://workbench.verily.com/api/axon/cli-version): unauthenticated JSON giving `oldestSupportedCli`, `latestSupportedCli`, the distribution bucket and a SHA-256 checksum. ## Documentation - [Verily Workbench documentation](https://support.workbench.verily.com/docs/) - [Getting started](https://support.workbench.verily.com/docs/getting_started/) - [References](https://support.workbench.verily.com/docs/references/) - [CLI full reference](https://support.workbench.verily.com/docs/references/cli_reference/): 153 documented command paths across 21 groups — the most complete public description of what the Workbench API can do. - [CLI install and run](https://support.workbench.verily.com/docs/guides/cli/cli_install_and_run/) - [Architecture overview](https://support.workbench.verily.com/docs/references/architecture_overview/) - [Glossary](https://support.workbench.verily.com/docs/references/glossary/) - [Troubleshooting](https://support.workbench.verily.com/docs/references/troubleshooting/) - [Release notes](https://support.workbench.verily.com/docs/release_notes/) - [Contact / support](https://support.workbench.verily.com/docs/contact/) — workbench-support@verily.com ## Clients and packages - [Terraform provider verily-src/workbench](https://registry.terraform.io/providers/verily-src/workbench/latest) — v0.0.4, published 2026-01-22. A real API client for the control plane. - [Terraform module verily-src/workbench-analysis-plane/aws](https://registry.terraform.io/modules/verily-src/workbench-analysis-plane/aws/latest) — v0.3.16, published 2026-09-02. - `wb` CLI — v0.422.514 (live from the cli-version endpoint). Installed from `https://storage.googleapis.com/bkt-workbench-artifacts/download-install.sh`. Requires Java 17, the gcloud SDK and jq. macOS and Linux only. No Homebrew, npm or PyPI distribution. - [fhirpath-go](https://github.com/verily-src/fhirpath-go) — v1.5.0, 2025-11-20. Go FHIRPath implementation over the google/fhir protobufs. - [fsh-lint](https://github.com/verily-src/fsh-lint) — v0.1.0, 2025-05-30. FHIR Shorthand linter, with an official GitHub Action. - No npm or PyPI package is published by Verily. Registry name collisions (`verily` on npm and PyPI, `workbench-cli` on PyPI) belong to unrelated publishers. ## Repositories - [github.com/verily-src](https://github.com/verily-src) — the active organization. - [github.com/verilylifesciences](https://github.com/verilylifesciences) — older open-source projects (genomewarp, medtimeline, deepmass, variant-qc, purplequery). - [workbench-examples](https://github.com/verily-src/workbench-examples) — example notebooks and documentation for working with Verily Workbench. ## Products - [Verily Pre platform](https://verily.com/solutions/pre-platform) — the AI-native precision health platform. Syntax is its FHIR-native common data model. - [Verily Workbench](https://verily.com/solutions/pre-platform/workbench) — the Trusted Research Environment, on Google Cloud and AWS. - [Pre Exchange](https://verily.com/solutions/pre-platform/exchange) and [Refinery](https://verily.com/solutions/pre-platform/refinery) - [Verily Intelligence](https://verily.com/solutions/pre-platform/verily-intelligence) ## Commercial - Tiers: **Standard** (free, self-serve with a Google identity, up to 5 workspaces, select data collections), **Professional** (paid; custom applications, more workspaces, own-data upload), **Enterprise** (sales-gated). No price is published for any paid tier. - [Talk to an expert](https://verily.com/solutions/pre-platform/workbench/contact) - [Terms of service](https://verily.com/terms) - [Privacy policy](https://verily.com/privacy-policy) - [Security and trust](https://verily.com/security-trust) — names no certification; attestation reports are requested from info@verily.com and may require an NDA. - Cloud compute and storage are billed by the customer's own GCP or AWS account, linked through a Workbench billing pod. ## Known gaps (as of 2026-09-02) - No published OpenAPI, GraphQL SDL, AsyncAPI or gRPC contract. - No documented rate limits, no rate-limit response headers, no 429 semantics. - No idempotency keys and no documented retry safety. - No error-code registry and no RFC 9457 problem details. - No OAuth scope reference. - No pagination contract. - No `/.well-known/` documents on any host; no security.txt and no vulnerability disclosure program. - No hosted status page (per-service `/status` endpoints exist instead). - No deprecation or sunset policy for the API; a supported-version window is published for the CLI only. ## Company - [Verily](https://verily.com/) - [Perspectives (blog)](https://verily.com/perspectives) - [About us](https://verily.com/about-us) - [Contact](https://verily.com/contact-us)