A month ago, we launched Gencove Consumer, a direct-to-consumer DNA test that uses low-pass whole genome sequencing to provide PRS results, ancestry, and access to raw data.
This week, we released developer access for Gencove Consumer, including a REST API, MCP server, and OAuth 2.0 flows for partner applications.
The goal is to make Gencove Consumer data easier to use outside of the Gencove application, while keeping access explicit and user-controlled. A consumer should be able to connect their genetic data to tools they choose. A partner should be able to build on top of Gencove data without having to operate the full genetics stack themselves.
This release is most relevant to developers and teams building products in consumer health, particularly in areas such as preventive care, fitness tracking, and longevity.
Why developer access matters
A DNA test is more useful when the data can be revisited and used in context.
PRS results, ancestry, and raw data are useful on their own, but they can also become part of broader consumer health products. A preventive care product may want to combine genetic predisposition with labs, family history, or clinical guidelines. A fitness product may want to incorporate genetic context alongside training, sleep, and recovery data. A longevity product may want to present genetics as one layer among biomarkers, habits, and longitudinal tracking.
Historically, this has been awkward to support. Consumer genetics products often expose data through reports or downloads, but not through integration surfaces that are easy for other applications to use. On the other side, consumer health companies that want to include genetics have to deal with sample logistics, sequencing, bioinformatics, authentication, consent, reporting, and support.
Most teams do not want to build all of that from scratch.
The developer platform is intended to provide a cleaner integration path. Gencove handles the genetics workflow and exposes the resulting consumer data through standard interfaces. Partners can then focus on their own product experience.
What we released
The Gencove Consumer developer platform exposes a user's data through three programmatic surfaces:
- A read-only REST API for direct programmatic access
- An MCP server for AI agents and developer tools
- OAuth 2.0 with PKCE for partner applications acting on behalf of a user
These surfaces are intended for different use cases, but they follow the same basic principle: access should be explicit and controlled by the user.
A Gencove user can create a personal API key to access their own data. A developer can connect an AI assistant or local tool through the MCP server. A partner application can request scoped access through OAuth so a consumer can authorize the data that the partner application is allowed to read.
REST API
The REST API provides read-only JSON endpoints for the core Gencove Consumer data model: profile information, kits, kit status, PRS trait scores, ancestry composition, and raw data files.
The API is designed around familiar web conventions: authenticated requests, JSON responses, pagination, clear status codes, and read-only GET endpoints. For individual users and developers experimenting with their own accounts, personal API keys provide the fastest path to get started.
The intent is to make common product questions straightforward to answer:
- Has this user's kit been processed?
- Which PRS traits are available?
- Which traits are in a higher-risk category?
- What is the user's ancestry composition?
- Is there a raw data file available for download?
These are the kinds of questions partner products often need to answer before deciding what to show to a user.
MCP
We also released an MCP server for Gencove Consumer.
MCP, or Model Context Protocol, gives AI tools a standard way to call external tools and retrieve structured data. For Gencove Consumer, the MCP server acts as a protocol adapter over the same data exposed by the REST API, with setup instructions for supported clients in the developer docs.
This makes it possible for a user to connect their Gencove account to an AI assistant or developer environment that supports MCP, and then ask questions such as:
- “What is the status of my Gencove kits?”
- “Show my ancestry breakdown.”
- “Which of my PRS scores are in the high-risk category?”
The assistant can call Gencove tools and answer using the user's data, rather than relying on manual uploads or copy-pasted exports.
We think this is a practical pattern for AI-based consumer health products. Genetic data is structured, personal, and often requires context. MCP provides a way to make that data available to AI tools through an authenticated interface, using a defined set of tools rather than an ad hoc file upload.
OAuth for partner applications
OAuth 2.0 with PKCE is the integration path for partners building consumer products that need to read a Gencove user's data on the user's behalf.
This is different from a personal API key. A personal API key is useful when a user or developer wants direct access to their own account. OAuth is more appropriate when a third-party application needs access after a user explicitly authorizes it.
With OAuth, a partner application can request specific scopes, such as profile:read, kits:read, prs:read, ancestry:read, or files:read. The user reviews the request and grants access. The partner receives a bearer token and can call the REST API or MCP server with the permissions the user approved.
For a consumer health application, this creates a more standard connection flow. A user can connect their Gencove account to a product they already use, and the partner application can retrieve the relevant data without asking the user to manually download and re-upload files.
The important design point is scoped access. A partner should request the data it needs, and the user should have a clear authorization step before that data is shared.
What partners can build
For partner teams, this release is most useful when genetics is one input among several.
- Preventive care: Help consumers understand genetic predisposition alongside age, sex, family history, labs, and screening recommendations.
- Longevity: Incorporate PRS and ancestry into a broader experience that already includes biomarkers, imaging, wearable signals, interventions, and longitudinal tracking.
- Fitness and performance: Use genetics as another layer of personalization, alongside training history, recovery, sleep, nutrition, and goals.
In each case, genetics does not need to be the entire product. It can be one data layer in a broader consumer experience.
That is the use case we are trying to support: making it easier for companies to incorporate consumer genetics where it is relevant, without forcing them to build the underlying sequencing and data infrastructure themselves.
Built around user-controlled access
Genetic data is personal, so the access model matters.
The Gencove Consumer developer platform is designed around read-only access, explicit authentication, scoped OAuth permissions for partner applications, and a separation between personal access and third-party access.
A personal API key is useful for a user accessing their own data. OAuth is the right path when a partner application needs access on behalf of that user. MCP makes the same underlying data available to AI tools through a structured interface.
This gives us a consistent model:
- Users can access their own data
- Developers can build with familiar tools
- Partners can request scoped access
- AI tools can interact with structured Gencove data
There is more to build, but this gives us a starting point for a more connected consumer genetics ecosystem.
Getting started
Developers can start with the Gencove Consumer developer documentation, which includes the REST API reference, MCP setup instructions, authentication details, and OAuth integration guidance.
For companies building in preventive care, fitness tracking, longevity, or adjacent consumer health categories, we would be interested in discussing partner integrations.
Gencove Consumer started as a way for individuals to access PRS, ancestry, and raw genetic data through a low-pass sequencing-based test. With API, MCP, and OAuth support, that data can now be used more easily in the products and tools consumers choose to connect.