Vrije Universiteit Amsterdam
Vrije Universiteit Amsterdam (VU Amsterdam) is a public research university in the Netherlands, ranked #221 in the QS World University Rankings 2025. Like most universities, VU Amsterdam does not operate a centralized public developer portal. Its programmatic footprint is concentrated in research-infrastructure systems: the VU Research Portal (research.vu.nl), an Elsevier Pure instance that exposes a live OAI-PMH harvesting endpoint and a Pure REST web service, and research data published through DataverseNL. The University Library maintains an active public GitHub organization (ubvu) of open-science tooling. Most teaching, student-information, and identity systems are internal and not publicly documented.
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 Vrije Universiteit Amsterdam the way a machine reads it — 45 machine-readable artifacts across 28 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 — Vrije Universiteit Amsterdam scores 43.5/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 Vrije Universiteit Amsterdam
Each block below is one kind of artifact we hold for Vrije Universiteit Amsterdam. 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 28
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.
VU Research Portal OAI-PMH
OAI-PMH 2.0 metadata harvesting endpoint for the Vrije Universiteit Amsterdam Repository, served by the institution's Elsevier Pure research information system at research.vu.nl...
VU Amsterdam research data on DataverseNL
Vrije Universiteit Amsterdam publishes and shares research datasets through DataverseNL, the national Dataverse repository service. The Dataverse software exposes a documented N...
Vrije Universiteit Amsterdam activity API
The activity API from Vrije Universiteit Amsterdam — 38 operation(s) for activity.
Vrije Universiteit Amsterdam application API
The application API from Vrije Universiteit Amsterdam — 36 operation(s) for application.
Vrije Universiteit Amsterdam authorCollaboration API
The authorCollaboration API from Vrije Universiteit Amsterdam — 9 operation(s) for authorcollaboration.
Vrije Universiteit Amsterdam award API
The award API from Vrije Universiteit Amsterdam — 35 operation(s) for award.
Vrije Universiteit Amsterdam classificationScheme API
The classificationScheme API from Vrije Universiteit Amsterdam — 7 operation(s) for classificationscheme.
Vrije Universiteit Amsterdam concept API
The concept API from Vrije Universiteit Amsterdam — 4 operation(s) for concept.
Vrije Universiteit Amsterdam course API
The course API from Vrije Universiteit Amsterdam — 27 operation(s) for course.
Vrije Universiteit Amsterdam dataSet API
The dataSet API from Vrije Universiteit Amsterdam — 29 operation(s) for dataset.
Vrije Universiteit Amsterdam equipment API
The equipment API from Vrije Universiteit Amsterdam — 26 operation(s) for equipment.
Vrije Universiteit Amsterdam event API
The event API from Vrije Universiteit Amsterdam — 21 operation(s) for event.
Vrije Universiteit Amsterdam externalOrganization API
The externalOrganization API from Vrije Universiteit Amsterdam — 29 operation(s) for externalorganization.
Vrije Universiteit Amsterdam externalPerson API
The externalPerson API from Vrije Universiteit Amsterdam — 22 operation(s) for externalperson.
Vrije Universiteit Amsterdam fundingOpportunity API
The fundingOpportunity API from Vrije Universiteit Amsterdam — 21 operation(s) for fundingopportunity.
Vrije Universiteit Amsterdam journal API
The journal API from Vrije Universiteit Amsterdam — 22 operation(s) for journal.
Vrije Universiteit Amsterdam keywordGroupConfiguration API
The keywordGroupConfiguration API from Vrije Universiteit Amsterdam — 7 operation(s) for keywordgroupconfiguration.
Vrije Universiteit Amsterdam organization API
The organization API from Vrije Universiteit Amsterdam — 33 operation(s) for organization.
Vrije Universiteit Amsterdam person API
The person API from Vrije Universiteit Amsterdam — 57 operation(s) for person.
Vrije Universiteit Amsterdam pressMedia API
The pressMedia API from Vrije Universiteit Amsterdam — 24 operation(s) for pressmedia.
Vrije Universiteit Amsterdam prize API
The prize API from Vrije Universiteit Amsterdam — 28 operation(s) for prize.
Vrije Universiteit Amsterdam project API
The project API from Vrije Universiteit Amsterdam — 33 operation(s) for project.
Vrije Universiteit Amsterdam publisher API
The publisher API from Vrije Universiteit Amsterdam — 18 operation(s) for publisher.
Vrije Universiteit Amsterdam researchOutput API
The researchOutput API from Vrije Universiteit Amsterdam — 66 operation(s) for researchoutput.
Vrije Universiteit Amsterdam role API
The role API from Vrije Universiteit Amsterdam — 2 operation(s) for role.
Vrije Universiteit Amsterdam studentThesis API
The studentThesis API from Vrije Universiteit Amsterdam — 26 operation(s) for studentthesis.
Vrije Universiteit Amsterdam thesaurus API
The thesaurus API from Vrije Universiteit Amsterdam — 5 operation(s) for thesaurus.
Vrije Universiteit Amsterdam user API
The user API from Vrije Universiteit Amsterdam — 7 operation(s) for user.
Scroll within the panel for all 28 ·
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.
Vrije Universiteit Amsterdam 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.
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.
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.
JSON Schema 4
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.
Vrije Universiteit Amsterdam Person Structure
JSON STRUCTUREVrije Universiteit Amsterdam Research Output Structure
JSON STRUCTUREExamples 2
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 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 Vrije Universiteit Amsterdam — 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 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
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 3
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/vrije-universiteit-amsterdam · machine-readable index on apis.io