TU Dresden
Technische Universität Dresden (TUD) is a German public technical university in Dresden, Saxony, a member of TU9 and one of the institutions funded under the German Universities Excellence Strategy. Re-profiled on 2026-08-30 under the API Evangelist university pipeline, which settles WHO OPERATES a surface before crediting it to the institution. The June 2026 profile credited TU Dresden with five OpenAPI contracts and five extra apis[] entries; all five were one document — the Linked Open Data API of the Sächsische Landesbibliothek – Staats- und Universitätsbibliothek Dresden (SLUB), a separate Saxon state institution, served from data.slub-dresden.de and split by tag into five apparent surfaces. Worse, every one of those entries carried a baseURL of vvz.phil.tu-dresden.de, a host the specs never mention, which is why a hostname-based audit read them as institution-owned. Those contracts and the twenty-two schema, structure, JSON-LD, vocabulary, ruleset, example, collection and agentic-access artifacts derived from them have been removed. What is left is what TU Dresden actually runs, and it is more than the old profile showed. The headline find is TUD:AI at llm.scads.ai/v1 — an OpenAI-compatible LLM inference API operated by ZIH and ScaDS.AI Dresden/Leipzig on TU Dresden's own network, keyed from the university's Self-Service Portal, serving nine open-weight chat models plus embedding, audio and image endpoints. Alongside it: OPARA, the DSpace 7.6.2 research-data repository TU Dresden operates for four Saxon institutions, with an open REST API and an OAI-PMH interface; the university's own Shibboleth identity provider, registered in DFN-AAI and exported to eduGAIN, which now also serves OpenID Connect discovery and a JWKS; and the gated lecture-directory JSON API of the Faculty of Arts. Two surfaces are real institutional facts running on somebody else's engineering: the Pure-based research information system at fis.tu-dresden.de and the TU Dresden view of the SLUB-operated Qucosa document server. TU Dresden publishes no OpenAPI of its own, no developer portal, no open data portal and no llms.txt — but it does publish a security.txt, and it holds its own DataCite membership and DOI prefix.
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 TU Dresden the way a machine reads it — 13 machine-readable artifacts across 7 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 — TU Dresden 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.
Why this profile is thin
TU Dresden operates five surfaces of its own and four of the five require an institutional credential, which is the normal shape for a German university and is a finding about the institution, not about us. Nothing blocked the probe: more than sixty hosts and paths were fetched successfully with a browser User-Agent, every status code below was observed live, and the thinness that remains is real. Verified institution-operated and live: TUD:AI at https://llm.scads.ai/v1/models answers with a LiteLLM auth_error envelope for a missing key and a DIFFERENT envelope naming a key hash for an invalid one, which proves the token is validated rather than merely required; llm.scads.ai resolves to 141.76.18.84 and 141.76.19.193, inside the RIPE allocation 141.76.0.0/16 netname TUDINF-LAN, org "Technische Universitaet Dresden", and keys are issued from https://selfservice.tu-dresden.de/services/scads-llm-api/ with support at llm.scads.ai@tu-dresden.de. OPARA answers anonymously at https://opara.zih.tu-dresden.de/server/api with a DSpace 7.6.2 HAL root document and at /server/oai/request with a valid OAI-PMH 2.0 Identify naming adminEmail servicedesk@tu-dresden.de and twelve metadata prefixes. https://idp.tu-dresden.de/idp/shibboleth serves DFN-AAI-registered SAML metadata and /.well-known/openid-configuration plus /idp/profile/oidc/keyset now serve OIDC — correcting the June profile, which recorded OIDC as "planned but not yet available". https://vvz.phil.tu-dresden.de/api?auth_code=test returns "Der Auth-Code ist leider nicht richtig." under a 200. Verified live but tenant-operated: fis.tu-dresden.de is Elsevier Pure (a PureFacade marker in the portal HTML; /ws/api, /ws/oai and /ws/rest all answer 403 while /portal/ws/api answers 404), and https://tud.qucosa.de/oai/?verb=Identify returns an OAI-PMH envelope whose request element names the backend http://sdvcmr-prod-oai01.slub-dresden.de:8080/oai/ and whose adminEmail is qucosa-it@slub-dresden.de, with the DataCite client for it registered as tbyu.ozzulw under SLUB's provider TBYU. Removed as another institution's: the five SLUB LOD contracts at data.slub-dresden.de — SLUB is a Saxon state library that serves TU Dresden under agreement, it holds its own Crossref membership (26325) and its own DataCite provider symbol (TBYU), and its API is not TU Dresden's engineering. Not TU Dresden's either: OPAL at bildungsportal.sachsen.de, the Saxony-wide LMS run by BPS Bildungsportal Sachsen GmbH, and the Mensa API at studentenwerk-dresden.de, run by the student services organisation. Confirmed absent by DNS: data.tu-dresden.de, api.tu-dresden.de, opendata.tu-dresden.de, developer.tu-dresden.de, gitlab.tu-dresden.de, elearning.tu-dresden.de, status.tu-dresden.de, chat.zih.tu-dresden.de and ki.tu-dresden.de all fail to resolve. Confirmed absent by fetch: https://tu-dresden.de/llms.txt 404, https://llm.scads.ai/v1/openapi.json 404, and github.com/tu-dresden holds a single repository. The one contract that is publicly served — https://llm.scads.ai/openapi.json — is LiteLLM's own generic proxy specification, titled "LiteLLM API", and is deliberately not saved here for the same reason the SLUB contracts were removed.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is TU Dresden'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://llm.scads.ai/v1/models→ HTTP 500https://llm.scads.ai/docs/→ HTTP 200https://llm.scads.ai/docs/usage/api/→ HTTP 200https://llm.scads.ai/docs/models/→ HTTP 200https://llm.scads.ai/status/→ HTTP 200https://llm.scads.ai/openapi.json→ HTTP 200https://llm.scads.ai/v1/openapi.json→ HTTP 404https://chat.llm.scads.ai/→ HTTP 200https://selfservice.tu-dresden.de/services/scads-llm-api/→ HTTP 200https://opara.zih.tu-dresden.de/server/api→ HTTP 200https://opara.zih.tu-dresden.de/server/api/core/collections→ HTTP 200https://opara.zih.tu-dresden.de/server/api/discover/search/objects→ HTTP 200https://opara.zih.tu-dresden.de/server/oai/request?verb=Identify→ HTTP 200https://opara.zih.tu-dresden.de/server/oai/request?verb=ListMetadataFormats→ HTTP 200https://opara.zih.tu-dresden.de/server/oai/request?verb=ListSets→ HTTP 200https://opara.zih.tu-dresden.de/server/oai/request?verb=ListRecords&metadataPrefix=oai_dc→ HTTP 200https://idp.tu-dresden.de/idp/shibboleth→ HTTP 200https://idp.tu-dresden.de/.well-known/openid-configuration→ HTTP 200https://idp.tu-dresden.de/idp/profile/oidc/keyset→ HTTP 200https://met.refeds.org/met/entity/https%3A%2F%2Fidp.tu-dresden.de%2Fidp%2Fshibboleth/→ HTTP 200https://vvz.phil.tu-dresden.de/api→ HTTP 200https://vvz.phil.tu-dresden.de/api?auth_code=test→ HTTP 200https://fis.tu-dresden.de/portal/→ HTTP 200https://fis.tu-dresden.de/ws/api→ HTTP 403https://fis.tu-dresden.de/ws/oai?verb=Identify→ HTTP 403https://fis.tu-dresden.de/portal/ws/api→ HTTP 404https://tud.qucosa.de/oai/?verb=Identify→ HTTP 200https://api.datacite.org/providers/kiyb→ HTTP 200https://api.datacite.org/clients/tib.zih→ HTTP 200https://api.datacite.org/dois/10.25532/OPARA-101→ HTTP 200https://api.crossref.org/members?query=dresden→ HTTP 200https://tu-dresden.de/.well-known/security.txt→ HTTP 200https://tu-dresden.de/llms.txt→ HTTP 404https://bildungsportal.sachsen.de/opal/restapi/repo/entries→ HTTP 403https://data.tu-dresden.de/→ HTTP 0https://api.tu-dresden.de/→ HTTP 0https://opendata.tu-dresden.de/→ HTTP 0https://developer.tu-dresden.de/→ HTTP 0https://gitlab.tu-dresden.de/→ HTTP 0
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 TU Dresden'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/tu-dresden/"
title="TU Dresden on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tu-dresden.svg"
alt="TU Dresden Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/tu-dresden/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/tu-dresden/"
title="TU Dresden on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tu-dresden/card.svg"
alt="TU Dresden 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 TU Dresden
Each block below is one kind of artifact we hold for TU Dresden. 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 7
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.
TUD:AI LLM API
An OpenAI-compatible LLM inference API operated by ZIH and ScaDS.AI Dresden/Leipzig for TU Dresden staff, students and ScaDS.AI affiliates, served from a LiteLLM proxy on the un...
OPARA Research Data Repository REST API
The DSpace 7.6.2 REST API of OPARA, the open-access research-data repository ZIH operates for TU Dresden and three further Saxon institutions. The HAL root at /server/api is ser...
OPARA OAI-PMH Harvesting Interface
The standards-based harvesting interface for OPARA — how TU Dresden's research data reaches OpenAIRE, BASE, re3data and the rest of the aggregator layer. Identify returns protoc...
TU Dresden Identity Provider (Shibboleth SAML 2.0 + OpenID Connect)
The university's own Shibboleth identity provider, operated by ZIH, and the surface class this pipeline exists to surface: institution-operated by definition, fully machine-read...
TU Dresden Lecture Catalog API (Vorlesungsverzeichnis)
A gated JSON API over the public data of the TU Dresden lecture directory — courses, seminars, instructors, buildings, semesters, institutes and degree programmes. Access requir...
TU Dresden Research Portal (Elsevier Pure) Web Service
TU Dresden's research information system, a current-research-information-system tenancy on Elsevier Pure, published to the world as the TUD Research Portal at fis.tu-dresden.de....
Qucosa TU Dresden OAI-PMH (Institutional Document Server)
The OAI-PMH 2.0 harvesting interface for the TU Dresden instance of Qucosa, the Saxon document and publication server used for dissertations, theses and open-access publications...
Scroll within the panel for all 7 ·
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.
Tu Dresden 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.
Tu Dresden Finops
FINOPSSecurity 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 TU Dresden — 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 2
Pagination, idempotency, versioning, errors, and events
Build 3
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 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/tu-dresden · machine-readable index on apis.io
This is an independent, third-party profile of TU Dresden, 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.