Delft University of Technology
Delft University of Technology (TU Delft) is the largest and oldest public technical university in the Netherlands, ranked #51 in the QS World University Rankings 2025. Its public developer footprint centers on research and library data infrastructure rather than a unified developer portal: the 4TU.ResearchData repository (data.4tu.nl), which TU Delft co-founded and leads, exposes a public REST API (v2/v3, the open-source "djehuty" platform) plus OAI-PMH metadata harvesting; the TU Delft Repository (repository.tudelft.nl) publishes open-access theses and research output with OAI-PMH metadata; and TU Delft operates a NetID/OAuth2 single sign-on identity service. TU Delft historically ran a general institutional API platform at api.tudelft.nl (campus, buildings, courses, education and organisation data) secured with OAuth2, but that platform has been publicly announced as being suspended with no new client registrations accepted, so it is documented here as gated/legacy.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Delft University of Technology the way a machine reads it — 11 machine-readable artifacts across 5 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 — Delft University of Technology scores 29.3/100 (emerging), with a separate agent-readiness read of 16/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Delft University of Technology
Each block below is one kind of artifact we hold for Delft University of Technology. 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 5
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.
4TU.ResearchData API
Public REST API for the 4TU.ResearchData repository (data.4tu.nl), which TU Delft co-founded and leads. Provides versioned endpoints (v2/v3) for published articles (datasets), c...
4TU.ResearchData OAI-PMH
OAI-PMH metadata harvesting interface for the 4TU.ResearchData repository, enabling programmatic harvesting of dataset and software metadata (findable via DataCite, Google Datas...
TU Delft Repository (OAI-PMH)
Institutional repository for publicly available TU Delft research output, peer-reviewed articles, technical reports and 46,000+ bachelor/master theses. Metadata is licensed CC0 ...
TU Delft NetID / OAuth2 SSO
TU Delft single sign-on and identity service (NetID) used for authentication across TU Delft web services and as the OAuth2 authorization service (oauth.tudelft.nl) for institut...
TU Delft API Platform (legacy / suspended)
Legacy general-purpose TU Delft API platform (api.tudelft.nl) exposing campus, buildings, computer workspaces, educations, study-years, courses, course schedules, study results/...
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 six things the Kin Score reads for commercial clarity.
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 Delft 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 Delft 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.
Tu Delft Context
JSON-LDSecurity 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 Delft University of Technology — 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
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/tu-delft · machine-readable index on apis.io