National University of Singapore
The National University of Singapore is Singapore's flagship public research university, ranked eighth in the QS World University Rankings 2025, and it is a near-perfect illustration of why a university is a federation of buyers rather than a producer. NUS operates exactly one substantial machine-readable API surface of its own: the federated identity service at vafs.nus.edu.sg, which publishes a live OpenID Connect discovery document, a JWKS, and signed SAML 2.0 metadata for entityID https://vafs.nus.edu.sg/adfs/services/trust, and which registers NUS as an identity provider in the Singapore Access Federation. Everything else that looks like an NUS API belongs to a platform NUS rents — ScholarBank@NUS is Atmire's DSpace, the learning management system is Instructure's Canvas, the blogs are CampusPress, the library guides are Springshare. NUS has an API gateway hostname at api.nus.edu.sg on a certificate issued to the university, and it returns HTTP 500 on every path. The campus shuttle bus API at nnextbus.nus.edu.sg is genuinely NUS's and genuinely live, but sits behind HTTP Basic credentials the university does not issue publicly. Most strikingly, NUS's own course vocabulary — modules, modular credits, prerequisite trees — has no public machine-readable expression from the university at all; the only OpenAPI describing NUS course data is published by NUSMods, a student organisation, from a non-NUS domain. There is no NUS developer portal, no institution-wide GitHub organisation, no public open-data portal, no llms.txt, and no self-service registration path to any NUS API.
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 National University of Singapore the way a machine reads it — 24 machine-readable artifacts across 10 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 — National University of Singapore scores 31.3/100 (thin), with a separate agent-readiness read of 29/100 (agent ready). 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
NUS operates real institution-owned API surfaces, but none of them can be consumed by an unaffiliated caller. The federated identity service at vafs.nus.edu.sg publishes anonymously readable OIDC and SAML metadata, yet a client_id exists only if NUS Information Technology creates one and there is no public or dynamic registration endpoint. The NUS shuttle bus API at nnextbus.nus.edu.sg answers 401 with an HTTP Basic challenge and NUS issues no public credentials for it. The api.nus.edu.sg gateway is live on an NUS-issued certificate and returns HTTP 500 on every probed path, publishing no route at all. Two secondary limits apply and are recorded rather than treated as findings about NUS - the main nus.edu.sg web estate sits behind an Imperva bot challenge that returns 200 with a JavaScript shell for every deep path, so terms-of-use, IT and library pages could not be read and are not claimed as pointers; and nusit.nus.edu.sg answered 403 to the HPC documentation path. Everything else that is publicly readable belongs to a platform NUS rents. This is a correct thin profile, not a failed probe - 40+ URLs were fetched successfully across nine hosts.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is National University of Singapore'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://vafs.nus.edu.sg/adfs/.well-known/openid-configuration→ HTTP 200https://vafs.nus.edu.sg/FederationMetadata/2007-06/FederationMetadata.xml→ HTTP 200https://vafs.nus.edu.sg/adfs/discovery/keys→ HTTP 200https://nnextbus.nus.edu.sg/BusStops→ HTTP 401https://api.nus.edu.sg/→ HTTP 500https://api.nus.edu.sg/swagger.json→ HTTP 500https://scholarbank.nus.edu.sg/oai/request?verb=Identify→ HTTP 200https://scholarbank.nus.edu.sg/server/api→ HTTP 200https://canvas.nus.edu.sg/api/v1/accounts→ HTTP 401https://canvas.nus.edu.sg/api/lti/security/jwks→ HTTP 200https://blog.nus.edu.sg/wp-json/→ HTTP 200https://vafs.nus.edu.sg/scim/v2/ServiceProviderConfig→ HTTP 404https://nus.edu.sg/llms.txt→ HTTP 200https://www.nus.edu.sg/robots.txt→ HTTP 200https://nus.edu.sg/about-nus/terms-of-use→ HTTP 200https://nusit.nus.edu.sg/hpc/→ HTTP 403https://luminus.nus.edu.sg/→ 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. 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 National University of Singapore'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/nus/"
title="National University of Singapore on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/nus.svg"
alt="National University of Singapore Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/nus/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/nus/"
title="National University of Singapore on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/nus/card.svg"
alt="National University of Singapore 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 National University of Singapore
Each block below is one kind of artifact we hold for National University of Singapore. 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 10
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.
NUS NextBus (Internal Shuttle Bus) API
The API behind the NUS internal shuttle bus service — bus stops, services and arrival times across the Kent Ridge and Bukit Timah campuses. Institution-operated and live, but ga...
ScholarBank@NUS DSpace REST API
The HAL-style REST API of ScholarBank@NUS, the university's institutional repository — communities, collections, items, bitstreams and a 485-field metadata registry covering the...
ScholarBank@NUS OAI-PMH Interface
OAI-PMH 2.0 metadata harvesting endpoint for ScholarBank@NUS, advertising twelve metadata formats including oai_dc, qdc, mods, mets, marc, etdms and uketd_dc, with an earliest d...
NUS Canvas LMS API
The learning management system for NUS courses, running on Instructure's Canvas as a vanity tenant. The REST API is live and returns a structured 401 to unauthenticated callers;...
Blog.nus WordPress REST API
The NUS academic, educational, research and administrative blogging platform exposes a full WordPress REST API with eleven namespaces and 190 routes, anonymously readable. Runs ...
NUSMods API (student-operated, not endorsed)
The only public machine-readable description of NUS course data that exists — module lists, module information, prerequisite trees, timetables and venue occupancy, published as ...
NUS entry in the Singapore Access Federation
NUS is one of fourteen identity providers registered in the Singapore Access Federation, which SingAREN operates and which interfederates with eduGAIN. The entityID NUS is regis...
National University of Singapore Authorization API
OAuth 2.0 / OpenID Connect authorization and token issuance.
National University of Singapore Discovery API
Machine-readable metadata describing the identity service and its signing keys.
National University of Singapore Session API
End-user claims and session termination.
Scroll within the panel for all 10 ·
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.
Nus 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.
Nus 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.
Nus 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.
Nus Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 2
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.
NUS JSON Web Key Set
JSON SCHEMANUS OpenID Provider Metadata
JSON SCHEMAExamples 3
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.
Nus 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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for National University of Singapore — 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.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
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 5
The organization behind the API
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/nus · machine-readable index on apis.io
This is an independent, third-party profile of National University of Singapore, 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.