Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Eindhoven University of Technology website screenshot

Eindhoven University of Technology

Eindhoven University of Technology (TU/e) is a research-driven public technical university in Eindhoven, Netherlands, ranked #136 in the QS World University Rankings 2025. Its public, machine-readable developer footprint centers on its Elsevier Pure research information system, which exposes the institutional research output through an OAI-PMH metadata-harvesting interface and the Pure Web Service (REST/SOAP) API. TU/e does not operate a single consolidated public developer portal; programmatic access to course, identity, and library systems is generally institution-internal or vendor-mediated, and numerous departmental research groups publish open-source code across separate GitHub organizations.

agent ready

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.

Kin Score

API Evangelist profiles Eindhoven University of Technology the way a machine reads it — 57 machine-readable artifacts across 38 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 45.7/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 45.7/100 · developing
Contract Quality 15.4 / 25
Developer Ergonomics 2.2 / 20
Commercial Clarity 5.8 / 20
Operational Transparency 3.4 / 13
Governance 8.8 / 12
Discoverability 9.3 / 10
Regulatory · Government & Public Sector 7.5 / 15
Agent readiness — 48/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

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 38

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

OAI-PMH metadata-harvesting interface for the TU/e Research Portal, powered by Elsevier Pure. It exposes research-output metadata (publications, projects, researcher profiles, d...

Eindhoven University of Technology activity API

The activity API from Eindhoven University of Technology — 39 operation(s) for activity.

Eindhoven University of Technology application API

The application API from Eindhoven University of Technology — 36 operation(s) for application.

Eindhoven University of Technology authorCollaboration API

The authorCollaboration API from Eindhoven University of Technology — 9 operation(s) for authorcollaboration.

Eindhoven University of Technology award API

The award API from Eindhoven University of Technology — 37 operation(s) for award.

Eindhoven University of Technology classificationScheme API

The classificationScheme API from Eindhoven University of Technology — 7 operation(s) for classificationscheme.

Eindhoven University of Technology concept API

The concept API from Eindhoven University of Technology — 4 operation(s) for concept.

Eindhoven University of Technology conferenceSeries API

The conferenceSeries API from Eindhoven University of Technology — 14 operation(s) for conferenceseries.

Eindhoven University of Technology contract API

The contract API from Eindhoven University of Technology — 26 operation(s) for contract.

Eindhoven University of Technology course API

The course API from Eindhoven University of Technology — 27 operation(s) for course.

Eindhoven University of Technology dataSet API

The dataSet API from Eindhoven University of Technology — 30 operation(s) for dataset.

Eindhoven University of Technology education API

The education API from Eindhoven University of Technology — 14 operation(s) for education.

Eindhoven University of Technology equipment API

The equipment API from Eindhoven University of Technology — 28 operation(s) for equipment.

Eindhoven University of Technology ethicalReview API

The ethicalReview API from Eindhoven University of Technology — 22 operation(s) for ethicalreview.

Eindhoven University of Technology event API

The event API from Eindhoven University of Technology — 22 operation(s) for event.

Eindhoven University of Technology externalOrganization API

The externalOrganization API from Eindhoven University of Technology — 29 operation(s) for externalorganization.

Eindhoven University of Technology externalPerson API

The externalPerson API from Eindhoven University of Technology — 22 operation(s) for externalperson.

Eindhoven University of Technology fingerprint API

The fingerprint API from Eindhoven University of Technology — 3 operation(s) for fingerprint.

Eindhoven University of Technology fundingOpportunity API

The fundingOpportunity API from Eindhoven University of Technology — 21 operation(s) for fundingopportunity.

Eindhoven University of Technology impact API

The impact API from Eindhoven University of Technology — 31 operation(s) for impact.

Eindhoven University of Technology journal API

The journal API from Eindhoven University of Technology — 22 operation(s) for journal.

Eindhoven University of Technology keywordGroupConfiguration API

The keywordGroupConfiguration API from Eindhoven University of Technology — 7 operation(s) for keywordgroupconfiguration.

Eindhoven University of Technology milestone API

The milestone API from Eindhoven University of Technology — 24 operation(s) for milestone.

Eindhoven University of Technology organization API

The organization API from Eindhoven University of Technology — 34 operation(s) for organization.

Eindhoven University of Technology person API

The person API from Eindhoven University of Technology — 58 operation(s) for person.

Eindhoven University of Technology personExpertise API

The personExpertise API from Eindhoven University of Technology — 7 operation(s) for personexpertise.

Eindhoven University of Technology pressMedia API

The pressMedia API from Eindhoven University of Technology — 24 operation(s) for pressmedia.

Eindhoven University of Technology prize API

The prize API from Eindhoven University of Technology — 29 operation(s) for prize.

Eindhoven University of Technology project API

The project API from Eindhoven University of Technology — 33 operation(s) for project.

Eindhoven University of Technology publisher API

The publisher API from Eindhoven University of Technology — 18 operation(s) for publisher.

Eindhoven University of Technology researchOutput API

The researchOutput API from Eindhoven University of Technology — 67 operation(s) for researchoutput.

Eindhoven University of Technology role API

The role API from Eindhoven University of Technology — 2 operation(s) for role.

Eindhoven University of Technology semester API

The semester API from Eindhoven University of Technology — 8 operation(s) for semester.

Eindhoven University of Technology specialization API

The specialization API from Eindhoven University of Technology — 8 operation(s) for specialization.

Eindhoven University of Technology studentProject API

The studentProject API from Eindhoven University of Technology — 26 operation(s) for studentproject.

Eindhoven University of Technology studentThesis API

The studentThesis API from Eindhoven University of Technology — 26 operation(s) for studentthesis.

Eindhoven University of Technology thesaurus API

The thesaurus API from Eindhoven University of Technology — 5 operation(s) for thesaurus.

Eindhoven University of Technology user API

The user API from Eindhoven University of Technology — 7 operation(s) for user.

Scroll within the panel for all 38 ·

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.

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.

Eindhoven University Of Technology Context

25 classes · 4 properties

JSON-LD

Spectral Rules 2

Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.

Eindhoven University of Technology API Rules

5 rules · 3 warnings

SPECTRAL

Eindhoven University of Technology API Rules

6 rules · 2 errors · 3 warnings

SPECTRAL

JSON Schema 3

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.

TU/e Pure Organization

31 properties

JSON SCHEMA

TU/e Pure Person

51 properties

JSON SCHEMA

TU/e Pure ResearchOutput

53 properties

JSON SCHEMA

JSON Structure 3

JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.

JSON Structure definitions describing this provider's data shapes.

Examples 3

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.

Eindhoven University Of Technology Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Eindhoven University Of Technology Vulnerability Disclosure

security.txt · contact published

SECURITY

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Eindhoven University Of Technology Agentic Access

969 operations · 278 acting · 1 human-in-the-loop

969 operations · 278 acting

AGENTIC

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.

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Build 1

SDKs, sample code, and the tooling you integrate with

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/eindhoven-university-of-technology · machine-readable index on apis.io