UCL
University College London (UCL) is a public research university in London, United Kingdom, and a member of the Russell Group. UCL is the clearest illustration in this cohort of why a university is a federation of buyers rather than a producer of APIs. Its flagship developer surface, UCL API (uclapi.com) — a student-built, ISD-backed, open-source, OAuth2-secured platform exposing room bookings, timetables, staff search, desktop and study-space availability and workspaces — was genuinely UCL's own engineering, and as of 2026-08-19 its entire estate is gone: uclapi.com, api.uclapi.com, docs.uclapi.com and status.uclapi.com all fail to complete a TCP connection on either port 80 or 443. The source repository remains public and unarchived (github.com/uclapi/uclapi, last pushed 2026-05-06); the OpenAPI repository was archived in 2021. What remains is almost entirely bought, not built. UCL Discovery, the open-access institutional repository, is the one institution-operated machine-readable surface left standing: EPrints on UCL's own domain with an OAI-PMH endpoint, currently behind a Cloudflare challenge. Everything else is a tenancy — the UCL Research Data Repository is Figshare (rdr.ucl.ac.uk CNAMEs to figshare.com, UCL's data addressed as institution=549 on Figshare's shared host), UCL Profiles is Symplectic Elements (profiles.ucl.ac.uk CNAMEs to ucl.discovery.symplectic.org), library discovery is Ex Libris Primo VE, site search is Funnelback, and even UCL's UK Access Management Federation identity provider — the one class of surface a university is supposed to operate by definition — resolves its SAML SSO to OpenAthens rather than to a UCL host. UCL owns the entityID, the ucl.ac.uk scope and the DataCite DOI prefix 10.5522; vendors run the services underneath them. No central developer portal, no open data portal and no publicly callable institution-operated API were found in this pass.
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 UCL the way a machine reads it — 10 machine-readable artifacts across 6 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 — UCL scores 26.6/100 (thin), with a separate agent-readiness read of 3/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.
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 UCL'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/ucl/"
title="UCL on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/ucl.svg"
alt="UCL Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/ucl/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/ucl/"
title="UCL on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/ucl/card.svg"
alt="UCL 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 UCL
Each block below is one kind of artifact we hold for UCL. 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.
UCL Discovery — OAI-PMH
UCL Discovery is UCL's open-access institutional repository of research outputs, running EPrints on UCL's own registrable domain, and it exposes an OAI-PMH 2.0 metadata-harvesti...
UCL Research Data Repository (Figshare tenancy)
The UCL Research Data Repository is UCL's institutional data repository, used to deposit, archive, publish and mint DOIs for research datasets. The data, the curation policy and...
UCL Profiles / IRIS (Symplectic Elements tenancy)
UCL Profiles is UCL's public research-information and researcher-profile directory, successor to the IRIS research portal (iris.ucl.ac.uk now redirects to it). It is a Symplecti...
UCL Library Discovery (Ex Libris Primo VE tenancy)
UCL Library Services runs its catalog and discovery layer on Ex Libris Primo VE, at an institution-specific view on Ex Libris' shared host: ucl.primo.exlibrisgroup.com with vid=...
UCL site search (Funnelback tenancy)
UCL's website and module-catalogue search runs on Funnelback (Squiz) at search2.ucl.ac.uk, on UCL's own registrable domain. It is the only surface in this profile that returns a...
UCL Identity Provider — UK Access Management Federation
UCL is a registered Identity Provider in the UK Access Management Federation (Jisc), and by extension in eduGAIN. Its SAML metadata is published in the federation's machine-read...
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.
Ucl 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.
Ucl 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.
Ucl Finops
FINOPSSecurity Posture 1
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 UCL — 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
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 4
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 8
Properties that don't map to a standard resource type
Scroll within the panel for all 8 ·
← All providers · Data indexed from github.com/api-evangelist/ucl · machine-readable index on apis.io
This is an independent, third-party profile of UCL, 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.