University of Leeds
The University of Leeds is a public research university in Leeds, United Kingdom, a member of the Russell Group, with more than 34,000 students and over 7,000 staff. Its programmable footprint is small, real, and almost entirely the work of one department: University of Leeds Libraries. Four surfaces were verified live on 2026-08-30 and every one of them runs on a leeds.ac.uk host under the institution's own operation — two self-hosted EPrints repositories exposing OAI-PMH 2.0 (Research Data Leeds, and the Digital Library of digitised Special Collections), a IIIF Image API level 0 service behind the library floor plans, and Spacefinder, an unauthenticated JSON dataset of 68 campus study spaces with geolocation, opening hours, facilities and accessibility. All four are anonymous, keyless and read-only. There is no central developer portal, no API gateway, no registration, no status page, no changelog and no published OpenAPI — the four OpenAPI documents in this repository were derived by API Evangelist from probed responses, not published by Leeds. Library discovery is an Ex Libris Alma/Primo tenancy and the university's publications repository is White Rose Research Online, a three-university consortium platform; both are recorded here as tenant relationships, not as Leeds contracts. Advanced Research Computing (ARC) operates the Aire HPC service for researchers, but its allocation and service surfaces are behind institutional login.
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 Leeds the way a machine reads it — 16 machine-readable artifacts across 4 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 Leeds scores 34.0/100 (thin), with a separate agent-readiness read of 24/100 (agent aware). 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.
Put this on your own site. The badge is drawn live from University of Leeds'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-leeds/"
title="University of Leeds on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-leeds.svg"
alt="University of Leeds Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/university-of-leeds/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/university-of-leeds/"
title="University of Leeds on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-leeds/card.svg"
alt="University of Leeds 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 Leeds
Each block below is one kind of artifact we hold for University of Leeds. 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 6
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.
Research Data Leeds Repository (OAI-PMH)
The University of Leeds institutional research data repository, running EPrints 3 on the university's own infrastructure, with a live unauthenticated OAI-PMH 2.0 interface. Veri...
Leeds Digital Library (OAI-PMH and OpenSearch)
A second, separate institution-run EPrints deployment holding digitised Special Collections — Bronte, incunabula, the Liddle Collection, cookery, history of science, the Leeds P...
Spacefinder Campus Space Data
The data layer behind the University of Leeds Libraries wayfinding application, published as two unauthenticated static JSON documents. spaces.json returned 68 campus and librar...
Library Floor Plans IIIF Image API
A static IIIF Image API level 0 service on the institution's own host, serving high-resolution floor plans for the Brotherton, Edward Boyle, Health Sciences and Laidlaw librarie...
Library Search (Ex Libris Alma / Primo) — tenancy
RELATIONSHIP, NOT A CONTRACT. University of Leeds Libraries discovery and resource management run on the Ex Libris Alma library services platform with the Primo discovery layer....
White Rose Research Online (OAI-PMH) — consortium tenancy
RELATIONSHIP, NOT A CONTRACT. Leeds' scholarly publications repository is White Rose Research Online, a shared EPrints platform operated by the White Rose University Consortium ...
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 Leeds 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 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.
University Of Leeds 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.
University of Leeds API Rules
SPECTRALJSON Schema 1
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.
University of Leeds Spacefinder Space
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 University of Leeds — 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 4
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 2
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/university-of-leeds · machine-readable index on apis.io
This is an independent, third-party profile of University of Leeds, 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.