LifeMine

LifeMine (LifeMine Therapeutics) 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 in 2017 by Gregory Verdine, Richard Klausner and WeiQing Zhou, the company is headquartered in Watertown, Massachusetts with sites in Gloucester, Massachusetts and Basel, Switzerland, and has raised more than $320 million. Its lead programme, LIFE-001, is a structurally novel calcineurin inhibitor that entered a first-in-human Phase 1 trial in April 2025. LifeMine publishes no developer portal and no API documentation, and its drug-discovery platform is not exposed publicly. It does, however, operate two genuinely public, anonymous, machine-readable read APIs as byproducts of the platforms it runs: a WordPress REST API serving its news, pages, media and a structured leadership/board record set, and a Greenhouse job board API serving its open roles, departments and offices.

LifeMine publishes 7 API contracts indexed on the APIs.io network, including Board API, Departments API, Education API, and 4 more. Tagged areas include Company, Biotechnology, Pharmaceuticals, Drug Discovery, and Life Sciences.

The LifeMine catalog on APIs.io includes 1 Spectral governance ruleset.

LifeMine’s developer surface includes engineering blog, product news, support, authentication, and 23 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

25.7/100 emerging ▬ flat Agent 28/100 agent aware Front door AI 1/6 silent Heartbeat 100/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 3 Agent Skills

Company Biotechnology Pharmaceuticals Drug Discovery Life Sciences Clinical Trials Genomics Content Careers WordPress

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 25.7/100 · emerging

Contract Quality 4.6 / 21

Developer Ergonomics 4.4 / 17

Access Clarity 4.9 / 17

Operational Transparency 0.0 / 11

Contract Governance 1.9 / 10

Discoverability 4.9 / 9

Regulatory Posture 3.3 / 15

Agent readiness — 28/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 4 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/lifemine/"><img src="https://apis.io/badge/lifemine/card.svg" alt="LifeMine on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks

4 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 21.7 — up to +19.6 composite points
Developer Ergonomics scores 25.6 — up to +14.9 composite points
Access Clarity scores 28.6 — up to +14.3 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/lifemine/apis.yml: open an issue on github.com/api-evangelist/lifemine to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 7

Individual APIs this provider publishes, each with its own machine-readable definition.

LifeMine Website (WordPress REST)

The public WordPress REST API (wp-json) of the LifeMine website at lifeminetx.com: the route index of the site's content management system, catalogued as one site surface rather...

LifeMine Board API

Board-level metadata.

LifeMine Departments API

Department taxonomy.

LifeMine Education API

Greenhouse education reference data used by application forms.

LifeMine Jobs API

Open roles.

LifeMine Offices API

Office / location taxonomy.

LifeMine Sections API

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

LifeMine API Rules

57 rules · 51 errors 5 warnings 1 info

SPECTRAL

OpenAPI Overlays 2

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Lifemine Careers Overlay

8 actions · update · lifemine-careers-openapi.yml

DERIVED

Lifemine Content Overlay

10 actions · update · lifemine-content-openapi.yml

DERIVED

JSON Schema 7

Standalone JSON Schema definitions for this provider's data models.

Lifemine Categories

0 properties

JSON SCHEMA

Lifemine Media

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Lifemine Authentication

apiKey/http · 2 schemes

SECURITY

Lifemine Domain Security

TLSv1.3 · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Lifemine Agentic Access

12 operations

12 operations · 0 acting

AGENTIC

Resources

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

AgenticAccess

AgenticAccess

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Build 1

SDKs, sample code, and the tooling you integrate with

ToolCrosswalk

ToolCrosswalk

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Contact

Contact

Support

Support

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Company 7

The organization behind the API

Website

About

Blog

News

BlogRSS

Careers

LinkedIn

Scroll for all 7

Other 4

Properties that don't map to a standard resource type

Overlay

Science

Pipeline

SecondaryMarket

Source (apis.yml)

aid: lifemine
name: LifeMine
description: 'LifeMine (LifeMine Therapeutics) 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 in 2017 by Gregory Verdine, Richard Klausner and WeiQing Zhou, the company
  is headquartered in Watertown, Massachusetts with sites in Gloucester, Massachusetts and Basel, Switzerland, and has raised
  more than $320 million. Its lead programme, LIFE-001, is a structurally novel calcineurin inhibitor that entered a first-in-human
  Phase 1 trial in April 2025. LifeMine publishes no developer portal and no API documentation, and its drug-discovery platform
  is not exposed publicly. It does, however, operate two genuinely public, anonymous, machine-readable read APIs as byproducts
  of the platforms it runs: a WordPress REST API serving its news, pages, media and a structured leadership/board record set,
  and a Greenhouse job board API serving its open roles, departments and offices.'
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: true
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://lifeminetx.com/wp-content/uploads/2024/05/cropped-Favicon-B.png
url: https://raw.githubusercontent.com/api-evangelist/lifemine/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: enriched
x-tier-reason: enrichment-pipeline
specificationVersion: '0.23'
created: '2026-08-04'
modified: '2026-08-04'
tags:
- Company
- Biotechnology
- Pharmaceuticals
- Drug Discovery
- Life Sciences
- Clinical Trials
- Genomics
- Content
- Careers
- WordPress
apis:
- aid: lifemine:lifeminetx-com-website-wordpress-rest
  name: LifeMine Website (WordPress REST)
  description: 'The public WordPress REST API (wp-json) of the LifeMine website at lifeminetx.com: the route index of the
    site''s content management system, catalogued as one site surface rather than as separate APIs.'
  baseURL: https://lifeminetx.com/wp-json
  tags:
  - WordPress
  x-surface: platform-generated
  properties:
  - type: Documentation
    url: https://lifeminetx.com/wp-json
  x-platform: wordpress
  x-platform-surface: rest
