# LifeMine > LifeMine is a clinical-stage biopharmaceutical company pioneering Top-Down Drug Discovery — mining the fungal biosphere for genetically encoded small molecules and developing them into precision medicines for immune-mediated disease and organ transplant rejection. Founded 2017 by Gregory Verdine, Richard Klausner and WeiQing Zhou; headquartered in Watertown, Massachusetts, with sites in Gloucester, Massachusetts and Basel, Switzerland. LifeMine publishes no developer portal, no API documentation and no llms.txt of its own. This file was GENERATED by API Evangelist on 2026-08-04 from artifacts fetched from LifeMine's live hosts. The company nonetheless operates two genuinely public, anonymous, machine-readable read APIs as a byproduct of the platforms it runs — a WordPress REST API on its website, and a Greenhouse job board API for its careers surface. Both are documented below. ## What is NOT here LifeMine's drug-discovery platform (Avatar-Rx), its genomics, its compound libraries and its clinical data are NOT exposed through any public API. No endpoint on either host returns scientific, clinical or regulatory data. Do not represent the APIs below as access to LifeMine's research. ## APIs - [LifeMine Website Content API (WordPress REST)](https://lifeminetx.com/wp-json/): Anonymous read API over site content — 24 news items (press releases, publications, in-the-news, thought leadership), 9 static pages, 117 media assets, and a `team` custom post type carrying 15 leadership, founder and board records. 203 registered routes across 10 namespaces. No credentials required for reads. - [LifeMine Careers API (Greenhouse Job Board)](https://boards-api.greenhouse.io/v1/boards/lifeminetx): Anonymous read API over open roles, departments and offices. 2 open roles, 32 departments, 3 offices observed 2026-08-04. Includes GDPR data-compliance blocks and AI-disclosure fields per role. - [WPGraphQL endpoint](https://lifeminetx.com/graphql): Live GraphQL endpoint (RootQuery confirmed). Public introspection is DISABLED, so no schema is available — do not assume a schema. ## Specs Neither host publishes an OpenAPI document. Both specs below were derived by API Evangelist from the hosts' own self-describing documents and live payloads. - [Content OpenAPI 3.1](https://raw.githubusercontent.com/api-evangelist/lifemine/refs/heads/main/openapi/lifemine-content-openapi.yml): 134 paths, 268 operations. Derived from the WordPress route index plus per-resource JSON Schemas returned by HTTP OPTIONS. - [Careers OpenAPI 3.1](https://raw.githubusercontent.com/api-evangelist/lifemine/refs/heads/main/openapi/lifemine-careers-openapi.yml): 12 paths, 12 operations. Derived from the Greenhouse Job Board API docs plus live responses from LifeMine's board. - [WordPress route index (verbatim)](https://raw.githubusercontent.com/api-evangelist/lifemine/refs/heads/main/openapi/_original/lifemine-wp-json-index.json): The unmodified discovery document, all 203 routes. - [JSON Schemas](https://github.com/api-evangelist/lifemine/tree/main/json-schema): Seven real schemas harvested via OPTIONS — post (28 properties), page (26), attachment (33), team (20), category (10), tag (8), team_categories (10). ## Key operations Content API — base `https://lifeminetx.com/wp-json`: - `GET /wp/v2/posts` — news; filter with `categories`, `after`, `search`; always send `_fields`. - `GET /wp/v2/categories` — the news taxonomy: press-releases (9), in-the-news (13), publications (1), expedition-academy (1). - `GET /wp/v2/team` — leadership, founders and board as structured records. - `GET /wp/v2/team_categories` — leadership (10), founders (3), board-of-directors (7); people hold multiple terms, so deduplicate by id. - `GET /wp/v2/pages` — about, science, pipeline, culture-careers, contact, privacy-policy. - `GET /wp/v2/search` — cross-resource typed search stubs. - `GET /wp/v2/media` — 117 assets with `source_url` and `alt_text`. Careers API — base `https://boards-api.greenhouse.io/v1/boards/lifeminetx`: - `GET /jobs` — open roles; add `content=true` for full descriptions. - `GET /jobs/{id}?questions=true` — one role with departments, offices and application questions. - `GET /departments?render_as=tree` — hiring org hierarchy. - `GET /offices` — Basel CH, Gloucester MA, Watertown MA. ## Conventions - **Auth:** none for reads on either surface. The WordPress discovery document advertises `"authentication": []`. Writes need a WordPress credential that is not issued to the public and return `401 rest_forbidden`. - **Pagination (content):** `page` / `per_page` (max 100) / `offset`; read `X-WP-Total` and `X-WP-TotalPages` headers; `Link: rel="next"` per RFC 8288. Both headers are CORS-exposed. - **Pagination (careers):** none — collections return whole, with `meta.total` on `/jobs`. - **Sparse fields:** `_fields=id,title,link` on the content API. Use it — a full post object is 28 properties of rendered HTML. - **Embedding:** `_embed` inlines author, featured media and terms, avoiding N+1 requests. - **Schema discovery:** HTTP OPTIONS on any content collection returns that resource's full JSON Schema. - **Errors:** NOT RFC 9457. WordPress returns `{"code","message","data":{"status"}}`; Greenhouse returns `{"error"}`. - **Idempotency:** not supported on either surface. No public write path exists. - **Rate limits:** none published, no rate-limit headers. robots.txt asks for `Crawl-delay: 10` — treat that as the pacing contract. - **Caching:** content collections are `Cache-Control: max-age=600` behind WP Engine and Cloudflare. - **Indexing:** API responses carry `x-robots-tag: noindex`. Public, but deliberately not indexed. ## Docs - [Website](https://lifeminetx.com/) - [About](https://lifeminetx.com/about/) - [Science](https://lifeminetx.com/science/) - [Pipeline](https://lifeminetx.com/pipeline/) - [News](https://lifeminetx.com/news/) - [Culture & Careers](https://lifeminetx.com/culture-careers/) - [Contact](https://lifeminetx.com/contact/) - [Privacy Policy](https://lifeminetx.com/privacy-policy/) - [RSS feed](https://lifeminetx.com/feed/) - [WordPress REST API Handbook](https://developer.wordpress.org/rest-api/) — the upstream spec the content API implements - [Greenhouse Job Board API docs](https://developers.greenhouse.io/job-board.html) — the upstream spec the careers API implements ## Agent posture - No MCP server. No A2A agent card at either `/.well-known/agent-card.json` or `/.well-known/agent.json` (both 404). - No `/.well-known/security.txt`, `openid-configuration`, `oauth-authorization-server`, `api-catalog` or `ai-plugin.json` (all 404). - The WordPress Abilities API (`wp-abilities/v1`) IS registered on the host — a native agent-capability registry — but returns `401 rest_forbidden` anonymously. It is the one unrealised agent surface here. - `robots.txt` disallows nothing: `User-agent: * / Disallow:`. All agents are permitted. - Candidate MCP tools derived from these specs: [mcp/lifemine-mcp.yml](https://raw.githubusercontent.com/api-evangelist/lifemine/refs/heads/main/mcp/lifemine-mcp.yml) — candidate only, not deployed by LifeMine. - Packaged agent skills: [skills/](https://github.com/api-evangelist/lifemine/tree/main/skills) — track company news, map leadership and board, monitor open roles. ## Provenance This is an independent third-party profile maintained by [API Evangelist](https://apievangelist.com), assembled entirely from publicly reachable material with no credentials. It is not operated, endorsed or reviewed by LifeMine. Corrections, re-scores and removal are free — open an issue on https://github.com/api-evangelist/lifemine or email info@apievangelist.com.