University of Washington
The University of Washington (UW) is a public research university based in Seattle, Washington, United States, ranked #52 in the QS World University Rankings 2025. UW operates a mature, institutionally documented developer footprint through its UW-IT Enterprise Web Services (EWS) program, which exposes a registry of REST/SOAP web services for student, identity, person, group, and ID-card data, each with public Swagger/OpenAPI documentation. Most production data endpoints require an institutional UW NetID, certificate-based authentication, and approved access; the documentation, service registry, and Swagger specifications are publicly browsable. UW also publishes open scholarly metadata through its ResearchWorks DSpace repository (REST API and OAI-PMH) and maintains active public GitHub organizations.
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 University of Washington the way a machine reads it — 43 machine-readable artifacts across 29 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 Washington scores 40.8/100 (thin), with a separate agent-readiness read of 39/100 (agent aware). 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 University of Washington
Each block below is one kind of artifact we hold for University of Washington. 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 29
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.
Identity Registration Web Service (IRWS)
The Identity Registration Web Service is the UW-IT Identity Registry REST API (V1 and V2) providing access to identity and person registry data. Access is authenticated and appr...
UW-IT Enterprise Web Services Registry
Enterprise Web Services (EWS) is UW-IT's secure collection of REST/SOAP web services that let enterprise business applications access commonly shared source data in a scalable, ...
ResearchWorks Repository (DSpace REST + OAI-PMH)
ResearchWorks is UW's institutional digital repository for disseminating text-based scholarly work produced by the UW community, running on DSpace. It exposes a public DSpace RE...
University of Washington Campus API
The Campus API from University of Washington — 1 operation(s) for campus.
University of Washington Card API
The Card API from University of Washington — 1 operation(s) for card.
University of Washington College API
The College API from University of Washington — 1 operation(s) for college.
University of Washington Course API
The Course API from University of Washington — 2 operation(s) for course.
University of Washington Curriculum API
The Curriculum API from University of Washington — 1 operation(s) for curriculum.
University of Washington Degree API
The Degree API from University of Washington — 2 operation(s) for degree.
University of Washington DegreeAudit API
The DegreeAudit API from University of Washington — 2 operation(s) for degreeaudit.
University of Washington DegreeAuditException API
The DegreeAuditException API from University of Washington — 3 operation(s) for degreeauditexception.
University of Washington DegreeAuditProgram API
The DegreeAuditProgram API from University of Washington — 1 operation(s) for degreeauditprogram.
University of Washington DegreeAuditStatus API
The DegreeAuditStatus API from University of Washington — 1 operation(s) for degreeauditstatus.
University of Washington Department API
The Department API from University of Washington — 1 operation(s) for department.
University of Washington Enrollment API
The Enrollment API from University of Washington — 2 operation(s) for enrollment.
University of Washington EnrollmentMajor API
The EnrollmentMajor API from University of Washington — 1 operation(s) for enrollmentmajor.
University of Washington MajorStudents API
The MajorStudents API from University of Washington — 1 operation(s) for majorstudents.
University of Washington Notice API
The Notice API from University of Washington — 1 operation(s) for notice.
University of Washington Person API
The Person API from University of Washington — 5 operation(s) for person.
University of Washington PersonalFinancial API
The PersonalFinancial API from University of Washington — 1 operation(s) for personalfinancial.
University of Washington Photo API
The Photo API from University of Washington — 3 operation(s) for photo.
University of Washington Program API
The Program API from University of Washington — 2 operation(s) for program.
University of Washington Registration API
The Registration API from University of Washington — 3 operation(s) for registration.
University of Washington ResourceList API
The ResourceList API from University of Washington — 2 operation(s) for resourcelist.
University of Washington Schedule API
The Schedule API from University of Washington — 2 operation(s) for schedule.
University of Washington Section API
The Section API from University of Washington — 5 operation(s) for section.
University of Washington Term API
The Term API from University of Washington — 4 operation(s) for term.
University of Washington TestScore API
The TestScore API from University of Washington — 2 operation(s) for testscore.
University of Washington Version API
The Version API from University of Washington — 1 operation(s) for version.
Scroll within the panel for all 29 ·
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 Washington 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 Washington API Rules
SPECTRALUniversity of Washington 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.
University Of Washington Course Structure
JSON STRUCTUREUniversity Of Washington Photo 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 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.
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 Washington — 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 1
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-washington · machine-readable index on apis.io