TRexBio
TRexBio, Inc. is a clinical-stage biotechnology company headquartered at 681 Gateway Blvd in South San Francisco, California, founded in 2018 and seed funded by SV Health Investors, that discovers and develops immunoregulatory biologics based on tissue regulatory T cell (Treg) biology. Its Deep Biology Platform combines human tissue samples, computational biology and immunobiology expertise to map how tissue Tregs behave in disease and to identify and characterize novel targets for inflammatory, autoimmune and other immune-mediated conditions. Disclosed programs include TRB-061, the CD30 agonist TRB-071, TRB-081, and the Lilly-partnered TRB-051, with Phase 1 trials expected to initiate in 2027. The company announced an $84 million Series B in November 2024 and closed a further $50 million financing in January 2026; investors include Eli Lilly and Company, Pfizer Ventures, Johnson & Johnson, SV Health Investors and Polaris Partners. TRexBio publishes no developer program, API documentation, SDK or machine-readable API contract. trex.bio is a WordPress marketing site whose only machine-readable surfaces are the WordPress core REST API, a Yoast-generated llms.txt, and an OAuth-protected WordPress MCP adapter endpoint — CMS infrastructure rather than a product API.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles TRexBio the way a machine reads it — 2 machine-readable artifacts, 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 — TRexBio scores 13.5/100 (emerging), with a separate agent-readiness read of 11/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
TRexBio is a clinical-stage Treg biologics company with no developer program at all — trex.bio is a WordPress/WP Engine marketing site, and the only machine-readable things on it are stock CMS plumbing: the WordPress core REST API at /wp-json/ (342 routes, all of them WordPress and plugin routes), a Yoast-SEO-generated /llms.txt listing news posts and careers pages, and an undocumented WordPress MCP adapter at /wp-json/mcp/mcp-oauth-server that returns 401 mcp_unauthorized to anonymous tools/list — there is no product API, no /openapi.json, no docs host, and github.com/trexbio has zero public repositories.
This is an honest zero, not a gap in our research. TRexBio does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://trex.bio/openapi.json→ HTTP 404https://trex.bio/graphql→ HTTP 404https://trex.bio/.well-known/agent-card.json→ HTTP 404https://trex.bio/wp-json/mcp/mcp-oauth-server→ HTTP 401https://trex.bio/llms.txt→ HTTP 200https://api.github.com/orgs/trexbio/repos→ HTTP 200
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.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from TRexBio'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/trexbio/"
title="TRexBio on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/trexbio.svg"
alt="TRexBio Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/trexbio/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/trexbio/"
title="TRexBio on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/trexbio/card.svg"
alt="TRexBio 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 TRexBio
Each block below is one kind of artifact we hold for TRexBio. 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.
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.
trexbio-mcp.yml
MCP SERVERSecurity Posture 1
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.
Resources
Every other property we hold for TRexBio — 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 3
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
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 7
The organization behind the API
Scroll within the panel for all 7 ·
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/trexbio · machine-readable index on apis.io
This is an independent, third-party profile of TRexBio, 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.