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
University College Dublin website screenshot

University College Dublin

University College Dublin is Ireland's largest university, a public research institution in Belfield, Dublin. It operates no API programme: there is no developer portal, no API key issuance, no OAuth authorization server and no first-party OpenAPI anywhere on a ucd.ie host. What it does operate, verified live on 2026-08-30, is three real machine-readable surfaces — an OAI-PMH 2.0 harvesting endpoint for Research Repository UCD (17,167 records, fourteen metadata formats, plus an OpenAIRE CRIS base URL), a SAML 2.0 Shibboleth Identity Provider registered in Edugate/eduGAIN as https://sso.ucd.ie/idp/shibboleth with scope ucd.ie, and static Dublin Core collection data exports from the UCD Digital Library. Everything else is somebody else's engineering under UCD's name: the repository platform is DSpace-CRIS hosted by 4Science, library discovery is Serials Solutions, and the Dúchas API for the National Folklore Collection — the collection is UCD's, the platform is DCU's — was withdrawn by its operator and now returns HTTP 500 on every path. This profile was re-run under the university pipeline on 2026-08-30 and the previously catalogued Dúchas contracts were removed.

agent aware

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles University College Dublin the way a machine reads it — 12 machine-readable artifacts across 1 API, 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 College Dublin scores 42.5/100 (developing), with a separate agent-readiness read of 27/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.

No API surface

Why this profile is thin

University College Dublin operates no public API programme — no developer portal, no API key issuance, no OAuth authorization server, no first-party OpenAPI, no llms.txt and no security.txt on any ucd.ie host — and this profile now says so. Three institution-operated machine-readable surfaces do exist and are catalogued: the OAI-PMH 2.0 harvesting endpoint of Research Repository UCD (17,167 records, fourteen metadata formats, OpenAIRE CRIS profile), the SAML 2.0 Shibboleth IdP registered in Edugate/eduGAIN, and the UCD Digital Library's static Dublin Core data exports. None is a hosted API product, and the single OpenAPI in this repository is DERIVED by API Evangelist from live probes of the OAI-PMH endpoint, not published by UCD. What was catalogued here on 2026-06-03 was a different institution's contract: six per-tag OpenAPIs of the Dúchas API, whose info.contact is "Gaois / Dúchas" and whose operator is the Gaois research group at Dublin City University, all registered under UCD's slug with a fabricated baseURL of https://researchrepository.ucd.ie/oai/request — a path that returns 405 and does not serve those endpoints. Six times the apparent footprint, on a host that does not run the software, for an API its own documentation says "is no longer available" and which returns HTTP 500 on every path. Those six specifications, their twelve collections, and every schema, structure, example, ruleset, vocabulary, JSON-LD context and agentic-access file derived from them — 34 files — were removed on 2026-08-30. Two further June entries described the UCD Digital Library's IIIF Image, IIIF Presentation, Geospatial and unAPI endpoints; those were decommissioned with the old platform and now 404, and were replaced by the static data-export entry. The remaining machinery under UCD's name belongs to someone else and is labelled as such: the repository platform is DSpace-CRIS 7.6.1 hosted by 4Science (researchrepository.ucd.ie CNAMEs to ucd7.4science.cloud), and library discovery is Serials Solutions under a customer key.

This is an honest zero, not a gap in our research. University College Dublin 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://researchrepository.ucd.ie/server/oai/request?verb=IdentifyHTTP 200
  • https://researchrepository.ucd.ie/oai/request?verb=IdentifyHTTP 405
  • https://researchrepository.ucd.ie/server/apiHTTP 200
  • https://sso.ucd.ie/idp/shibbolethHTTP 200
  • https://technical.edugain.org/api.php?action=list_entities&format=jsonHTTP 200
  • https://digital.ucd.ie/data.htmlHTTP 200
  • https://digital.ucd.ie/help/HTTP 404
  • https://digital.ucd.ie/apiHTTP 404
  • https://www.duchas.ie/api/v0.5/apiHTTP 500
  • https://www.duchas.ie/api/v0.6/apiHTTP 500
  • https://docs.gaois.ie/en/data/duchas/v0.6/apiHTTP 200
  • https://api.ucd.ie/HTTP 0
  • https://data.ucd.ie/HTTP 0
  • https://www.ucd.ie/llms.txtHTTP 404
  • https://www.ucd.ie/.well-known/security.txtHTTP 404
  • https://researchrepository.ucd.ie/HTTP 405
  • https://digital.ucd.ie/assets/data/HTTP 403
  • https://www.linkedin.com/school/university-college-dublin/HTTP 999

Checked 2026-08-30. 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
University College Dublin Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from University College Dublin'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/ucd/"
   title="University College Dublin on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/ucd.svg"
       alt="University College Dublin 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 University College Dublin

Each block below is one kind of artifact we hold for University College Dublin. 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 Repository UCD — OAI-PMH 2.0

Keyless, anonymous OAI-PMH 2.0 metadata harvesting for UCD's open-access institutional repository. Verified live 2026-08-30: all six verbs return HTTP 200 with a well-formed env...

University College Dublin Identity Provider (Shibboleth / Edugate / eduGAIN)

UCD's SAML 2.0 Shibboleth Identity Provider, and the institution's only authentication surface it runs itself. It is machine-readable by definition — a federated IdP publishes S...

UCD Digital Library collection data exports

Static, keyless Dublin Core metadata exports for UCD Library's digital cultural-heritage collections — metadata as CSV and JSON, plus facets, subjects and a TimelineJS export, a...

Research Repository UCD — DSpace-CRIS REST API (4Science)

A live DSpace-CRIS 7.6.1 HAL REST API on UCD's branded repository host, advertising roughly ninety link relations including items, collections, communities, discover, authn, oid...

Dúchas API — National Folklore Collection (operated by DCU)

The National Folklore Collection (Cnuasach Bhéaloideas Éireann) is held at UCD; the Dúchas digitisation platform and its API are built and operated by DCU's Gaois research group...

UCD Library discovery (Serials Solutions / Clarivate)

UCD Library's discovery layer runs on Serials Solutions (Clarivate/ProQuest) under a customer key, not on a UCD host. It exposes a search interface for people, not a documented ...

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.

Ucd Plans Pricing

2 plans

PLANS

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.

Ucd Rate Limits

1 limits

RATE LIMITS

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.

Ucd Finops

FINOPS

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

Ucd Authentication

3 schemes

SECURITY

Ucd Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Every other property we hold for University College Dublin — 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

Design & Contract 3

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/ucd · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of University College Dublin, 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.