Maastricht University
Maastricht University (UM) is an international research university in Maastricht, Netherlands, known for its Problem-Based Learning model and ranked #230 in the QS World University Rankings 2025. UM does not operate a unified public developer portal; its confirmed machine-readable footprint consists of standards-based research-infrastructure interfaces rather than a productized API program. The Pure (Elsevier) current research information system at cris.maastrichtuniversity.nl exposes a live OAI-PMH endpoint serving OpenAIRE CERIF metadata, research data is published through the shared DataverseNL platform (a Dataverse instance with a public REST API), and the Maastricht University Institute of Data Science maintains an active open-source GitHub organization. Identity is federated via Shibboleth/SAML.
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 Maastricht University the way a machine reads it — 54 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 — Maastricht University scores 40.7/100 (thin), 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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Maastricht University
Each block below is one kind of artifact we hold for Maastricht University. 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.
Maastricht University Research Portal (Pure) OAI-PMH
OAI-PMH metadata harvesting endpoint for the Maastricht University Pure (Elsevier) current research information system. Verified live, returning OpenAIRE CERIF 1.2 profile metad...
Maastricht University Institute of Data Science (Open Source)
The Maastricht University Institute of Data Science (IDS) maintains an active public GitHub organization with open-source data-science tooling, including MOD-API conformance too...
Maastricht University Access API
The Access API from Maastricht University — 23 operation(s) for access.
Maastricht University addFilesToDataset API
Uploads a set of files to a dataset
Maastricht University addFileToDataset API
Uploads a file for a dataset
Maastricht University addGlobusFilesToDataset API
Uploads a Globus file for a dataset
Maastricht University Admin API
The Admin API from Maastricht University — 127 operation(s) for admin.
Maastricht University Batch API
The Batch API from Maastricht University — 3 operation(s) for batch.
Maastricht University Builtin Users API
The Builtin Users API from Maastricht University — 4 operation(s) for builtin users.
Maastricht University Datasetfields API
The Datasetfields API from Maastricht University — 1 operation(s) for datasetfields.
Maastricht University Datasets API
The Datasets API from Maastricht University — 101 operation(s) for datasets.
Maastricht University Datatags API
The Datatags API from Maastricht University — 1 operation(s) for datatags.
Maastricht University DataverseFeaturedItems API
The DataverseFeaturedItems API from Maastricht University — 1 operation(s) for dataversefeatureditems.
Maastricht University Dataverses API
The Dataverses API from Maastricht University — 43 operation(s) for dataverses.
Maastricht University Edit API
The Edit API from Maastricht University — 1 operation(s) for edit.
Maastricht University ExternalTools API
The ExternalTools API from Maastricht University — 2 operation(s) for externaltools.
Maastricht University Files API
The Files API from Maastricht University — 21 operation(s) for files.
Maastricht University Harvest API
The Harvest API from Maastricht University — 7 operation(s) for harvest.
Maastricht University Inbox API
The Inbox API from Maastricht University — 1 operation(s) for inbox.
Maastricht University Info API
The Info API from Maastricht University — 50 operation(s) for info.
Maastricht University Ingest API
The Ingest API from Maastricht University — 1 operation(s) for ingest.
Maastricht University Licenses API
The Licenses API from Maastricht University — 6 operation(s) for licenses.
Maastricht University Localcontexts API
The Localcontexts API from Maastricht University — 2 operation(s) for localcontexts.
Maastricht University Logout API
The Logout API from Maastricht University — 1 operation(s) for logout.
Maastricht University Mail API
The Mail API from Maastricht University — 1 operation(s) for mail.
Maastricht University Meta API
The Meta API from Maastricht University — 2 operation(s) for meta.
Maastricht University Metadatablocks API
The Metadatablocks API from Maastricht University — 2 operation(s) for metadatablocks.
Maastricht University Mydata API
The Mydata API from Maastricht University — 2 operation(s) for mydata.
Maastricht University Notifications API
The Notifications API from Maastricht University — 8 operation(s) for notifications.
Maastricht University Pids API
The Pids API from Maastricht University — 6 operation(s) for pids.
Maastricht University replaceFilesInDataset API
Replace a file to a dataset
Maastricht University Roles API
The Roles API from Maastricht University — 3 operation(s) for roles.
Maastricht University saveAuxiliaryFileWithVersion API
Save Auxiliary File With Version
Maastricht University Search API
The Search API from Maastricht University — 2 operation(s) for search.
Maastricht University Sendfeedback API
The Sendfeedback API from Maastricht University — 1 operation(s) for sendfeedback.
Maastricht University uploadDatasetLogo API
Uploads a logo for a dataset
Maastricht University Users API
The Users API from Maastricht University — 10 operation(s) for users.
Maastricht University Workflows API
The Workflows API from Maastricht University — 1 operation(s) for workflows.
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.
Maastricht 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.
Maastricht 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.
Maastricht Context
JSON-LDSpectral 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.
Maastricht University API Rules
SPECTRALMaastricht University API Rules
SPECTRALJSON Schema 2
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.
JSON Structure 2
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.
Maastricht Dataset Structure
JSON STRUCTUREMaastricht Dataverse Structure
JSON STRUCTUREExamples 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.
Maastricht Search Example
EXAMPLEMaastricht Version Example
EXAMPLESecurity 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.
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.
Resources
Every other property we hold for Maastricht University — 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
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/maastricht · machine-readable index on apis.io