Enveda website screenshot

Enveda

Enveda (Enveda Biosciences) is a Boulder, Colorado based clinical-stage biotechnology company founded in 2019 that discovers medicines by decoding the chemistry of the natural world. It combines high-throughput mass spectrometry, metabolomics, robotics and machine learning — including PRISM, a foundation model trained on more than a billion small- molecule mass spectra — to build a searchable library of plant-derived molecules and translate them into drug candidates. Enveda has raised over $360M across Series B, C and D rounds from Premji Invest, Kinnevik, Lux Capital, Dimension and Sanofi, reached unicorn status in 2026, and runs FDA-cleared clinical programs including ENV-294 (atopic dermatitis and asthma), ENV-308 (obesity) and ENV-6946 (inflammatory bowel disease). Enveda publishes no product or developer API; the machine-readable surface on enveda.com is a published llms.txt plus the WordPress REST API (wp/v2) that serves the company newsroom, In-Veda blog, leadership profiles, clinical-trial site directory and media library as JSON, alongside a WordPress MCP Adapter endpoint that is present but authentication-gated. Its open science is published as research code and data in the github.com/enveda organization.

Enveda publishes 13 APIs on the APIs.io network, including Comments API, Discovery API, Issues API, and 10 more. Tagged areas include Company, Biotechnology, Drug Discovery, Life Sciences, and Artificial Intelligence.

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

23.3/100 emerging ▬ flat Agent 29/100 agent aware Full breakdown ↓
scored 2026-08-12 · rubric v0.11.0
14 APIs 1 MCP Servers
CompanyBiotechnologyDrug DiscoveryLife SciencesArtificial IntelligenceMachine LearningMetabolomicsNatural ProductsPharmaceuticalsClinical TrialsResearchContent

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-12 · rubric v0.11.0
Composite quality — 23.3/100 · emerging
Contract Quality 3.1 / 21
Developer Ergonomics 3.2 / 17
Commercial Clarity 3.6 / 17
Operational Transparency 0.6 / 11
Governance 1.2 / 10
Discoverability 6.9 / 9
Regulatory Posture 4.7 / 15
Agent readiness — 29/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 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 0 / 4
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.
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/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/enveda-biosciences: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 14

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

Enveda MCP Server (WordPress MCP Adapter)

A Model Context Protocol server endpoint advertised in the enveda.com WordPress REST route index under the "mcp" namespace and served at /wp-json/mcp/mcp-adapter-default-server....

Enveda Comments API

The Comments API from Enveda — 2 operation(s) for comments.

Enveda Discovery API

The Discovery API from Enveda — 6 operation(s) for discovery.

Enveda Issues API

The Issues API from Enveda — 2 operation(s) for issues.

Enveda Media API

The Media API from Enveda — 3 operation(s) for media.

Enveda News API

The News API from Enveda — 4 operation(s) for news.

Enveda Pages API

The Pages API from Enveda — 2 operation(s) for pages.

Enveda People API

The People API from Enveda — 4 operation(s) for people.

Enveda Posts API

The Posts API from Enveda — 2 operation(s) for posts.

Enveda Search API

The Search API from Enveda — 1 operation(s) for search.

Enveda Settings API

The Settings API from Enveda — 1 operation(s) for settings.

Enveda Taxonomy API

The Taxonomy API from Enveda — 4 operation(s) for taxonomy.

Enveda Trial Sites API

The Trial Sites API from Enveda — 4 operation(s) for trial sites.

Enveda Users API

The Users API from Enveda — 3 operation(s) for users.

Scroll for all 14

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Security Posture 2

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

Enveda Biosciences Authentication

http · 1 scheme

SECURITY

Enveda Biosciences Domain Security

TLSv1.3 · DNSSEC · DMARC

SECURITY

Agentic Access 1

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

Enveda Biosciences Agentic Access

115 operations · 78 acting

115 operations · 78 acting

AGENTIC

Resources

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 8

The organization behind the API

Scroll for all 8

