How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Vrije Universiteit Amsterdam website screenshot

Vrije Universiteit Amsterdam

Vrije Universiteit Amsterdam (VU Amsterdam) is a public research university in the Netherlands, founded in 1880 and ranked #221 in the QS World University Rankings 2025. It operates no public developer program, no API portal, and no first-party API contract: every OpenAPI previously attributed to VU in this repository was Elsevier's Pure API v5.34.3 (contact pure-support@elsevier.com), the same product contract at least nine other universities ship, and it has been removed. What VU genuinely operates and publishes machine-readably is two protocol surfaces on its own domain — a live OAI-PMH 2.0 repository interface at research.vu.nl/ws/oai serving OpenAIRE CERIF and Dublin Core, administered by the University Library, and a signed SAML 2.0 identity-provider metadata document at stsfed.login.vu.nl published into the SURFconext national federation and onward to eduGAIN. Everything else programmable under a vu.nl subdomain is a vendor product VU is the tenant of: the Elsevier Pure REST web service, VU Yoda (Utrecht University software maintained by SURF for VU), Instructure Canvas, and Semestry MyTimetable — all credential-gated. Research data is also published to the national DataverseNL service. The University Library GitHub organisation (ubvu) is the institution's active open-source presence with 90 public repositories; the official VU GitHub organisation has none.

human only

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles Vrije Universiteit Amsterdam the way a machine reads it — 11 machine-readable artifacts across 7 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 30.1/100 (thin), with a separate agent-readiness read of 5/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.

Behind a wall

Why this profile is thin

Two institution-operated machine-readable surfaces were reached and read in full — the OAI-PMH 2.0 endpoint at research.vu.nl/ws/oai (Identify, ListMetadataFormats, ListSets and a 108KB ListRecords harvest all returned 200) and the signed SAML 2.0 IdP metadata at stsfed.login.vu.nl (200, 116,822 bytes, also present in the SURFconext national feed). Beyond those two, every programmable surface under a vu.nl subdomain is a vendor product VU is a tenant of, and every one of them is credential-gated: the Elsevier Pure REST web service (research.vu.nl/ws/api/524/persons -> 401), Instructure Canvas (canvas.vu.nl/api/v1/accounts -> 401), Semestry MyTimetable (rooster.vu.nl/api/ -> 401) and VU Yoda's WebDAV endpoint (data.yoda.vu.nl -> 401). The two Yoda public hosts and DataverseNL sit behind an Anubis bot challenge that returns HTTP 200 with a "checking your connection" body rather than content, and research.vu.nl HTML pages sit behind a Cloudflare challenge (403) even though its /ws/ protocol endpoints are open. No developer portal, no llms.txt, no security.txt and no institution-authored API contract exists at any probed location. This profile is thin because the institution is a buyer, not a producer — not because the surface was unreachable.

An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Vrije Universiteit Amsterdam's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.

What we probed
  • https://research.vu.nl/ws/oai?verb=IdentifyHTTP 200
  • https://research.vu.nl/ws/oai?verb=ListSetsHTTP 200
  • https://stsfed.login.vu.nl/FederationMetadata/2007-06/FederationMetadata.xmlHTTP 200
  • https://metadata.surfconext.nl/idps-metadata.xmlHTTP 200
  • https://research.vu.nl/ws/api/524/personsHTTP 401
  • https://canvas.vu.nl/api/v1/accountsHTTP 401
  • https://rooster.vu.nl/api/HTTP 401
  • https://data.yoda.vu.nl/HTTP 401
  • https://portal.yoda.vu.nl/HTTP 200
  • https://publication.yoda.vu.nl/HTTP 200
  • https://dataverse.nl/api/info/versionHTTP 200
  • https://research.vu.nl/en/organisationsHTTP 403
  • https://vu.nl/llms.txtHTTP 404
  • https://vu.nl/.well-known/security.txtHTTP 404

If this is out of date, tell us on the provider's repo and we will re-run the profile.

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 Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Vrije Universiteit Amsterdam Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Vrije Universiteit Amsterdam'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/vrije-universiteit-amsterdam/"
   title="Vrije Universiteit Amsterdam on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/vrije-universiteit-amsterdam.svg"
       alt="Vrije Universiteit Amsterdam Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

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 7

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 interface for the Vrije Universiteit Amsterdam Repository, served from the institution's own domain and administered by the VU University Library...

VU Amsterdam SAML 2.0 identity provider (SURFconext / eduGAIN)

Vrije Universiteit Amsterdam operates its own SAML 2.0 identity provider on Microsoft ADFS and publishes signed, machine-readable federation metadata for it. entityID http://sts...

Elsevier Pure REST web service — VU Amsterdam deployment

VU Amsterdam's tenancy of the Elsevier Pure research information system, reachable at research.vu.nl/ws/api and API-key gated (GET /524/persons returns HTTP 401). The contract i...

VU Yoda research data repository

VU Amsterdam's research data management and publication platform, running at portal.yoda.vu.nl. Yoda is open-source iRODS-based software built by Utrecht University and, per its...

VU Amsterdam collection on DataverseNL

Vrije Universiteit Amsterdam publishes research datasets into DataverseNL, the shared national Dataverse service, under the collection dataverse.nl/dataverse/vuamsterdam. The RE...

VU Amsterdam Canvas LMS API

Instructure Canvas deployed for VU Amsterdam at canvas.vu.nl. The Canvas REST API is live and credential-gated — GET /api/v1/accounts returns HTTP 401 with a JSON body — and the...

VU Amsterdam timetable (MyTimetable)

VU Amsterdam's class timetable at rooster.vu.nl, running Semestry MyTimetable (the vendor is named in an HTML comment in the served page). A JSON REST API is live behind authent...

Scroll within the panel for all 7 ·

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 1

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.

Vrije Universiteit Amsterdam Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

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.

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 1

Authentication, authorization, and security posture

Learn 1

Tutorials, courses, talks, and written guidance

Operate 2

Status, limits, changes, and where to get help

← All providers · Data indexed from github.com/api-evangelist/vrije-universiteit-amsterdam · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Vrije Universiteit Amsterdam, 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.