Queen's University at Kingston
Queen's University at Kingston is a public research university in Kingston, Ontario, Canada — a member of the U15 group of Canadian research universities, serving more than 25,000 students. Its machine-readable footprint is small, and stating it honestly matters more than inflating it: Queen's operates no public developer portal, no institution-run open-data API, and no published course, timetable, or registrar contract. api.queensu.ca, developer.queensu.ca and data.queensu.ca do not resolve. What Queen's genuinely operates and publishes on its own domain is federated identity — a Shibboleth Identity Provider serving SAML 2.0 metadata at login.queensu.ca — and an authored llms.txt directing AI agents to official sources. Its two research-data surfaces are real institutional facts but are tenant deployments, not Queen's engineering: QSpace, the institutional repository, now runs as DSpace 8.4 on Scholaris, the shared service of the Ontario Council of University Libraries, and the Queen's University Dataverse Collection lives inside Borealis, the national Dataverse operated by Scholars Portal. Both expose live REST and OAI-PMH interfaces, and both contracts belong to their platforms. An earlier profile of this repository carried 36 OpenAPI definitions titled after Queen's; every one of them was the Dataverse product's own contract, and they have been removed.
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 Queen's University at Kingston the way a machine reads it — 8 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 — Queen's University at Kingston scores 28.0/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
Queen's operates no public API of its own. Every callable surface reachable under its name is a tenant deployment on a shared Ontario or Canadian platform: QSpace runs as DSpace 8.4 on Scholaris (OCUL / Scholars Portal) after qspace.library.queensu.ca was redirected to queensu.scholaris.ca, and the Queen's University Dataverse Collection runs inside Borealis (Scholars Portal). Library discovery is Ex Libris Primo on the OCUL shared instance. Two surfaces ARE genuinely Queen's own and are recorded as such: the Shibboleth / SAML 2.0 IdP metadata at login.queensu.ca, and a substantive authored llms.txt at www.queensu.ca. The one previously catalogued open-data API, the student-built Qmulus project, is dead — api.qmulus.io and manage.qmulus.io return NXDOMAIN and its GitHub org has not been pushed to since January 2023 — so its landing page is kept only as a CourseCatalog pointer and it is no longer listed as an API. No institution-operated OpenAPI exists, and none was generated; 36 previously stored specs were the Dataverse product's contract and were removed with everything derived from them.
This is an honest zero, not a gap in our research. Queen's University at Kingston 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://login.queensu.ca/idp/shibboleth→ HTTP 200https://www.queensu.ca/llms.txt→ HTTP 200https://qspace.library.queensu.ca/server/api→ HTTP 301https://queensu.scholaris.ca/server/api→ HTTP 200https://queensu.scholaris.ca/server/oai/request?verb=Identify→ HTTP 200https://borealisdata.ca/api/dataverses/queens→ HTTP 200https://api.qmulus.io/v1→ HTTP 0https://manage.qmulus.io/token→ HTTP 0https://api.queensu.ca/→ HTTP 0https://developer.queensu.ca/→ HTTP 0https://data.queensu.ca/→ 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 Queen's University at Kingston'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/queens-university-at-kingston/"
title="Queen's University at Kingston on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/queens-university-at-kingston.svg"
alt="Queen's University at Kingston Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/queens-university-at-kingston/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/queens-university-at-kingston/"
title="Queen's University at Kingston on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/queens-university-at-kingston/card.svg"
alt="Queen's University at Kingston 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 Queen's University at Kingston
Each block below is one kind of artifact we hold for Queen's University at Kingston. 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 3
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.
Queen's University Shibboleth Identity Provider (SAML 2.0 Metadata)
Queen's runs its own Shibboleth Identity Provider and publishes SAML 2.0 IdP metadata as application/xml at a stable, unauthenticated URL on its own registrable domain. The Enti...
QSpace — Queen's University Institutional Repository (DSpace on Scholaris)
QSpace is Queen's open-access institutional repository for theses, dissertations and scholarship. The repository identity is unambiguously Queen's — the DSpace REST root reports...
Queen's University Dataverse Collection (Borealis)
The Queen's University Dataverse Collection is Queen's multidisciplinary research-data repository — collection alias "queens", id 41133, affiliation "Queen's University", holdin...
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.
Queens University At Kingston 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.
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 Queen's University at Kingston — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
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 3
Pricing, plans, and the legal terms of use
Company 2
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/queens-university-at-kingston · machine-readable index on apis.io
This is an independent, third-party profile of Queen's University at Kingston, 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.