Friedrich-Alexander-Universität Erlangen-Nürnberg
Friedrich-Alexander-Universität Erlangen-Nürnberg (FAU) is a public research university in Erlangen and Nuremberg, Bavaria, Germany, founded in 1743 and one of Germany's largest, with around 39,000 students across five faculties. FAU operates no central developer portal and publishes no OpenAPI definition of its own — but unlike most of this cohort its programmable footprint is real, and every surface in it runs on FAU's own infrastructure: every host recorded below resolves inside FAU's own 131.188.0.0/16 network, and not one of them CNAMEs to a vendor. The institution-operated, publicly readable surfaces verified live on 2026-08-30 are the OPEN FAU institutional repository on DSpace 7.4, which serves both a REST/HAL API and a fully functional OAI-PMH 2.0 harvesting endpoint with eight metadata crosswalks; a Matrix (Synapse 1.159.0) homeserver at matrix.fau.de, correctly delegated from .well-known/matrix/server and .well-known/matrix/client on fau.de, which makes FAU's chat service reachable by any standards-conformant Matrix client; the WordPress REST API behind the RRZE-operated FAU web platform, where the /wp-json index and search route are restricted but the wp/v2 content collections return real JSON on www.fau.de and a complete route index on ub.fau.de; and anonymous read access to the GitLab v4 REST API on FAU's self-hosted GitLab at gitlab.rrze.fau.de, which reports 132 public projects. Three further surfaces are live but gated: the FAU API gateway at api.fau.de, which fronts an authenticated API router behind SSO; the ClusterCockpit HPC job-monitoring REST API at monitoring.nhr.fau.de, run by NHR@FAU, the national high-performance computing centre FAU hosts; and the Clarivate Converis web service on cris.fau.de, which is FAU's research information system and returns HTTP 403 on its public web-service paths. FAU also operates a SAML 2.0 identity provider registered in the DFN-AAI federation, mints DOIs under its own DataCite prefix 10.25593, and maintains three active public GitHub organisations plus a self-hosted GitLab. No vendor contract is saved in this repository under FAU's name: where the software beneath a surface is someone else's product, the profile says so and keeps no copy of that product's specification.
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 Friedrich-Alexander-Universität Erlangen-Nürnberg the way a machine reads it — 15 machine-readable artifacts across 9 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 — Friedrich-Alexander-Universität Erlangen-Nürnberg scores 37.1/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.
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 Friedrich-Alexander-Universität Erlangen-Nürnberg'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/friedrich-alexander-universitat-erlangen-nurnberg/"
title="Friedrich-Alexander-Universität Erlangen-Nürnberg on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/friedrich-alexander-universitat-erlangen-nurnberg.svg"
alt="Friedrich-Alexander-Universität Erlangen-Nürnberg Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/friedrich-alexander-universitat-erlangen-nurnberg/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/friedrich-alexander-universitat-erlangen-nurnberg/"
title="Friedrich-Alexander-Universität Erlangen-Nürnberg on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/friedrich-alexander-universitat-erlangen-nurnberg/card.svg"
alt="Friedrich-Alexander-Universität Erlangen-Nürnberg 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 Friedrich-Alexander-Universität Erlangen-Nürnberg
Each block below is one kind of artifact we hold for Friedrich-Alexander-Universität Erlangen-Nürnberg. 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.
OPEN FAU OAI-PMH Metadata Service
Open Archives Initiative Protocol for Metadata Harvesting 2.0 service for OPEN FAU, the university's open-access publication repository. Verified live on 2026-08-30: Identify re...
OPEN FAU DSpace REST API
The REST/HAL API of OPEN FAU, FAU's DSpace 7.4 institutional repository, run by the University Library on FAU's own host. Verified live on 2026-08-30: the API root at /server/ap...
FAU Matrix Homeserver
FAU operates a Matrix homeserver — Synapse 1.159.0 at matrix.fau.de — with a hosted Element web client at chat.fau.de. It is properly delegated: both https://fau.de/.well-known/...
FAU WebSSO SAML 2.0 Identity Provider
FAU's central web single sign-on, operated by RRZE, publishes SAML 2.0 identity provider metadata as a machine-readable document at https://www.sso.uni-erlangen.de/simplesaml/sa...
FAU Web Platform WordPress REST API
FAU's central web platform is a WordPress estate run by the RRZE Webteam, and its REST API is partly open to anonymous callers. Verified live on 2026-08-30: https://www.fau.de/w...
RRZE GitLab REST API (FAU self-hosted)
RRZE runs FAU's self-hosted GitLab at gitlab.rrze.fau.de, and its v4 REST API answers anonymous reads. Verified live on 2026-08-30: /api/v4/projects?per_page=1 returns HTTP 200 ...
FAU API Gateway (api.fau.de)
api.fau.de is an FAU-operated API portal — the browser title is "FAU API", the single-page application is served from FAU's own network, and its footer links to rrze.fau.de and ...
NHR@FAU ClusterCockpit Job Monitoring API
NHR@FAU — the Erlangen National High Performance Computing Center, hosted by FAU — runs ClusterCockpit at monitoring.nhr.fau.de as the job-specific performance monitoring servic...
Clarivate Converis Web Service — FAU CRIS deployment
FAU CRIS is the university's research information system, holding 146,000+ publications and 5,200+ projects and syndicating data to more than a thousand FAU websites. The data i...
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.
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.
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.
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.
Friedrich Alexander Universitat Erlangen Nurnberg Domain Security
TLSv1.3 · HSTS · DNSSEC · DMARC
SECURITYFriedrich Alexander Universitat Erlangen Nurnberg Vulnerability Disclosure
security.txt · contact published
SECURITYResources
Every other property we hold for Friedrich-Alexander-Universität Erlangen-Nürnberg — 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 1
Pagination, idempotency, versioning, errors, and events
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 5
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/friedrich-alexander-universitat-erlangen-nurnberg · machine-readable index on apis.io
This is an independent, third-party profile of Friedrich-Alexander-Universität Erlangen-Nürnberg, 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.