Queensland University of Technology
Queensland University of Technology (QUT) is a public research university in Brisbane, Australia, serving around 50,000 students with an applied emphasis in teaching and research. It is not an API producer and it publishes no developer portal, no API keys and no OpenAPI of its own — but it is one of the few institutions in this cohort whose machine-readable surfaces are genuinely its own engineering rather than a vendor's contract running under its name. Three surfaces were verified live on QUT-owned infrastructure inside APNIC allocation QUT-AU (AS7575), with no CNAME to a managed platform: the QUT ePrints OAI-PMH 2.0 repository interface at eprints.qut.edu.au, fully public and advertising oai_dc, oai_bibl, oai_openaire and uketd_dc; a self-hosted Shibboleth SAML 2.0 identity provider at idp.qut.edu.au registered in the Australian Access Federation and asserting the qut.edu.au scope; and a Keycloak OpenID Connect authorization server at esoe.qut.edu.au publishing a complete discovery document, JWKS, RFC 8414 metadata, dynamic client registration, PAR, CIBA and certificate-bound tokens, brokering interactive login to Microsoft Entra ID. QUT eResearch additionally publishes a public agent plugin marketplace carrying an MCP server definition, which is rare for a university — though the documentation host it targets, docs.eres.qut.edu.au, resolves publicly to an RFC 1918 private address and is unreachable from outside QUT. Everything else is bought: library discovery is an Ex Libris Primo VE tenancy, the LMS is Instructure Canvas, research data is contributed to ARDC's national registry, and identity is registered in DataCite, Crossref and ROR. Those relationships are recorded here; their contracts are not, because they are not QUT's. There is no open data portal, no course or timetable API, and no public route to a credential for the one authorization server QUT does run.
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 Queensland University of Technology the way a machine reads it — 24 machine-readable artifacts across 3 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 — Queensland University of Technology scores 35.3/100 (thin), with a separate agent-readiness read of 37/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.
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 Queensland University of Technology'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/qut/"
title="Queensland University of Technology on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/qut.svg"
alt="Queensland University of Technology Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/qut/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/qut/"
title="Queensland University of Technology on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/qut/card.svg"
alt="Queensland University of Technology 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 Queensland University of Technology
Each block below is one kind of artifact we hold for Queensland University of Technology. 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 12
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.
QUT ePrints OAI-PMH 2.0
Public, unauthenticated OAI-PMH 2.0 metadata harvesting interface for QUT's institutional research repository. All six verbs served. Advertises oai_dc, oai_bibl, oai_openaire an...
QUT ESOE OpenID Connect Provider
QUT's enterprise single sign-on authorization server, a Keycloak deployment on QUT's own address space. Publishes OpenID Connect Discovery 1.0 metadata, an RFC 8414 authorizatio...
QUT Shibboleth Identity Provider
QUT's self-hosted Shibboleth SAML 2.0 identity provider. Publishes per-entity metadata that dereferences from its own entityID, asserts shibmd:Scope qut.edu.au, and is registere...
QUT ePrints REST Interface
The GNU EPrints REST dataset interface. The index is open and the payload is closed — /rest/, /rest/eprint/ and /rest/subject/ return 200 without credentials, while every indivi...
QUT eResearch Agent Plugin Marketplace
A public agent plugin marketplace published by QUT eResearch, carrying one MCP server definition that wraps the QUT eResearch documentation site. Institution-authored and a rare...
QUT Library Discovery (Ex Libris Primo VE tenant)
QUT's library discovery layer runs on Ex Libris Primo VE / Alma under view id 61QUT_INST:QUT. The collection and the configuration are QUT's; the platform and any API contract a...
QUT Canvas LMS (Instructure tenant)
QUT's learning management system, an Instructure Canvas tenancy on a QUT hostname, front-ended by Microsoft Entra ID sign-in. Canvas is an LTI 1.3 platform and exposes Instructu...
QUT collection in ARDC Research Data Australia
QUT contributes a named group to the Australian Research Data Commons national registry. A live query for group "Queensland University of Technology" returns 926 registry object...
DataCite DOI and RAiD registration
QUT registers persistent identifiers with DataCite through the ARDC consortium. Two clients are evidenced: ARDCX.QUT1, a repository client registered 2020 holding 535 DOIs, and ...
Crossref membership
QUT is a Crossref member, id 3230, primary-name "Queensland University of Technology", verified live against Crossref's member API. Recorded as a membership; Crossref's API is n...
ROR registration
QUT's Research Organization Registry identifier is https://ror.org/03pnv4752. The canonical machine-readable identifier for the institution itself, used across DataCite, Crossre...
Australian Access Federation membership
QUT is a member of the Australian Access Federation, which is interfederated with eduGAIN. Five entity descriptors naming QUT appear in the production aggregate; three are QUT-o...
Scroll within the panel for all 12 ·
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.
Qut 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.
Qut 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.
Qut 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.
Qut 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 3
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.
QUT ESOE OpenID Provider Metadata
JSON SCHEMAQUT ePrints OAI-PMH Identify Response
JSON SCHEMAQUT ePrints OAI-PMH Metadata Format
JSON SCHEMAExamples 1
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.
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.
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 Queensland University of Technology — 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 1
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
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
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/qut · machine-readable index on apis.io
This is an independent, third-party profile of Queensland University of Technology, 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.