# Colossal Biosciences

> Colossal Biosciences is a Dallas, Texas de-extinction and species-preservation biotechnology company founded in 2021 by Ben Lamm and Harvard geneticist George Church. It applies ancient-DNA sequencing, comparative genomics, CRISPR multiplex genome editing, cloning and artificial-womb research to restoring extinct keystone species — the woolly mammoth, thylacine, dodo, moa, dire wolf and blue buck among them — and to conserving critically endangered living species.

IMPORTANT — read this before using anything below. Colossal Biosciences publishes NO product
or developer API, no developer portal, no API documentation and no SDK. The only
machine-readable surface on colossal.com is the WordPress REST API (wp/v2) that serves the
company newsroom, pages, media and site search as JSON, plus an authentication-gated
WordPress MCP Adapter endpoint. Treat it as a content/CMS API for reading Colossal's public
communications — not as an interface to Colossal's science, genomic data or laboratory
systems. None of Colossal's research data is exposed through any public API.

This file was GENERATED by the API Evangelist enrichment pipeline from the artifacts in
https://github.com/api-evangelist/colossal-biosciences — Colossal Biosciences does not
publish an llms.txt (https://colossal.com/llms.txt returns 404, probed 2026-08-04).

## APIs

- [Colossal Biosciences Content API (WordPress REST wp/v2)](https://colossal.com/wp-json/wp/v2): Anonymously readable JSON for newsroom posts, marketing pages, media library, categories, tags, comments, authors and site-wide search. 25 paths / 67 operations. Page-number pagination via page and per_page (max 100), with X-WP-Total and X-WP-TotalPages response headers and an RFC 8288 Link header.
- [Colossal Biosciences MCP Server (WordPress MCP Adapter)](https://colossal.com/wp-json/mcp/mcp-adapter-default-server): A live JSON-RPC MCP endpoint in the "mcp" namespace. AUTHENTICATION-GATED — an anonymous tools/list returns HTTP 401 rest_forbidden, as does the backing wp-abilities/v1 registry, so the published tool set is not publicly enumerable. Do not assume a tool set; introspect with credentials.

## Specs

- [Content API OpenAPI 3.1 (derived)](https://raw.githubusercontent.com/api-evangelist/colossal-biosciences/refs/heads/main/openapi/colossal-biosciences-content-openapi.yml): DERIVED by API Evangelist from the live route-discovery document at https://colossal.com/wp-json/. Not published by Colossal Biosciences.
- [WordPress route-discovery source](https://colossal.com/wp-json/): The provider's own machine-readable route index — 306 routes across 18 namespaces. The authoritative source for this API.
- [API Evangelist overlay](https://raw.githubusercontent.com/api-evangelist/colossal-biosciences/refs/heads/main/overlays/colossal-biosciences-content-overlay.yaml): OpenAPI Overlay 1.0.0 of API Evangelist annotations layered over the derived spec.

## How to call it

- Authentication: anonymous for all read operations. Writes require a WordPress Application Password over HTTP Basic, issued at https://colossal.com/wp-admin/authorize-application.php. There is no OAuth — /.well-known/oauth-authorization-server and /.well-known/openid-configuration both 404.
- Pagination: `?page=1&per_page=100`; read totals from `X-WP-Total` / `X-WP-TotalPages`.
- Trim payloads: `?_fields=id,title,link,date` returns only those top-level fields.
- Expand the graph: `?_embed` inlines author, `wp:featuredmedia`, `wp:term` and `replies` into `_embedded`.
- Errors: the WordPress envelope `{"code":..., "message":..., "data":{"status":...}}` — NOT RFC 9457 problem details.
- Idempotency: none. No idempotency key header or parameter exists on any route.
- Rate limits: not documented and not signalled by headers. robots.txt requests `Crawl-delay: 10` — honour it.
- There is no sandbox, no status page, no changelog, no CLI and no webhook or event surface.

## Agent skills

- [Read the Colossal newsroom](https://raw.githubusercontent.com/api-evangelist/colossal-biosciences/refs/heads/main/skills/colossal-biosciences-read-newsroom.md): Page through published news posts with authors, images and taxonomy resolved.
- [Search colossal.com and resolve results](https://raw.githubusercontent.com/api-evangelist/colossal-biosciences/refs/heads/main/skills/colossal-biosciences-search-site.md): Use the cross-type search endpoint and resolve each pointer to its full object.
- [Browse species pages and media](https://raw.githubusercontent.com/api-evangelist/colossal-biosciences/refs/heads/main/skills/colossal-biosciences-species-pages.md): Retrieve the species, science and glossary pages and their media assets.

## Docs

- [Company](https://colossal.com/company/)
- [Science & Technology](https://colossal.com/technology/)
- [Labs](https://colossal.com/labs/)
- [Our Species](https://colossal.com/species/)
- [Glossary](https://colossal.com/glossary/)
- [De-extinction Education](https://colossal.com/education/)
- [News & Insights](https://colossal.com/news/)
- [Podcast](https://colossal.com/podcast/)
- [Careers](https://colossal.com/careers/)
- [Terms of Use](https://colossal.com/terms-of-use/)
- [Privacy Policy](https://colossal.com/privacy-policy/)

## Related

- [Colossal Foundation](https://colossalfoundation.org/): Colossal's non-profit conservation arm.
- [colossal-compsci on GitHub](https://github.com/colossal-compsci): Colossal's computational-biology GitHub organization. Three first-party research repositories — tfboot (R, bootstrapping motifbreakR results), few-shot-bird-call (Python) and SSLUnsupDet (Python) — plus two forks of third-party models (GenNet, nucleotide-transformer). None is an API client library; no Colossal package is published to npm, PyPI, CRAN or any other registry.
- Form Bio (https://www.form.bio/): the computational life-sciences platform spun out of Colossal. A separate company with its own product surface — not covered by this file.

## Not available

- No OpenAPI published by Colossal Biosciences (the spec in this repo is derived).
- No llms.txt, security.txt, api-catalog, openid-configuration, oauth-authorization-server, ai-plugin.json, agent-card.json or agent.json — every /.well-known/ path returns 404 (probed 2026-08-04).
- No A2A agent card, no AsyncAPI, no webhooks, no gRPC, no Postman collection, no public pricing, no status page, no trust center, no published vulnerability-disclosure policy and no SOC 2 / ISO 27001 / HIPAA compliance program.