How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
King's College London website screenshot

King's College London

King's College London is a UK public research university and Russell Group member, founded in 1829, ranked #40 in the QS World University Rankings. Re-profiled on 2026-08-19 under the API Evangelist university pipeline, which settles WHO OPERATES a surface before crediting it to the institution. The June 2026 profile credited King's with eleven API entries and ten OpenAPI contracts; every one of them was api.figshare.com/v2 — a single Figshare document that the same pass attributed to twenty-five different universities — split by tag into eleven apparent surfaces. Those contracts, and the collections and agentic-access artifacts derived from them, have been removed. What is left is what King's actually operates. The genuine find is the e-Research AI Hub at ai.create.kcl.ac.uk: King's own OpenAI-compatible LLM inference platform for researchers, live, bearer-authenticated, metered and billed, running on King's own infrastructure — a real institution-operated API, and a rare one in this cohort. Alongside it sit four tenancies that are real institutional facts but somebody else's engineering: the King's Research Portal OAI-PMH endpoint (Elsevier Pure), the research data repository (Figshare), LibrarySearch (Ex Libris Primo) and the UK federation identity provider (OpenAthens). King's holds its own DataCite membership and prefix, and is registered in the UK Access Management Federation and eduGAIN. It publishes no OpenAPI, no developer portal, no open data portal, no llms.txt and no security.txt.

human only

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles King's College London the way a machine reads it — 11 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 — King's College London scores 36.8/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.

Behind a wall

Why this profile is thin

Verified institution-operated and live: https://ai.create.kcl.ac.uk/api/v1/models returns 401 application/json with the OpenAI error envelope ({"error":{"message":"Unauthorized — no bearer token provided","type":"invalid_request_error", "param":null,"code":"invalid_api_key"}}) from nginx/1.30.4, and a request bearing an unknown key returns a different message ("invalid API key"), which establishes the token is validated rather than merely required. King's own documentation at docs.er.kcl.ac.uk/CREATE/ai_hub/ describes it as "King's College London's AI inference platform for researchers", OpenAI- compatible, with chat completions, image generation, streaming, RAG, agent workflows and MCP integration, free starter tokens and project budgets thereafter. No contract is published for it: /openapi.json, /api/openapi.json, /v1/models and /.well-known/openapi all return the application's 404. Institution-operated but unreachable: cloud.er.kcl.ac.uk, the CREATE Cloud OpenStack API documented at docs.er.kcl.ac.uk/CREATE/cloud/openstack_api/, has no public DNS record on 1.1.1.1 or 8.8.8.8 — it is VPN-only, and its application-credential and root-CA flow is documented but not probeable. Institution-authored but internal: the KCL e-Research Authentication API (github.com/kcl-eresearch/auth_api) documents its own REST surface for SSH keys, OpenVPN certificates and MFA requests in a public README, with no public base URL; and kcl-eresearch/artemis is a King's-authored Perplexity-compatible research API server. Neither ships an OpenAPI. Verified live but tenant-operated: kclpure.kcl.ac.uk (CNAME kings.elsevierpure.com), kcl.figshare.com (CNAME figshare.com), librarysearch.kcl.ac.uk (CNAME kcl.primo.exlibrisgroup.com), keats.kcl.ac.uk (CNAME kcl-vle.bloom.ulcc.ac.uk) and the UK federation IdP whose SSO endpoints are on login.openathens.net. Confirmed absent: no DNS for data.kcl.ac.uk, developer.kcl.ac.uk, courses.kcl.ac.uk, sis.kcl.ac.uk, idp.kcl.ac.uk or sso.kcl.ac.uk; api.kcl.ac.uk resolves to 137.73.130.161 but accepts no TCP connection on 80 or 443 across three attempts at 30s, 40s and 60s; www.kcl.ac.uk/llms.txt and /.well-known/security.txt both 404. The development identity provider https://kclidpdev.kcl.ac.uk/idp/shibboleth is registered in the UK federation but carries the hide-from-discovery entity category and is treated as a placeholder, not a surface.