Other 5

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: enveda-biosciences
name: Enveda
description: Enveda (Enveda Biosciences) is a Boulder, Colorado based clinical-stage biotechnology company founded in 2019
  that discovers medicines by decoding the chemistry of the natural world. It combines high-throughput mass spectrometry,
  metabolomics, robotics and machine learning — including PRISM, a foundation model trained on more than a billion small-
  molecule mass spectra — to build a searchable library of plant-derived molecules and translate them into drug candidates.
  Enveda has raised over $360M across Series B, C and D rounds from Premji Invest, Kinnevik, Lux Capital, Dimension and Sanofi,
  reached unicorn status in 2026, and runs FDA-cleared clinical programs including ENV-294 (atopic dermatitis and asthma),
  ENV-308 (obesity) and ENV-6946 (inflammatory bowel disease). Enveda publishes no product or developer API; the machine-readable
  surface on enveda.com is a published llms.txt plus the WordPress REST API (wp/v2) that serves the company newsroom, In-Veda
  blog, leadership profiles, clinical-trial site directory and media library as JSON, alongside a WordPress MCP Adapter endpoint
  that is present but authentication-gated. Its open science is published as research code and data in the github.com/enveda
  organization.
url: https://raw.githubusercontent.com/api-evangelist/enveda-biosciences/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment-pipeline
image: https://enveda.com/wp-content/uploads/2026/06/cropped-enveda-favicon.jpg
specificationVersion: '0.20'
created: '2026-08-04'
modified: '2026-08-04'
tags:
- Company
- Biotechnology
- Drug Discovery
- Life Sciences
- Artificial Intelligence
- Machine Learning
- Metabolomics
- Natural Products
- Pharmaceuticals
- Clinical Trials
- Research
- Content
apis:
- aid: enveda-biosciences:mcp
  name: Enveda MCP Server (WordPress MCP Adapter)
  description: 'A Model Context Protocol server endpoint advertised in the enveda.com WordPress REST route index under the
    "mcp" namespace and served at /wp-json/mcp/mcp-adapter-default-server. The endpoint is live but authentication-gated:
    an anonymous JSON-RPC tools/list returns HTTP 401 rest_forbidden, as does initialize and the companion wp-abilities/v1
    abilities registry, so the published tool set could not be enumerated.'
  humanURL: https://enveda.com/wp-json/mcp
  baseURL: https://enveda.com/wp-json/mcp/mcp-adapter-default-server
  tags:
  - MCP
  - Agents
  properties:
  - type: MCPServer
    url: mcp/enveda-biosciences-mcp.yml
  - type: ToolCrosswalk
    url: mcp/enveda-biosciences-tool-crosswalk.yml
- aid: enveda-biosciences:enveda-biosciences-comments-api
  name: Enveda Comments API
  description: The Comments API from Enveda — 2 operation(s) for comments.
  humanURL: https://enveda.com/news/
  baseURL: https://enveda.com/wp-json/wp/v2
  tags:
  - Comments
  properties:
  - type: OpenAPI
    url: openapi/enveda-biosciences-comments-api-openapi.yml
  - type: DataModel
    url: data-model/enveda-biosciences-data-model.yml
  - type: ErrorCatalog
    url: errors/enveda-biosciences-problem-types.yml
  - type: Examples
    url: examples/enveda-biosciences-examples.yml
- aid: enveda-biosciences:enveda-biosciences-discovery-api
  name: Enveda Discovery API
  description: The Discovery API from Enveda — 6 operation(s) for discovery.
  humanURL: https://enveda.com/news/
  baseURL: https://enveda.com/wp-json/wp/v2
  tags:
  - Discovery
  properties:
  - type: OpenAPI
    url: openapi/enveda-biosciences-discovery-api-openapi.yml
  - type: DataModel
    url: data-model/enveda-biosciences-data-model.yml
  - type: ErrorCatalog
    url: errors/enveda-biosciences-problem-types.yml
  - type: Examples
    url: examples/enveda-biosciences-examples.yml
- aid: enveda-biosciences:enveda-biosciences-issues-api
  name: Enveda Issues API
  description: The Issues API from Enveda — 2 operation(s) for issues.
  humanURL: https://enveda.com/news/
  baseURL: https://enveda.com/wp-json/wp/v2
  tags:
  - Issues
  properties:
  - type: OpenAPI
    url: openapi/enveda-biosciences-issues-api-openapi.yml
  - type: DataModel
    url: data-model/enveda-biosciences-data-model.yml
  - type: ErrorCatalog
    url: errors/enveda-biosciences-problem-types.yml
  - type: Examples
    url: examples/enveda-biosciences-examples.yml