- aid: lifemine:lifemine-board-api
  name: LifeMine Board API
  description: Board-level metadata.
  humanURL: https://lifeminetx.com/
  baseURL: https://boards-api.greenhouse.io/v1/boards/lifeminetx
  tags:
  - Boards
  tags_raw:
  - board
  properties:
  - type: OpenAPI
    url: openapi/lifemine-board-api-openapi.yml
  - type: JSONSchema
    url: json-schema/lifemine-posts-schema.json
  - type: JSONSchema
    url: json-schema/lifemine-team-schema.json
  - type: Examples
    url: examples/lifemine-posts-example.json
  - type: GraphQL
    url: graphql/lifemine-graphql.yml
  - type: Examples
    url: examples/lifemine-careers-jobs-example.json
- aid: lifemine:lifemine-departments-api
  name: LifeMine Departments API
  description: Department taxonomy.
  humanURL: https://lifeminetx.com/
  baseURL: https://boards-api.greenhouse.io/v1/boards/lifeminetx
  tags:
  - Departments
  tags_raw:
  - departments
  properties:
  - type: OpenAPI
    url: openapi/lifemine-departments-api-openapi.yml
  - type: JSONSchema
    url: json-schema/lifemine-posts-schema.json
  - type: JSONSchema
    url: json-schema/lifemine-team-schema.json
  - type: Examples
    url: examples/lifemine-posts-example.json
  - type: GraphQL
    url: graphql/lifemine-graphql.yml
  - type: Examples
    url: examples/lifemine-careers-jobs-example.json
- aid: lifemine:lifemine-education-api
  name: LifeMine Education API
  description: Greenhouse education reference data used by application forms.
  humanURL: https://lifeminetx.com/
  baseURL: https://boards-api.greenhouse.io/v1/boards/lifeminetx
  tags:
  - Education
  tags_raw:
  - education
  properties:
  - type: OpenAPI
    url: openapi/lifemine-education-api-openapi.yml
  - type: JSONSchema
    url: json-schema/lifemine-posts-schema.json
  - type: JSONSchema
    url: json-schema/lifemine-team-schema.json
  - type: Examples
    url: examples/lifemine-posts-example.json
  - type: GraphQL
    url: graphql/lifemine-graphql.yml
  - type: Examples
    url: examples/lifemine-careers-jobs-example.json
- aid: lifemine:lifemine-jobs-api
  name: LifeMine Jobs API
  description: Open roles.
  humanURL: https://lifeminetx.com/
  baseURL: https://boards-api.greenhouse.io/v1/boards/lifeminetx
  tags:
  - Job
  tags_raw:
  - jobs
  properties:
  - type: OpenAPI
    url: openapi/lifemine-jobs-api-openapi.yml
  - type: JSONSchema
    url: json-schema/lifemine-posts-schema.json
  - type: JSONSchema
    url: json-schema/lifemine-team-schema.json
  - type: Examples
    url: examples/lifemine-posts-example.json
  - type: GraphQL
    url: graphql/lifemine-graphql.yml
  - type: Examples
    url: examples/lifemine-careers-jobs-example.json
- aid: lifemine:lifemine-offices-api
  name: LifeMine Offices API
  description: Office / location taxonomy.
  humanURL: https://lifeminetx.com/
  baseURL: https://boards-api.greenhouse.io/v1/boards/lifeminetx
  tags:
  - Offices
  tags_raw:
  - offices
  properties:
  - type: OpenAPI
    url: openapi/lifemine-offices-api-openapi.yml
  - type: JSONSchema
    url: json-schema/lifemine-posts-schema.json
  - type: JSONSchema
    url: json-schema/lifemine-team-schema.json
  - type: Examples
    url: examples/lifemine-posts-example.json
  - type: GraphQL
    url: graphql/lifemine-graphql.yml
  - type: Examples
    url: examples/lifemine-careers-jobs-example.json
- aid: lifemine:lifemine-sections-api
  name: LifeMine Sections API
  description: Board sections (empty on this board).
  humanURL: https://lifeminetx.com/
  baseURL: https://boards-api.greenhouse.io/v1/boards/lifeminetx
  tags:
  - Sections
  tags_raw:
  - sections
  properties:
  - type: OpenAPI
    url: openapi/lifemine-sections-api-openapi.yml
  - type: JSONSchema
    url: json-schema/lifemine-posts-schema.json
  - type: JSONSchema
    url: json-schema/lifemine-team-schema.json
  - type: Examples
    url: examples/lifemine-posts-example.json
  - type: GraphQL
    url: graphql/lifemine-graphql.yml
  - type: Examples
    url: examples/lifemine-careers-jobs-example.json
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Contact
  url: https://lifeminetx.com/contact/
