University of Waterloo
The University of Waterloo is a public research university in Waterloo, Ontario, Canada, ranked #115 in the QS World University Rankings 2025 and known for its cooperative education programs and strength in mathematics, engineering, and computer science. Its developer footprint is centered on the University of Waterloo Open Data API (the Open Data Initiative), a public, key-authenticated REST API exposing authoritative academic, campus, and student-information datasets. Official code, documentation, and datasets are published under the verified uWaterloo GitHub organization.
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.
API Evangelist profiles University of Waterloo the way a machine reads it — 35 machine-readable artifacts across 12 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 — University of Waterloo scores 46.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.
How we profile University of Waterloo
Each block below is one kind of artifact we hold for University of Waterloo. 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 12
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.
University of Waterloo AcademicOrganizations API
The AcademicOrganizations API from University of Waterloo — 2 operation(s) for academicorganizations.
University of Waterloo Account API
The Account API from University of Waterloo — 5 operation(s) for account.
University of Waterloo ClassSchedules API
The ClassSchedules API from University of Waterloo — 3 operation(s) for classschedules.
University of Waterloo Courses API
The Courses API from University of Waterloo — 5 operation(s) for courses.
University of Waterloo ExamSchedules API
The ExamSchedules API from University of Waterloo — 2 operation(s) for examschedules.
University of Waterloo FoodServices API
The FoodServices API from University of Waterloo — 6 operation(s) for foodservices.
University of Waterloo HolidayDates API
The HolidayDates API from University of Waterloo — 3 operation(s) for holidaydates.
University of Waterloo ImportantDates API
The ImportantDates API from University of Waterloo — 2 operation(s) for importantdates.
University of Waterloo Locations API
The Locations API from University of Waterloo — 6 operation(s) for locations.
University of Waterloo Subjects API
The Subjects API from University of Waterloo — 3 operation(s) for subjects.
University of Waterloo Terms API
The Terms API from University of Waterloo — 3 operation(s) for terms.
University of Waterloo Wcms API
The Wcms API from University of Waterloo — 8 operation(s) for wcms.
Scroll within the panel for all 12 ·
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.
University Of Waterloo 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.
University of Waterloo API Rules
SPECTRALUniversity of Waterloo API Rules
SPECTRALJSON Schema 5
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.
AcademicOrganization
JSON SCHEMACourse
JSON SCHEMALocation
JSON SCHEMASubject
JSON SCHEMATerm
JSON SCHEMAJSON Structure 4
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.
University Of Waterloo Course Structure
JSON STRUCTUREUniversity Of Waterloo Location Structure
JSON STRUCTUREUniversity Of Waterloo Subject Structure
JSON STRUCTUREUniversity Of Waterloo Term Structure
JSON STRUCTUREExamples 4
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.
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 University of Waterloo — 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.
Get Started 1
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 2
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 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/university-of-waterloo · machine-readable index on apis.io