Eindhoven University of Technology
Eindhoven University of Technology (TU/e) is a public technical university in Eindhoven, the Netherlands, and one of the four institutions of the 4TU federation. It operates no public developer portal, publishes no institution-authored API contract, and offers no self-serve API keys — and this profile says so rather than padding the gap. Everything machine-readable that carries the TU/e name is a deployment of somebody else's software: the TU/e Research Portal and its Pure Web Service REST API are Elsevier Pure 5.35.x running at pure.tue.nl, the student mobile app at osiris.tue.nl is Caci Osiris, library discovery is OCLC WorldCat, and research datasets are minted through the 4TU.ResearchData Figshare consortium. What TU/e genuinely operates on its own domain is narrower and real: a live, fully conformant OAI-PMH 2.0 harvesting endpoint at pure.tue.nl/ws/oai serving seven metadata formats and the OpenAIRE CERIF 1.2 CRIS profile, and a SAML 2.0 identity-provider entity registered in the SURFconext federation and so reachable through eduGAIN. Thirty-seven OpenAPI documents previously attributed to TU/e in this repository were Elsevier's Pure product contract (info.title "Pure …", contact pure-support@elsevier.com, relative servers "/ws/api", shipped identically by nine other universities) and have been removed; the tenant relationships they described are recorded here instead. Departmental research groups publish open source across many separate GitHub organizations, but the university runs no single official engineering org.
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 Eindhoven University of Technology the way a machine reads it — 8 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 — Eindhoven University of Technology scores 25.7/100 (emerging), with a separate agent-readiness read of 3/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/e publishes no institution-authored API contract and operates no developer portal. Every machine-readable surface found is a vendor's product running under TU/e's name: Elsevier Pure (research portal, Pure Web Service, OAI-PMH), Caci Osiris (student mobile), OCLC WorldCat (library discovery), Figshare via the 4TU.ResearchData consortium (datasets), and Microsoft Entra ID behind SURFconext (identity). Three of those are TU/e's own deployments and are recorded as tenant surfaces; the rest belong in the vendors' own repositories. The one fully public, keyless, verified-by-real-request surface is the OAI-PMH endpoint. Probed and NOT found, so the absence is measured rather than assumed: data.tue.nl, api.tue.nl, developer.tue.nl, opendata.tue.nl, ooapi.tue.nl, api.ooapi.tue.nl, idp.tue.nl, login.tue.nl, sts.tue.nl, sis.tue.nl, mytimetable.tue.nl and rooster.tue.nl all fail to resolve in DNS — they are not gated, they do not exist. purefaq.tue.nl, the Pure FAQ this repo previously carried as a Documentation pointer, now returns a deliberate TU/e "Off-site access blocked" page: it is VPN/campus-network-only, so it is recorded as evidence here and removed as a pointer. TU/e is named by SURF as a 2019 Open Onderwijs API (OOAPI) participant, but Dutch OOAPI endpoints are SURFconext-gated and none is publicly discoverable. github.com/TUEIndhoven resolves but holds zero public repositories; the departmental orgs (tue-datastewards, tue-robotics, tue-mdse, tue-aga, TUe-ICTLab, 3DCP-TUe) are research-group code, not an institutional API programme.
This is an honest zero, not a gap in our research. Eindhoven University of Technology does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://pure.tue.nl/ws/oai?verb=Identify→ HTTP 200https://pure.tue.nl/ws/oai?verb=ListMetadataFormats→ HTTP 200https://pure.tue.nl/ws/oai?verb=ListRecords&metadataPrefix=oai_cerif_openaire&set=openaire_cris_persons→ HTTP 200https://pure.tue.nl/ws/api/documentation/index.html→ HTTP 200https://metadata.surfconext.nl/idps-metadata.xml→ HTTP 200https://www.tue.nl/en/→ HTTP 200https://www.tue.nl/llms.txt→ HTTP 404https://purefaq.tue.nl/pure/faq/index.php?action=overview→ HTTP 403https://research.tue.nl/en/organisations/→ HTTP 403https://osiris.tue.nl/→ HTTP 200https://tue.on.worldcat.org/discovery→ HTTP 200https://data.4tu.nl/search?q=&categories=&organizations=Eindhoven%20University%20of%20Technology→ HTTP 200https://www.tueindhoven.ai/education/guidelines/index.html→ HTTP 200https://www.tue.nl/.well-known/security.txt→ HTTP 200https://github.com/TUEIndhoven→ HTTP 200https://educationguide.tue.nl/→ HTTP 200
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 Eindhoven University of Technology'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/eindhoven-university-of-technology/"
title="Eindhoven University of Technology on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/eindhoven-university-of-technology.svg"
alt="Eindhoven University of Technology Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/eindhoven-university-of-technology/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/eindhoven-university-of-technology/"
title="Eindhoven University of Technology on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/eindhoven-university-of-technology/card.svg"
alt="Eindhoven University of Technology 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 Eindhoven University of Technology
Each block below is one kind of artifact we hold for Eindhoven 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 3
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.
TU/e Research Portal OAI-PMH
Live OAI-PMH 2.0 harvesting interface for the TU/e Research Portal, served by Elsevier Pure at TU/e's own pure.tue.nl. Verified with a real harvest, not link presence: verb=Iden...
TU/e Pure Web Service (Elsevier Pure deployment)
TU/e's deployment of the Elsevier Pure Web Service REST API, the research-information (CRIS) interface behind the TU/e Research Portal. The deployment's own generated documentat...
TU/e SAML Identity Provider (SURFconext / eduGAIN)
TU/e's SAML 2.0 identity-provider entity as published in the SURFconext federation metadata, which feeds eduGAIN. The EntityDescriptor carries OrganizationName "Technische Unive...
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.
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 Eindhoven 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.
Documentation 1
Reference material describing how the API behaves
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
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 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/eindhoven-university-of-technology · machine-readable index on apis.io
This is an independent, third-party profile of Eindhoven University of Technology, 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.