Wuhan University
Wuhan University (武汉大学, WHU), founded in 1893 in Wuhan, Hubei, is a comprehensive public research university under China's Ministry of Education, a Double First-Class and former Project 985 institution, and is strongest in surveying, remote sensing, geoinformatics and GNSS. It operates no public developer portal, no open data portal and no documented public API: api., data., open. and developer. under whu.edu.cn do not resolve, /.well-known/apis.json, llms.txt, security.txt, robots.txt and sitemap.xml all return 404 on both the Chinese and English sites, and no OpenAPI, AsyncAPI or GraphQL contract exists anywhere in this profile. What it does operate, on its own CERNET address space, is an identity estate and a bulk research-data archive. Wuhan University runs a Shibboleth SAML 2.0 identity provider registered in CARSI, China's national research-and-education federation and a production eduGAIN member, and a campus CAS single-sign-on server that publishes a live OpenID Connect discovery document — the only conforming, self-describing, machine-readable contract WHU serves to the anonymous public, and it is the SSO product's shape rather than WHU engineering. It also operates one of the IGS Global Data Centers: the International GNSS Service's own data-access page names Wuhan University and links ftp://igs.gnsswhu.cn/, an anonymously listable archive of GPS, BDS, MGEX, high-rate and IERS products. Library discovery is an Ex Libris Aleph tenancy on a WHU host, and the registrar system is behind campus SSO. The institution's only evidenced education-regime conformance is SAML and Shibboleth; it is not a DataCite or Crossref depositing member, and no institution-operated OAI-PMH endpoint was found.
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 Wuhan University the way a machine reads it — 15 machine-readable artifacts across 8 APIs, 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 — Wuhan University scores 27.5/100 (thin), with a separate agent-readiness read of 5/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
Wuhan University publishes no public API, no developer portal and no contract of any kind, and that is the honest result rather than a wall we hit. api., data., open., developer., dspace., repository. and library. under whu.edu.cn return no DNS answer; /.well-known/apis.json, /.well-known/security.txt, /llms.txt, /robots.txt and /sitemap.xml are 404 on both www.whu.edu.cn and en.whu.edu.cn; and no OpenAPI, AsyncAPI, GraphQL SDL or Postman collection was located anywhere, so none has been saved and none has been derived. Four institution-operated surfaces WERE confirmed live, all on CERNET address space allocated to the Wuhan region or attributed by a standards body, and all are recorded above: the Shibboleth SAML 2.0 identity provider at idp.whu.edu.cn, registered in CARSI since 2024-12-10; the campus CAS/OIDC/SAML single-sign-on server at cas.whu.edu.cn, whose OpenID Connect discovery document is the only conforming machine-readable contract WHU serves the public; the IGS Global Data Center at ftp://igs.gnsswhu.cn/pub/, which the International GNSS Service's own data-access page attributes to Wuhan University; and the journal platform at ch.whu.edu.cn. None of the four publishes an API specification. The IdP's self-published metadata is Shibboleth's shipped template, expired in 2019, and namespace-ill-formed (undeclared md: prefix at lines 131-133, so namespace-aware parsers fail with "unbound prefix") — the service conforms, the document describing it does not. Library discovery is an Ex Libris Aleph tenancy and is recorded as a tenant relationship, not as a WHU contract. The registrar system jwgl.whu.edu.cn is real and institution-operated but sits behind campus SSO. One host, ir.whu.edu.cn, returns 403 from an openresty edge on every path and every user-agent tried, so it is unreadable from outside China and is deliberately NOT characterized here — a 403 with no body is not evidence of an institutional repository. Language was not the barrier: the Chinese-language estate was searched alongside the English one, and the only English-only gap found is the reverse — the CAS protocol errors are emitted in Chinese only.
This is an honest zero, not a gap in our research. Wuhan University 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://en.whu.edu.cn/→ HTTP 200https://www.whu.edu.cn/→ HTTP 200https://en.whu.edu.cn/.well-known/apis.json→ HTTP 404https://en.whu.edu.cn/llms.txt→ HTTP 404https://www.whu.edu.cn/sitemap.xml→ HTTP 404https://idp.whu.edu.cn/idp/shibboleth→ HTTP 200https://idp.whu.edu.cn/idp/profile/SAML2/Redirect/SSO→ HTTP 400https://cas.whu.edu.cn/authserver/oidc/.well-known/openid-configuration→ HTTP 200https://cas.whu.edu.cn/authserver/idp/metadata→ HTTP 200https://cas.whu.edu.cn/authserver/serviceValidate→ HTTP 200https://www.carsi.edu.cn/IdPlist.html→ HTTP 200https://igs.org/data-access/→ HTTP 200ftp://igs.gnsswhu.cn/pub/→ HTTP 226https://opac.lib.whu.edu.cn/→ HTTP 200https://jwgl.whu.edu.cn/→ HTTP 200https://ch.whu.edu.cn/oai?verb=Identify→ HTTP 200https://ir.whu.edu.cn/→ HTTP 403https://api.datacite.org/clients?query=Wuhan%20University→ HTTP 200https://api.ror.org/v2/organizations/033vjfk17→ 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. 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 Wuhan University'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/wuhan/"
title="Wuhan University on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/wuhan.svg"
alt="Wuhan University Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/wuhan/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/wuhan/"
title="Wuhan University on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/wuhan/card.svg"
alt="Wuhan University 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 Wuhan University
Each block below is one kind of artifact we hold for Wuhan University. 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 8
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.
Wuhan University Shibboleth Identity Provider (SAML 2.0)
WHU's federated login, published as a SAML 2.0 EntityDescriptor at https://idp.whu.edu.cn/idp/shibboleth (HTTP 200, application/xml, 14,864 bytes). Declares HTTP-Redirect, HTTP-...
Wuhan University Campus Single Sign-On (CAS / OpenID Connect / SAML)
The campus authentication server at cas.whu.edu.cn/authserver, which every institutional application redirects into, running the Wisedu CAS distribution. It publishes an OpenID ...
IGS Data Center at Wuhan University (GNSS archive)
One of the International GNSS Service's Global Data Centers, operated by Wuhan University's GNSS Research Center. The archive is anonymously listable over FTP at ftp://igs.gnssw...
CARSI membership (CERNET Authentication and Resource Sharing Infrastructure)
Wuhan University is a registered identity provider in CARSI, China's national research-and-education identity federation, operated from Peking University and a production eduGAI...
ROR registry entry (Research Organization Registry)
Wuhan University is registered in ROR as https://ror.org/033vjfk17 (active, established 1893), cross-walked to GRID grid.49470.3e, ISNI 0000 0001 2331 6153, Wikidata Q1108197 an...
Wuhan University Library catalog (Ex Libris Aleph tenant)
The library's online public access catalog at opac.lib.whu.edu.cn, running Ex Libris Aleph — the root document is Aleph's own session bootstrap ("Aleph main menu", redirecting t...
Wuhan University academic affairs / registrar system (SSO-gated)
The institutional teaching-administration and course-registration system. jwgl.whu.edu.cn is live and redirects unauthenticated callers to https://cas.whu.edu.cn/authserver/logi...
Geomatics and Information Science of Wuhan University (journal platform)
WHU's own journal publishing platform at ch.whu.edu.cn (115.156.123.29, WHR-CERNET), hosting 武汉大学学报·信息科学版 / Geomatics and Information Science of Wuhan University. Live and insti...
Scroll within the panel for all 8 ·
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.
Wuhan 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.
Wuhan 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.
Wuhan 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.
Wuhan Context
JSON-LDSecurity 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 Wuhan University — 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.
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 2
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 1
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 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/wuhan · machine-readable index on apis.io
This is an independent, third-party profile of Wuhan University, 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.