University of Freiburg
The University of Freiburg (Albert-Ludwigs-Universität Freiburg) is a public research university in Baden-Württemberg, Germany, founded in 1457, a member of the German U15 and ranked #212 in the QS World University Rankings 2025. Like most universities it operates no central developer portal, publishes no OpenAPI description of anything, and offers no API program, keys, plans or support channel for developers — but unlike most of the cohort a meaningful part of what it does run is genuinely its own rather than a vendor contract wearing its name. Its library (Universitätsbibliothek Freiburg) operates FreiDok plus, an institutional repository and university bibliography whose read-only JSON API and OAI-PMH 2.0 endpoint are open, anonymous and live (267,771 publications, 238,730 persons, 1,277 institutions and 10,612 projects as probed on 2026-09-01). The university also runs a FreiData research-data repository (an InvenioRDM deployment minting DataCite DOIs under its own prefix 10.60493), a self-hosted GitLab whose REST API answers anonymously for 56 public projects, a public status page with a JSON monitor feed, and its own Shibboleth/SAML Identity Provider published into the DFN-AAI national federation. Its library discovery catalog is live but IP-blocked to automated clients, and its campus-management and LMS systems (HISinOne, ILIAS) are human-facing only. Everything programmable here is read-only metadata infrastructure built for harvesting, not a product; there is nothing to sign up for and nothing to buy.
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 University of Freiburg the way a machine reads it — 21 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 of Freiburg scores 44.0/100 (developing), with a separate agent-readiness read of 22/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 University of Freiburg'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-freiburg/"
title="University of Freiburg on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-freiburg.svg"
alt="University of Freiburg Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/university-of-freiburg/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/university-of-freiburg/"
title="University of Freiburg on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-freiburg/card.svg"
alt="University of Freiburg 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 Freiburg
Each block below is one kind of artifact we hold for University of Freiburg. 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 9
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.
FreiDok plus JSON API
Read-only JSON API for FreiDok plus, the institutional repository and university bibliography built and operated by the Universitätsbibliothek Freiburg on the university's own h...
FreiDok plus OAI-PMH
OAI-PMH 2.0 metadata-harvesting endpoint for FreiDok plus, on the university's own host. Identify (probed 2026-09-01) reports repositoryName "FreiDok plus", repositoryIdentifier...
FreiData research-data repository REST API
REST API of FreiData, the university's research-data repository, deployed and operated on its own host at freidata.uni-freiburg.de. Anonymous read of records, files and IIIF man...
FreiData OAI-PMH
Second OAI-PMH 2.0 endpoint, on the FreiData research-data host, serving marcxml, oai_dc, dcat, marc21, datacite, oai_datacite, datacite4 and oai_datacite4. Identify returns the...
University of Freiburg GitLab REST API
Self-hosted GitLab operated by the university's computing centre. The v4 REST API answers anonymous requests for public resources — probed 2026-09-01, GET /api/v4/projects retur...
Uni-Freiburg Services status API
Public status page for central university services, with a JSON API — /api/status-page/ufr-services returns the monitor configuration and /api/status-page/heartbeat/ufr-services...
myLogin Shibboleth Identity Provider (SAML 2.0 metadata)
The university's own Shibboleth Identity Provider, myLogin, operated by the Universitätsrechenzentrum. Its SAML 2.0 metadata is published on the university's host (entityID http...
DataCite membership and repository registration
The University of Freiburg is a DataCite member (symbol QVVC, country DE, consortium organization under the TIB consortium, rorId https://ror.org/0245cg223) and operates the reg...
ROR organization identifier
The institution's Research Organization Registry identifier, https://ror.org/0245cg223, carrying its names in German and English and its website. Recorded as a registry membersh...
Scroll within the panel for all 9 ·
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 Freiburg 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.
JSON 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.
FreiDok plus JSON API response envelope
JSON SCHEMAExamples 4
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 3
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 University of Freiburg — 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.
Build 2
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 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/university-of-freiburg · machine-readable index on apis.io
This is an independent, third-party profile of University of Freiburg, 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.