An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is King's College London'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://ai.create.kcl.ac.uk/api/v1/modelsHTTP 401
  • https://ai.create.kcl.ac.uk/HTTP 200
  • https://ai.create.kcl.ac.uk/docsHTTP 200
  • https://ai.create.kcl.ac.uk/openapi.jsonHTTP 404
  • https://ai.create.kcl.ac.uk/api/openapi.jsonHTTP 404
  • https://docs.er.kcl.ac.uk/CREATE/ai_hub/HTTP 200
  • https://docs.er.kcl.ac.uk/CREATE/cloud/openstack_api/HTTP 200
  • https://docs.er.kcl.ac.uk/sitemap.xmlHTTP 200
  • https://kclpure.kcl.ac.uk/ws/oai?verb=IdentifyHTTP 200
  • https://kclpure.kcl.ac.uk/ws/oai?verb=ListMetadataFormatsHTTP 200
  • https://kclpure.kcl.ac.uk/ws/oai?verb=ListSetsHTTP 200
  • https://kclpure.kcl.ac.uk/ws/oai?verb=ListRecords&metadataPrefix=oai_dc&set=persons:allHTTP 200
  • http://metadata.ukfederation.org.uk/ukfederation-metadata.xmlHTTP 200
  • https://met.refeds.org/met/entity/https%3A%2F%2Fkclidp.kcl.ac.uk%2Fidp%2Fshibboleth/HTTP 200
  • https://api.datacite.org/providers/hcbrHTTP 200
  • https://api.datacite.org/dois?provider-id=hcbrHTTP 200
  • https://api.crossref.org/members?query=king%27s+college+londonHTTP 200
  • https://librarysearch.kcl.ac.uk/HTTP 200
  • https://keats.kcl.ac.uk/webservice/rest/server.phpHTTP 200
  • https://keats.kcl.ac.uk/mod/lti/auth.phpHTTP 200
  • https://keats.kcl.ac.uk/.well-known/openid-configurationHTTP 404
  • https://kcl.figshare.com/HTTP 202
  • https://portal.er.kcl.ac.uk/HTTP 200
  • https://github.com/kcl-eresearchHTTP 200
  • https://raw.githubusercontent.com/kcl-eresearch/auth_api/main/README.mdHTTP 200
  • https://www.kcl.ac.uk/llms.txtHTTP 404
  • https://www.kcl.ac.uk/.well-known/security.txtHTTP 404
  • https://api.kcl.ac.uk/HTTP 0
  • https://cloud.er.kcl.ac.uk/HTTP 0

If this is out of date, tell us on the provider's repo and we will re-run the profile.

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 Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
King's College London Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from King's College London'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/kings-college-london/"
   title="King's College London on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/kings-college-london.svg"
       alt="King's College London Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile King's College London

Each block below is one kind of artifact we hold for King's College London. 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.

King's e-Research AI Hub API

An OpenAI-compatible LLM inference API operated by King's e-Research for researchers, students and staff. Per King's documentation it serves chat completions against a curated s...

King's Research Portal (Pure) OAI-PMH

The standards-based harvesting interface for the King's Research Portal, the front end of Pure — how King's research outputs reach OpenAIRE, CORE, BASE and the rest of the aggre...

King's College London Research Data Repository (Figshare tenancy)

King's research data repository, operated for King's by Figshare. The data, the DOIs, the DataCite membership and the curation decisions are King's; the REST API, the OAI-PMH en...

King's UK Access Management Federation / eduGAIN Identity Provider

King's federated identity, and the surface class this pipeline flags as most often missed. The entity is registered in the UK Access Management Federation (uk001282, registered ...

King's LibrarySearch (Ex Libris Primo)

Library discovery for King's, on Ex Libris Primo. GET / returns 200 and redirects to /discovery/search?vid=44KCL_INST:44KCL_INST. Recorded as a tenancy because the catalog and t...

KEATS Virtual Learning Environment (Moodle) web services

King's VLE exposes the standard Moodle machine interfaces on a King's hostname: /webservice/rest/server.php answers 200 with an XML `invalidtoken` fault, /lib/ajax/service.php a...

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.

FinOps 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.

Kings College London Authentication

http/openIdConnect/saml/none · 5 schemes

SECURITY

Kings College London Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for King's College London — 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

Documentation 1

Reference material describing how the API behaves

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

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

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/kings-college-london · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of King's College London, 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.