- aid: enveda-biosciences:enveda-biosciences-media-api
  name: Enveda Media API
  description: The Media API from Enveda — 3 operation(s) for media.
  humanURL: https://enveda.com/news/
  baseURL: https://enveda.com/wp-json/wp/v2
  tags:
  - Media
  properties:
  - type: OpenAPI
    url: openapi/enveda-biosciences-media-api-openapi.yml
  - type: DataModel
    url: data-model/enveda-biosciences-data-model.yml
  - type: ErrorCatalog
    url: errors/enveda-biosciences-problem-types.yml
  - type: Examples
    url: examples/enveda-biosciences-examples.yml
- aid: enveda-biosciences:enveda-biosciences-news-api
  name: Enveda News API
  description: The News API from Enveda — 4 operation(s) for news.
  humanURL: https://enveda.com/news/
  baseURL: https://enveda.com/wp-json/wp/v2
  tags:
  - News
  properties:
  - type: OpenAPI
    url: openapi/enveda-biosciences-news-api-openapi.yml
  - type: DataModel
    url: data-model/enveda-biosciences-data-model.yml
  - type: ErrorCatalog
    url: errors/enveda-biosciences-problem-types.yml
  - type: Examples
    url: examples/enveda-biosciences-examples.yml
- aid: enveda-biosciences:enveda-biosciences-pages-api
  name: Enveda Pages API
  description: The Pages API from Enveda — 2 operation(s) for pages.
  humanURL: https://enveda.com/news/
  baseURL: https://enveda.com/wp-json/wp/v2
  tags:
  - Pages
  properties:
  - type: OpenAPI
    url: openapi/enveda-biosciences-pages-api-openapi.yml
  - type: DataModel
    url: data-model/enveda-biosciences-data-model.yml
  - type: ErrorCatalog
    url: errors/enveda-biosciences-problem-types.yml
  - type: Examples
    url: examples/enveda-biosciences-examples.yml
- aid: enveda-biosciences:enveda-biosciences-people-api
  name: Enveda People API
  description: The People API from Enveda — 4 operation(s) for people.
  humanURL: https://enveda.com/news/
  baseURL: https://enveda.com/wp-json/wp/v2
  tags:
  - People
  properties:
  - type: OpenAPI
    url: openapi/enveda-biosciences-people-api-openapi.yml
  - type: DataModel
    url: data-model/enveda-biosciences-data-model.yml
  - type: ErrorCatalog
    url: errors/enveda-biosciences-problem-types.yml
  - type: Examples
    url: examples/enveda-biosciences-examples.yml
- aid: enveda-biosciences:enveda-biosciences-posts-api
  name: Enveda Posts API
  description: The Posts API from Enveda — 2 operation(s) for posts.
  humanURL: https://enveda.com/news/
  baseURL: https://enveda.com/wp-json/wp/v2
  tags:
  - Posts
  properties:
  - type: OpenAPI
    url: openapi/enveda-biosciences-posts-api-openapi.yml
  - type: DataModel
    url: data-model/enveda-biosciences-data-model.yml
  - type: ErrorCatalog
    url: errors/enveda-biosciences-problem-types.yml
  - type: Examples
    url: examples/enveda-biosciences-examples.yml
- aid: enveda-biosciences:enveda-biosciences-search-api
  name: Enveda Search API
  description: The Search API from Enveda — 1 operation(s) for search.
  humanURL: https://enveda.com/news/
  baseURL: https://enveda.com/wp-json/wp/v2
  tags:
  - Search
  properties:
  - type: OpenAPI
    url: openapi/enveda-biosciences-search-api-openapi.yml
  - type: DataModel
    url: data-model/enveda-biosciences-data-model.yml
  - type: ErrorCatalog
    url: errors/enveda-biosciences-problem-types.yml
  - type: Examples
    url: examples/enveda-biosciences-examples.yml
- aid: enveda-biosciences:enveda-biosciences-settings-api
  name: Enveda Settings API
  description: The Settings API from Enveda — 1 operation(s) for settings.
  humanURL: https://enveda.com/news/
  baseURL: https://enveda.com/wp-json/wp/v2
  tags:
  - Settings
  properties:
  - type: OpenAPI
    url: openapi/enveda-biosciences-settings-api-openapi.yml
  - type: DataModel
    url: data-model/enveda-biosciences-data-model.yml
  - type: ErrorCatalog
    url: errors/enveda-biosciences-problem-types.yml
  - type: Examples
    url: examples/enveda-biosciences-examples.yml
