Brightseed
Brightseed is a bioactives and AI company founded in 2017 (San Francisco, CA, with operations in Durham, NC) that uses its Forager AI platform to map the compounds in plants to human biological pathways and health benefits. Forager draws on a proprietary dataset the company describes as the world's largest — 21 million bioactive compounds and hundreds of biological receptors spanning 23 health areas — combining high-resolution omics, high-throughput robotics and machine learning to predict which natural compounds confer a benefit and where to source them at commercial scale. Hummingbird, launched in 2026, layers an agentic AI system on top of Forager to carry partners from discovery through development. Brightseed sells discovery services (Bioactive Profiler, Bioactive Ingredient Finder) and market-ready ingredients (Bio Gut Fiber, Bio Meta Control, Bio Gut Core) to food, supplement and health-science companies. Brightseed publishes no product or developer API for Forager or Hummingbird — those are sold as enterprise engagements through a contact form. The single machine-readable surface the company operates is the WordPress REST API (wp/v2) behind its corporate site at www.brightseedbio.com, which exposes anonymous read access to posts, pages, categories, tags, users, media, comments, search, taxonomies, types and statuses, plus authenticated write operations via WordPress application passwords. This profile was enriched by the API Evangelist pipeline from that live surface.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Brightseed the way a machine reads it — 26 machine-readable artifacts across 11 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Brightseed scores 32.0/100 (thin), with a separate agent-readiness read of 39/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Put this on your own site. The badge is drawn live from Brightseed's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/brightseed/"
title="Brightseed on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/brightseed.svg"
alt="Brightseed Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/brightseed/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/brightseed/"
title="Brightseed on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/brightseed/card.svg"
alt="Brightseed Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Brightseed
Each block below is one kind of artifact we hold for Brightseed. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Brightseed posts API
The posts API from Brightseed — 13 operation(s) for posts, served by the WordPress REST API wp/v2 namespace on www.brightseedbio.com.
Brightseed pages API
The pages API from Brightseed — 13 operation(s) for pages, served by the WordPress REST API wp/v2 namespace on www.brightseedbio.com.
Brightseed media API
The media API from Brightseed — 9 operation(s) for media, served by the WordPress REST API wp/v2 namespace on www.brightseedbio.com.
Brightseed categories API
The categories API from Brightseed — 7 operation(s) for categories, served by the WordPress REST API wp/v2 namespace on www.brightseedbio.com.
Brightseed tags API
The tags API from Brightseed — 7 operation(s) for tags, served by the WordPress REST API wp/v2 namespace on www.brightseedbio.com.
Brightseed users API
The users API from Brightseed — 21 operation(s) for users, served by the WordPress REST API wp/v2 namespace on www.brightseedbio.com.
Brightseed comments API
The comments API from Brightseed — 7 operation(s) for comments, served by the WordPress REST API wp/v2 namespace on www.brightseedbio.com.
Brightseed search API
The search API from Brightseed — 1 operation(s) for search, served by the WordPress REST API wp/v2 namespace on www.brightseedbio.com.
Brightseed taxonomies API
The taxonomies API from Brightseed — 2 operation(s) for taxonomies, served by the WordPress REST API wp/v2 namespace on www.brightseedbio.com.
Brightseed types API
The types API from Brightseed — 2 operation(s) for types, served by the WordPress REST API wp/v2 namespace on www.brightseedbio.com.
Brightseed statuses API
The statuses API from Brightseed — 2 operation(s) for statuses, served by the WordPress REST API wp/v2 namespace on www.brightseedbio.com.
Scroll within the panel for all 11 ·
Open Collections 11
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Brightseed Site Content API (WordPress REST API) media API
OPEN COLLECTIONBrightseed Site Content API (WordPress REST API) pages API
OPEN COLLECTIONBrightseed Site Content API (WordPress REST API) posts API
OPEN COLLECTIONBrightseed Site Content API (WordPress REST API) search API
OPEN COLLECTIONBrightseed Site Content API (WordPress REST API) tags API
OPEN COLLECTIONBrightseed Site Content API (WordPress REST API) types API
OPEN COLLECTIONBrightseed Site Content API (WordPress REST API) users API
OPEN COLLECTIONScroll within the panel for all 11 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
brightseed-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Brightseed — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 6
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 1
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 within the panel for all 8 ·
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/brightseed · machine-readable index on apis.io
This is an independent, third-party profile of Brightseed, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.