University of Science and Technology of China
The University of Science and Technology of China (USTC, 中国科学技术大学) is a public research university in Hefei, Anhui, founded in 1958 under the Chinese Academy of Sciences, a member of the C9 League and ranked #63 in the QS World University Rankings 2025. USTC publishes no developer portal, no open-data platform and no institutional API program — but it is not the empty profile an earlier pass recorded. Its Network Information Center runs and DOCUMENTS a genuine identity platform: a first-party CAS 3.0 / OAuth 2.0 / OpenID Connect authorization server at id.ustc.edu.cn with an anonymously readable discovery document and JWKS, a developer manual with parameter tables and worked examples at id.ustc.edu.cn/doc/developer/, an enrollment-status query API with a published error table and a public health check, and a self-hosted Shibboleth 5.2.2 identity provider at idp.ustc.edu.cn whose SAML 2.0 metadata is the strongest machine-readable contract in this profile — federating into CARSI, the CAS Science Cloud AAI and eduGAIN. Beyond identity, USTC operates a course catalog with a live JSON API at catalog.ustc.edu.cn (401 to the public, and self-declaring restricted mode), the USTC Open Source Software Mirror on the university's own APNIC allocation, a campus GitLab, a supercomputing centre, and its own DeepSeek-based AI assistant with a published user agreement. Every one of those surfaces is institution-operated; almost every one is gated to campus members, and USTC states plainly that applications outside the ustc.edu.cn domain are not supported. No vendor contract is attributed to USTC in this profile — no Figshare, Pure, Ex Libris, Dataverse or Canvas surface was found under its name.
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 University of Science and Technology of China the way a machine reads it — 16 machine-readable artifacts across 1 API, 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 — University of Science and Technology of China scores 37.6/100 (thin), with a separate agent-readiness read of 26/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
USTC operates real, institution-owned API surfaces and documents some of them well, but an unaffiliated caller cannot consume any of them. The unified identity authorization server at id.ustc.edu.cn publishes an anonymously readable OIDC discovery document and JWKS, yet a client_id exists only after a manual registration and filing process, and USTC states explicitly that applications not deployed on campus and not on a ustc.edu.cn domain are not supported at all — the clearest such statement found in this cohort. The enrollment status API returns 200 on its public health check and 401 on every business path, and requires both an administrator-issued bearer token and a registered source IP. The course catalog's eighteen /api/teach/ routes answer 401 and the application declares itself restricted at /api/restricted. The library OPAC returns 200 with a prose refusal naming the caller's off-campus IP address. The one fully public machine-readable contract is the SAML 2.0 metadata of the Shibboleth IdP at idp.ustc.edu.cn, which is why it is the centrepiece of this profile. This is a re-profile, and it moves in the opposite direction to the rest of this cohort. The June 2026 pass recorded two surfaces and no artifacts and concluded USTC had no documented API program; probing found a documented one that was simply never looked for. Nothing was removed for vendor misattribution because nothing vendor-attributed was ever here — no Figshare, Pure, Ex Libris, Dataverse or Canvas contract. The single vendor-product API found (GitLab at git.ustc.edu.cn) is recorded as a deployment with x-contract-operator: vendor and no specification saved. Not found, after probing: any OAI-PMH endpoint (lib.ustc.edu.cn/oai 404s, ir.lib.ustc.edu.cn does not resolve), any institutional repository under USTC's own domain, any open-data portal (data.ustc.edu.cn does not resolve), any llms.txt, and any /.well-known catalog other than the OIDC discovery document. USTC's own AI assistant is real and institution-operated — the Network Information Center runs it on DeepSeek — and its user agreement mentions API delivery, but no API documentation for it is published, so it is recorded as a pointer rather than a surface.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is University of Science and Technology of China's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://idp.ustc.edu.cn/idp/shibboleth→ HTTP 200https://id.ustc.edu.cn/cas/oidc/.well-known/openid-configuration→ HTTP 200https://id.ustc.edu.cn/cas/oidc/jwks→ HTTP 200https://id.ustc.edu.cn/doc/api/health→ HTTP 200https://id.ustc.edu.cn/doc/status-api/→ HTTP 200https://id.ustc.edu.cn/doc/developer/→ HTTP 200https://id.ustc.edu.cn/doc/notice/→ HTTP 200https://passport.ustc.edu.cn/serviceValidate→ HTTP 200https://passport.ustc.edu.cn/healthcheck→ HTTP 200https://id.ustc.edu.cn/doc/api/status/by-zjhm/P0529→ HTTP 401https://id.ustc.edu.cn/cas/oauth2.0/profile→ HTTP 401https://catalog.ustc.edu.cn/api/restricted→ HTTP 200https://catalog.ustc.edu.cn/api/teach/semester/list→ HTTP 401https://mirrors.ustc.edu.cn/status/→ HTTP 200https://opac.lib.ustc.edu.cn/→ HTTP 200https://chat.ustc.edu.cn/ustchat/policies/ustchat-terms-of-use.html→ HTTP 200https://git.ustc.edu.cn/→ HTTP 200https://scc.ustc.edu.cn/→ HTTP 200https://lib.ustc.edu.cn/oai?verb=Identify→ HTTP 404https://id.ustc.edu.cn/cas/oidc/register→ HTTP 404https://mirrors.ustc.edu.cn/mirrorz.json→ HTTP 404
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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from University of Science and Technology of China'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/ustc/"
title="University of Science and Technology of China on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/ustc.svg"
alt="University of Science and Technology of China Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/ustc/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/ustc/"
title="University of Science and Technology of China on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/ustc/card.svg"
alt="University of Science and Technology of China 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 University of Science and Technology of China
Each block below is one kind of artifact we hold for University of Science and Technology of China. 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 6
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.
USTC Unified Identity Authentication (id.ustc.edu.cn, formerly Passport SSO)
USTC's institution-operated authorization server, run by the Network Information Center and the hub every other campus system authenticates against. It speaks CAS 3.0, OAuth 2.0...
USTC Campus Enrollment Status Query API (在校状态查询接口)
A small, precise, institution-authored REST API that resolves a person's campus enrollment status code by global person identifier or identity number, singly or in batches of up...
USTC Shibboleth Identity Provider (跨校资源认证中心)
USTC's self-hosted Shibboleth IdP 5.2.2, publishing a 15KB SAML 2.0 EntityDescriptor for entityID https://idp.ustc.edu.cn/idp/shibboleth with a shibmd:Scope of ustc.edu.cn, SSO ...
USTC Course Catalog API (catalog.ustc.edu.cn)
The JSON API behind USTC's public course catalog application — semesters, the college tree, program trees, course search, course and lesson detail, exam lists, major lists and p...
USTC Open Source Software Mirror
The USTC Open Source Software Mirror, operated by the campus Linux User Group (LUG @ USTC), is one of the largest open source mirror services among universities in mainland Chin...
USTC Campus GitLab
A GitLab instance USTC runs on its own domain at git.ustc.edu.cn, with a second LUG-operated instance at git.lug.ustc.edu.cn. GitLab exposes a well-documented REST and GraphQL A...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Ustc Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Ustc Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Ustc Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Ustc Context
JSON-LDJSON Schema 1
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
USTC Campus Enrollment Status API schemas
JSON SCHEMAExamples 2
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Ustc Jwks Example
EXAMPLESecurity 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for University of Science and Technology of China — 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.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/ustc · machine-readable index on apis.io
This is an independent, third-party profile of University of Science and Technology of China, 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.