University of Western Australia
The University of Western Australia (UWA) is a public research university in Perth, Western Australia, and ranked #80 in the QS World University Rankings 2025. Its public developer/API footprint is modest and primarily institutional: UWA operates an Azure API Management developer portal where APIs and products are published and consumed via API keys behind a sign-in, and exposes an Elsevier Pure CRIS Web Service for its Profiles and Research Repository that returns research outputs, people, projects, and related metadata via an API-key-protected REST interface. Most other interfaces are gated behind institutional affiliation or federated identity rather than open self-service.
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 Western Australia the way a machine reads it — 53 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 Western Australia scores 47.0/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile University of Western Australia
Each block below is one kind of artifact we hold for University of Western Australia. 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.
UWA Developer Portal (Azure API Management)
UWA's developer portal, built on Microsoft Azure API Management, where published APIs and products can be discovered, tried interactively, and subscribed to for API keys. The ca...
University of Western Australia activities API
The activities API from University of Western Australia — 4 operation(s) for activities.
University of Western Australia applications API
The applications API from University of Western Australia — 4 operation(s) for applications.
University of Western Australia author-collaborations API
The author-collaborations API from University of Western Australia — 4 operation(s) for author-collaborations.
University of Western Australia awards API
The awards API from University of Western Australia — 5 operation(s) for awards.
University of Western Australia changes API
The changes API from University of Western Australia — 1 operation(s) for changes.
University of Western Australia classification-schemes API
The classification-schemes API from University of Western Australia — 4 operation(s) for classification-schemes.
University of Western Australia concepts API
The concepts API from University of Western Australia — 4 operation(s) for concepts.
University of Western Australia courses API
The courses API from University of Western Australia — 6 operation(s) for courses.
University of Western Australia curricula-vitae API
The curricula-vitae API from University of Western Australia — 4 operation(s) for curricula-vitae.
University of Western Australia datasets API
The datasets API from University of Western Australia — 4 operation(s) for datasets.
University of Western Australia downloads API
The downloads API from University of Western Australia — 3 operation(s) for downloads.
University of Western Australia equipments API
The equipments API from University of Western Australia — 5 operation(s) for equipments.
University of Western Australia events API
The events API from University of Western Australia — 4 operation(s) for events.
University of Western Australia external-organisations API
The external-organisations API from University of Western Australia — 4 operation(s) for external-organisations.
University of Western Australia external-persons API
The external-persons API from University of Western Australia — 4 operation(s) for external-persons.
University of Western Australia fingerprints API
The fingerprints API from University of Western Australia — 4 operation(s) for fingerprints.
University of Western Australia impacts API
The impacts API from University of Western Australia — 4 operation(s) for impacts.
University of Western Australia journals API
The journals API from University of Western Australia — 4 operation(s) for journals.
University of Western Australia keyword-group-configuration API
The keyword-group-configuration API from University of Western Australia — 4 operation(s) for keyword-group-configuration.
University of Western Australia organisational-units API
The organisational-units API from University of Western Australia — 20 operation(s) for organisational-units.
University of Western Australia persons API
The persons API from University of Western Australia — 29 operation(s) for persons.
University of Western Australia press-media API
The press-media API from University of Western Australia — 4 operation(s) for press-media.
University of Western Australia prizes API
The prizes API from University of Western Australia — 4 operation(s) for prizes.
University of Western Australia projects API
The projects API from University of Western Australia — 6 operation(s) for projects.
University of Western Australia publishers API
The publishers API from University of Western Australia — 5 operation(s) for publishers.
University of Western Australia research-outputs API
The research-outputs API from University of Western Australia — 6 operation(s) for research-outputs.
University of Western Australia semantic-groups API
The semantic-groups API from University of Western Australia — 4 operation(s) for semantic-groups.
University of Western Australia thesauri API
The thesauri API from University of Western Australia — 4 operation(s) for thesauri.
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.
Uwa Plans Pricing
PLANSRate 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.
Uwa 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.
Uwa 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.
Uwa 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.
JSON 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.
WSDataSet
JSON SCHEMAWSOrganisation
JSON SCHEMAWSPerson
JSON SCHEMAWSUPMProject
JSON SCHEMAWSResearchOutput
JSON SCHEMAJSON Structure 5
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.
Uwa Dataset Structure
JSON STRUCTUREUwa Organisation Structure
JSON STRUCTUREUwa Person Structure
JSON STRUCTUREUwa Project Structure
JSON STRUCTUREUwa Research Output Structure
JSON STRUCTUREExamples 5
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 University of Western Australia — 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 1
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/uwa · machine-readable index on apis.io