Circle Pharma
Circle Pharma is a clinical-stage biopharmaceutical company in South San Francisco, California, developing cell-permeable, orally bioavailable macrocycle therapies for cancer. Founded in 2013 by Matthew P. Jacobson and Scott Lokey out of work on predicting synthetic macrocycle cell permeability, the company applies its proprietary MXMO structure-based design platform to protein-protein interactions that conventional small molecules cannot reach. Its pipeline targets cyclins, the regulators of the cell cycle that drive many cancers: lead program CID-078, a first-in-class oral cyclin A/B RxL inhibitor, is in Phase 1 for advanced solid tumors, followed by a preclinical cyclin D1 RxL inhibitor and undisclosed cyclin programs partnered with Boehringer Ingelheim. Circle Pharma closed a $90M Series D led by The Column Group in 2024 and has an agreement with Eli Lilly to use Lilly TuneLab to strengthen the AI/ML side of the MXMO platform. Circle Pharma runs no developer program and publishes no product API; the only machine-readable surface it exposes is the anonymously readable WordPress REST content API behind circlepharma.com.
Circle Pharma publishes 1 API on the APIs.io network: Content API. Tagged areas include Company, Biotechnology, Pharmaceuticals, Oncology, and Drug Discovery.
Circle Pharma’s developer surface includes engineering blog, support, authentication, and 22 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Circle Pharma Content API
The anonymously readable WordPress REST API behind circlepharma.com. It exposes Circle Pharma press releases, publications and in-the-news items (posts), site pages, the media l...
Open Collections 1
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Circle Pharma Content API (WordPress REST API)
OPEN COLLECTIONSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 3
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 for all 7
Other 3
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for providers
9 MCP tools reach this
find_providersBrowse and filter every provider in the catalog.get_provider_artifactsEvery artifact this provider publishes, grouped by type.get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.get_provider_toolsEvery MCP tool they ship, with the operation each wraps.get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.get_provider_ratingPRO — composite, band, trend and facet scores.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/providers/circle-pharma"
curl "https://apis.io/api/v1/providers?limit=25"
curl "https://apis.io/api/v1/providers/circle-pharma/operations?limit=25"
curl "https://apis.io/api/v1/providers/circle-pharma/evidence"
Discovery needs no key. Ratings and market analysis are Pro.