Ghent University
Ghent University (Universiteit Gent, UGent) is a public research university in Ghent, Belgium, founded in 1817 and ranked around #169 in the QS World University Rankings. Like almost every institution, it is a federation of buyers rather than an API producer, and its profile is written on that basis: it operates no central developer portal, no gateway and no institution-wide API programme, and most of what looks like a Ghent API on first inspection belongs to a supplier. The real programmable footprint is concentrated in one place - Ghent University Library. The Academic Bibliography at biblio.ugent.be is genuinely the university's own: a documented JSON/JSONP REST search API, fourteen export formats, a live OAI-PMH 2.0 endpoint identifying itself as the Ghent University Institutional Archive, an SRU 1.1 service over CQL with 78 documented indexes, unAPI discovery, RSS feeds and daily full-dataset dumps, all under the Open Database License. The library also authors and open-sources the software behind it, and three of those services carry first-party OpenAPI 3.1 contracts. Beyond the library the university runs its own SAML 2.0 identity provider and eight entities in the Belgian Belnet R&E Federation, and hosts the student-built Hydra Resto API on a university domain. Everything else is somebody else's: the library catalogue is now an Ex Libris Alma/Primo VE tenancy, and Dodona, which began at Ghent, has moved to its own domain and its own pricing. There is no DataCite membership. Ghent is a Crossref member in its own name.
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.
API Evangelist profiles Ghent University the way a machine reads it — 23 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 — Ghent University scores 42.6/100 (developing), with a separate agent-readiness read of 21/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.
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 Ghent University'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/ghent/"
title="Ghent University on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/ghent.svg"
alt="Ghent University Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/ghent/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/ghent/"
title="Ghent University on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/ghent/card.svg"
alt="Ghent University 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 Ghent University
Each block below is one kind of artifact we hold for Ghent University. 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 12
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.
Ghent University Academic Bibliography API
The Academic Bibliography (Biblio) is Ghent University's institutional publication and dataset registry, operated by Ghent University Library on the university's own host. It ex...
Ghent University Academic Bibliography OAI-PMH
OAI-PMH 2.0 harvesting endpoint for the Academic Bibliography. The live Identify response names the repository "Ghent University Institutional Archive", declares repositoryIdent...
Ghent University Academic Bibliography SRU
SRU 1.1 search/retrieve service over the Academic Bibliography, driven by Contextual Query Language. Seventy-eight indexes are documented with their supported relations and sort...
Hydra Resto API
Open JSON API for Ghent University's student restaurants - locations and opening hours, day menus, weekly ecological sandwiches, salad bowls, extra food and allergen information...
Ghent University Library People Service
An OpenAPI 3.1 contract authored and open-sourced by Ghent University Library for the people and organizations directory behind the Academic Bibliography. Sixteen operations cov...
Ghent University Library Projects Service
An OpenAPI 3.1 contract authored and open-sourced by Ghent University Library for the directory of research projects at Ghent University - add, get, delete and suggest operation...
Ghent University Library OAI Service
An OpenAPI 3.1 contract authored and open-sourced by Ghent University Library for the administrative side of the OAI-PMH server that fronts the Academic Bibliography - adding me...
Ghent University SAML 2.0 Identity Provider
Ghent University's own SAML 2.0 identity provider, operated by the university's ICT directorate. The signed metadata document is publicly readable and carries entityID https://i...
Ghent University Library catalogue (Ex Libris Alma/Primo VE tenancy)
lib.ugent.be redirects to libcatalog.ugent.be, an Ex Libris Primo VE discovery layer running under institution code 32RUG_INST and resolving through libugent.primo.exlibrisgroup...
Dodona
Dodona is the automated programming-practice platform that originated at Ghent University and is still used in its computer-science teaching; Ghent registered it as a service pr...
Crossref membership
Ghent University is a Crossref member in its own name - member id 9286, DOI prefix 10.21825, registered in Ghent, Belgium, with 28,489 DOIs deposited (960 current, 27,529 backfi...
ROR registration
Ghent University is registered in the Research Organization Registry as https://ror.org/00cv9y106, distinct from Ghent University Hospital (https://ror.org/00xmkp704) and HOGENT...
Scroll within the panel for all 12 ·
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.
Ghent 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.
Ghent 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.
Ghent Finops
FINOPSSemantic 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.
Ghent Context
JSON-LDJSON Schema 2
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.
Ghent Biblio Publication
JSON SCHEMAHydra Resto API payloads
JSON SCHEMAExamples 3
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.
Resources
Every other property we hold for Ghent University — 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 4
Pagination, idempotency, versioning, errors, and events
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/ghent · machine-readable index on apis.io
This is an independent, third-party profile of Ghent University, 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.