- aid: enveda-biosciences:enveda-biosciences-taxonomy-api
  name: Enveda Taxonomy API
  description: The Taxonomy API from Enveda — 4 operation(s) for taxonomy.
  humanURL: https://enveda.com/news/
  baseURL: https://enveda.com/wp-json/wp/v2
  tags:
  - Taxonomy
  properties:
  - type: OpenAPI
    url: openapi/enveda-biosciences-taxonomy-api-openapi.yml
  - type: DataModel
    url: data-model/enveda-biosciences-data-model.yml
  - type: ErrorCatalog
    url: errors/enveda-biosciences-problem-types.yml
  - type: Examples
    url: examples/enveda-biosciences-examples.yml
- aid: enveda-biosciences:enveda-biosciences-trial-sites-api
  name: Enveda Trial Sites API
  description: The Trial Sites API from Enveda — 4 operation(s) for trial sites.
  humanURL: https://enveda.com/news/
  baseURL: https://enveda.com/wp-json/wp/v2
  tags:
  - Trial Sites
  properties:
  - type: OpenAPI
    url: openapi/enveda-biosciences-trial-sites-api-openapi.yml
  - type: DataModel
    url: data-model/enveda-biosciences-data-model.yml
  - type: ErrorCatalog
    url: errors/enveda-biosciences-problem-types.yml
  - type: Examples
    url: examples/enveda-biosciences-examples.yml
- aid: enveda-biosciences:enveda-biosciences-users-api
  name: Enveda Users API
  description: The Users API from Enveda — 3 operation(s) for users.
  humanURL: https://enveda.com/news/
  baseURL: https://enveda.com/wp-json/wp/v2
  tags:
  - Users
  properties:
  - type: OpenAPI
    url: openapi/enveda-biosciences-users-api-openapi.yml
  - type: DataModel
    url: data-model/enveda-biosciences-data-model.yml
  - type: ErrorCatalog
    url: errors/enveda-biosciences-problem-types.yml
  - type: Examples
    url: examples/enveda-biosciences-examples.yml
x-enrichment:
  date: '2026-08-04'
  status: enriched
  artifacts_added: 20
  pass: local-v1
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Overlay
  url: overlays/enveda-biosciences-content-overlay.yaml
- type: Website
  url: https://enveda.com/
- type: About
  url: https://enveda.com/purpose/
- type: Blog
  url: https://enveda.com/in-veda/
- type: BlogRSS
  url: https://enveda.com/feed/
- type: News
  url: https://enveda.com/news/
- type: Press
  url: https://enveda.com/press/
- type: Support
  url: https://enveda.com/contact/
- type: Careers
  url: https://enveda.com/careers/
- type: Team
  url: https://enveda.com/people/
- type: Technology
  url: https://enveda.com/platform/
- type: Pipeline
  url: https://enveda.com/pipeline/
- type: TermsOfService
  url: https://enveda.com/terms-of-service/
- type: PrivacyPolicy
  url: https://enveda.com/privacy-policy/
- type: GitHubOrganization
  url: https://github.com/enveda
- type: LinkedIn
  url: https://www.linkedin.com/company/envedabio
- type: Packages
  url: packages/enveda-biosciences-packages.yml
- type: LLMsTxt
  url: llms/enveda-biosciences-llms.txt
- type: WellKnown
  url: well-known/enveda-biosciences-well-known.yml
- type: Authentication
  url: authentication/enveda-biosciences-authentication.yml
- type: Conventions
  url: conventions/enveda-biosciences-conventions.yml
- type: Conformance
  url: conformance/enveda-biosciences-conformance.yml
- type: Lifecycle
  url: lifecycle/enveda-biosciences-lifecycle.yml
- type: DomainSecurity
  url: security/enveda-biosciences-domain-security.yml
- type: AgenticAccess
  url: agentic-access/enveda-biosciences-agentic-access.yml
- type: AgentSkill
  url: skills/_index.yml
- type: SecondaryMarket
  url: https://forgeglobal.com/enveda-biosciences_stock/