- type: Overlay
  url: overlays/lifemine-careers-overlay.yaml
- type: Website
  url: https://lifeminetx.com/
- type: About
  url: https://lifeminetx.com/about/
- type: Science
  url: https://lifeminetx.com/science/
- type: Pipeline
  url: https://lifeminetx.com/pipeline/
- type: Blog
  url: https://lifeminetx.com/blog/
- type: News
  url: https://lifeminetx.com/news/
- type: BlogRSS
  url: https://lifeminetx.com/feed/
- type: Support
  url: https://lifeminetx.com/contact/
- type: Careers
  url: https://lifeminetx.com/culture-careers/
- type: PrivacyPolicy
  url: https://lifeminetx.com/privacy-policy/
- type: LinkedIn
  url: https://www.linkedin.com/company/lifemine-therapeutics
- type: SecondaryMarket
  name: Forge Global
  url: https://forgeglobal.com/lifemine_stock/
- type: Authentication
  url: authentication/lifemine-authentication.yml
- type: Conventions
  url: conventions/lifemine-conventions.yml
- type: ErrorCatalog
  url: errors/lifemine-problem-types.yml
- type: Lifecycle
  url: lifecycle/lifemine-lifecycle.yml
- type: Conformance
  url: conformance/lifemine-conformance.yml
- type: DataModel
  url: data-model/lifemine-data-model.yml
- type: WellKnown
  url: well-known/lifemine-well-known.yml
- type: DomainSecurity
  url: security/lifemine-domain-security.yml
- type: AgenticAccess
  url: agentic-access/lifemine-agentic-access.yml
- type: X-MCPServerCandidate
  url: mcp/lifemine-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: ToolCrosswalk
  url: mcp/lifemine-tool-crosswalk.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/lifemine-llms.txt
x-enrichment-notes:
  no_fabrication_record: 'The following canonical pointers are deliberately ABSENT because the underlying thing does not exist,
    and each absence was verified rather than assumed: AgentCard (both /.well-known/agent-card.json and /.well-known/agent.json
    returned 404); SecurityTxt and Security (/.well-known/security.txt returned 404, no disclosure page or bug bounty found);
    Compliance and TrustCenter (no trust centre, no published certifications); SDKs and Packages (no first-party client library
    in any registry); StatusPage and Deprecation (no status page, no deprecation policy, no Sunset headers); Idempotency (no
    idempotency key anywhere in the 203 registered routes or the Greenhouse surface); AsyncAPI and Webhooks (no event or webhook
    surface); OAuthScopes (no OAuth); RateLimits (no published limits, no rate-limit headers); ChangeLog, CLI, Sandbox and
    Components (none published); DeclineCodes (not a payments provider); Documentation, APIReference, GettingStarted and DeveloperPortal
    (LifeMine publishes no API documentation of any kind — pointing these at the upstream WordPress or Greenhouse handbooks
    would credit LifeMine for someone else''s work); TermsOfService (/terms/ and /terms-of-use/ both 404); GitHubOrganization
    (github.com/LifeMine resolves but is empty, undescribed and unverifiable as this company); Postman, Pricing and SignUp
    (not applicable to a biotech with no API product).'
  spec_provenance: Neither OpenAPI in this repo was published by LifeMine. Both were derived by API Evangelist from documents
    fetched from the live hosts — the WordPress self-describing route index plus per-resource HTTP OPTIONS schemas, and the
    Greenhouse Job Board API documentation plus live payloads from LifeMine's own board. The unmodified WordPress route index
    is preserved at openapi/_original/lifemine-wp-json-index.json.
  graphql_gated: A live WPGraphQL endpoint exists at https://lifeminetx.com/graphql but public introspection is disabled.
    No SDL was captured and none was synthesized.
x-enrichment:
  date: '2026-08-04'
  status: enriched
  artifacts_added: 37
  pass: local-v1

LifeMine API — frequently asked questions

Does LifeMine have an API?

Yes. APIs.io lists 7 APIs from LifeMine, including LifeMine Website (WordPress REST), LifeMine Board API and LifeMine Departments API, and 4 more.

Is there an OpenAPI specification for the LifeMine API?

Yes. APIs.io indexes 6 OpenAPI specifications for LifeMine, each linked for download from this page.

How do I authenticate with the LifeMine API?

LifeMine uses bearer-token authentication (apiKey/http · 2 schemes). The details are profiled on APIs.io as Lifemine Authentication.

Is the LifeMine API ready for AI agents?

LifeMine has a Kin Score of 25.7 out of 100 (emerging) and an Agent Readiness score of 28.1 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/lifemine"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/lifemine/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/lifemine/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.