University of Sydney
The University of Sydney is Australia's first university, founded in 1850, a Group of Eight member and ranked in the QS world top 40. Its programmable footprint is small, and most of what looks like a University of Sydney API is a vendor's contract running under the university's name. Re-profiled on 2026-08-19 with operator attribution settled first, the institution operates no public developer portal, publishes no OpenAPI, and offers no self-service developer credential. The only openly machine-readable artifact served under a University of Sydney hostname is SAML 2.0 federation metadata at federation.sydney.edu.au — and even that is a tenant surface, because the host CNAMEs to the Australian Access Federation's hosted Rapid IdP. The entity, scope and signing key are the university's; the infrastructure is AAF's. Beyond that it operates the Sydney eScholarship institutional repository (a DataCite repository client with 2,146 DOIs, whose documented OAI-PMH endpoint is currently behind Cloudflare bot management), the CUSP course and unit-of-study catalog as HTML only, the myUni student portal on session-gated internal JSON endpoints, and a MuleSoft Anypoint API gateway at api.sydney.edu.au whose production load balancer resolves in DNS but refuses connections from the public internet. Its library discovery, learning management and identity brokering all run on vendor platforms — Ex Libris Primo/Alma, Instructure Canvas and Okta — where the data is the university's and the contract is not. An earlier profile of this cohort risked attributing a Figshare repository here; sydney.figshare.com was checked and is not the University of Sydney's, and no Figshare contract has been saved under this slug.
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 Sydney the way a machine reads it — 14 machine-readable artifacts across 7 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 — University of Sydney scores 30.7/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
The University of Sydney operates real institutional surfaces but publishes none of them for third-party consumption. The one machine-readable artifact it serves openly is SAML 2.0 identity-provider metadata, which is consumable only by federation members. Its institutional repository documents an OAI-PMH interface on its own host but answers 403 to every automated client behind Cloudflare bot management. Its course catalog is HTML only. Its student portal APIs require a session. Its MuleSoft Anypoint production gateway resolves in DNS but filters TCP 443 from the public internet. Its library, LMS and sign-in run on Ex Libris, Instructure and Okta tenants whose contracts belong to those vendors. No OpenAPI, no developer portal, no credential self-service, no llms.txt and no security.txt were found — sydney.edu.au serves a soft-404 (HTTP 200 redirecting to /errors/404.html) for both well-known paths, so neither is credited. This is a correct thin profile, not a failed harvest.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is University of Sydney'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://federation.sydney.edu.au/idp/shibboleth→ HTTP 200https://md.aaf.edu.au/aaf-metadata.xml→ HTTP 200https://mds.edugain.org/edugain-v2.xml→ HTTP 200https://ses.library.usyd.edu.au/oai/request?verb=Identify→ HTTP 403https://ses.library.usyd.edu.au/robots.txt→ HTTP 200https://api.datacite.org/clients/ardcx.usyd→ HTTP 200https://api.crossref.org/members/12184→ HTTP 200https://cusp.sydney.edu.au/→ HTTP 200https://myuni.sydney.edu.au/→ HTTP 200https://api.sydney.edu.au/→ HTTP 0https://www.sydney.edu.au/llms.txt→ HTTP 200https://www.sydney.edu.au/.well-known/security.txt→ HTTP 200https://www.sydney.edu.au/s/search.json?collection=Usyd&query=library→ HTTP 502https://sydney.figshare.com/→ HTTP 202https://data.sydney.edu.au/→ HTTP 0https://developer.sydney.edu.au/→ 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 University of Sydney'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/university-of-sydney/"
title="University of Sydney on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-sydney.svg"
alt="University of Sydney Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/university-of-sydney/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/university-of-sydney/"
title="University of Sydney on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-sydney/card.svg"
alt="University of Sydney 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 Sydney
Each block below is one kind of artifact we hold for University of Sydney. 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 7
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.
Shibboleth Identity Provider (SAML 2.0 metadata)
The University of Sydney's federation entity serves signed SAML 2.0 metadata from federation.sydney.edu.au: entityID https://federation.sydney.edu.au/idp/shibboleth, an IDPSSODe...
Sydney eScholarship Repository (institutional repository, OAI-PMH)
Sydney eScholarship is the university's own institutional repository, running on the university-owned usyd.edu.au domain (usyd.edu.au redirects to www.sydney.edu.au). It is a re...
CUSP — Course & Unit of Study Portal
CUSP is the University of Sydney's own course and unit-of-study catalog, served from cusp.sydney.edu.au behind Cloudflare and cross-linked from the sydney.edu.au course and unit...
myUni Student Portal (session-gated internal APIs)
The myUni student portal runs on the university's own domain, served through CloudFront, and is backed by internal JSON endpoints consumed by the authenticated student single-pa...
api.sydney.edu.au — MuleSoft Anypoint gateway (not publicly reachable)
api.sydney.edu.au resolves in DNS to usyd-lb-p.lb.anypointdns.net — a MuleSoft Anypoint Platform dedicated load balancer named for the University of Sydney production environmen...
Library Discovery — Ex Libris Primo VE / Alma (tenant)
The University of Sydney Library runs on the Ex Libris Alma library services platform with the Primo VE discovery layer, on the institution-specific tenant sydney.primo.exlibris...
Canvas LMS (tenant)
canvas.sydney.edu.au is a vanity hostname on the university's own domain that CNAMEs to sydney-vanity.instructure.com, and it redirects unauthenticated visitors into the univers...
Scroll within the panel for all 7 ·
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.
Rate 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.
University Of Sydney 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.
Semantic Vocabularies 2
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.
Security 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.
Resources
Every other property we hold for University of Sydney — 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
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 4
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/university-of-sydney · machine-readable index on apis.io
This is an independent, third-party profile of University of Sydney, 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.