AusperBio
AusperBio — AusperBio Therapeutics, Inc. in the United States and Ausper Biopharma Co., Ltd. (杭州浩博医药有限公司) in Hangzhou, China — is a clinical-stage biopharmaceutical company founded in 2019 that develops oligonucleotide and targeted delivery technologies, with an initial focus on achieving a functional cure for chronic hepatitis B infection. Its proprietary Med-Oligo antisense oligonucleotide (ASO) platform pairs novel ASO design and optimization with targeted delivery conjugation chemistry, and its Au-HALO hepatocyte-targeting delivery technology extends the same modular approach to siRNA. The lead candidate AHB-137 is an unconjugated ASO that completed enrollment in two Phase II trials and received China CDE clearance to enter Phase III; a second clinical candidate, AHB-171, is a hepatocyte-targeted siRNA. The company has raised more than $200M across Series B, B+ and B2 rounds from investors including Qiming Venture Partners, HanKang Capital, CDH Investments, Sherpa Capital, YuanBio Venture Capital and Genesis Capital. AusperBio sells therapeutics, not software: it publishes no developer program, no public API, no SDK and no machine-readable API contract. Its only machine-readable surface is the private Spring Boot CMS backend that renders ausperbio.com, whose springdoc API description is correctly locked behind authentication.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles AusperBio the way a machine reads it — 1 machine-readable artifact, 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 — AusperBio scores 12.2/100 (minimal), with a separate agent-readiness read of 0/100 (human only). 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
AusperBio develops antisense-oligonucleotide and siRNA drugs for chronic hepatitis B, so there is no software product to expose; ausperbio.com is a Vue single-page app that returns an identical 2,601-byte shell (md5 519d85ce…) for every path including invented ones, and the only machine-readable API description on the estate is the springdoc description of the private Spring Boot CMS at cms.ausperbio.com/jzy-admin/, which is correctly 401-gated and is site infrastructure rather than a product surface.
This is an honest zero, not a gap in our research. AusperBio 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://www.ausperbio.com/openapi.json→ HTTP 200https://www.ausperbio.com/definitely-not-a-real-path-zzz999→ HTTP 200https://www.ausperbio.com/llms.txt→ HTTP 200https://www.ausperbio.com/.well-known/agent-card.json→ HTTP 200https://cms.ausperbio.com/jzy-admin/v3/api-docs→ HTTP 200https://cms.ausperbio.com/jzy-admin/doc.html→ HTTP 401https://api.ausperbio.com/→ HTTP 0
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 AusperBio'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/ausperbio/"
title="AusperBio on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/ausperbio.svg"
alt="AusperBio Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/ausperbio/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/ausperbio/"
title="AusperBio on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/ausperbio/card.svg"
alt="AusperBio 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 AusperBio
Each block below is one kind of artifact we hold for AusperBio. 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.
Security 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 AusperBio — 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 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/ausperbio · machine-readable index on apis.io
This is an independent, third-party profile of AusperBio, 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.