University of the Witwatersrand
The University of the Witwatersrand (Wits) is a leading public research university in Johannesburg, South Africa, ranked #268 in the QS World University Rankings 2025. Wits does not operate a central, branded developer portal, but it exposes standards-based machine-readable interfaces through its library and open-research infrastructure. The most clearly public surfaces are the WIReDSpace institutional repository (DSpace 9.2), which offers both a REST API and an OAI-PMH metadata harvesting endpoint, and the Wits Open Data Vault, a Figshare-powered research data repository carrying DOIs for datasets. Other systems (Springshare LibGuides/LibCal, identity/SSO, and student services) are vendor-hosted and generally gated rather than openly documented.
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 the Witwatersrand the way a machine reads it — 32 machine-readable artifacts across 15 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 the Witwatersrand scores 51.4/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 the Witwatersrand
Each block below is one kind of artifact we hold for University of the Witwatersrand. 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 15
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 the Witwatersrand altmetric API
The altmetric API from University of the Witwatersrand — 1 operation(s) for altmetric.
University of the Witwatersrand articles API
The articles API from University of the Witwatersrand — 34 operation(s) for articles.
University of the Witwatersrand authors API
The authors API from University of the Witwatersrand — 2 operation(s) for authors.
University of the Witwatersrand collections API
The collections API from University of the Witwatersrand — 23 operation(s) for collections.
University of the Witwatersrand Communities API
Top-level and sub-community containers
University of the Witwatersrand Discovery API
Browse and search/discovery endpoints
University of the Witwatersrand institutions API
The institutions API from University of the Witwatersrand — 20 operation(s) for institutions.
University of the Witwatersrand Items API
Repository items (records)
University of the Witwatersrand oauth API
The oauth API from University of the Witwatersrand — 1 operation(s) for oauth.
University of the Witwatersrand other API
The other API from University of the Witwatersrand — 7 operation(s) for other.
University of the Witwatersrand profiles API
The profiles API from University of the Witwatersrand — 2 operation(s) for profiles.
University of the Witwatersrand projects API
The projects API from University of the Witwatersrand — 17 operation(s) for projects.
University of the Witwatersrand Request API
The Request API from University of the Witwatersrand — 1 operation(s) for request.
University of the Witwatersrand Root API
HAL/JSON API root document
University of the Witwatersrand symplectic API
The symplectic API from University of the Witwatersrand — 5 operation(s) for symplectic.
Scroll within the panel for all 15 ·
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 The Witwatersrand 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 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.
Figshare Article
JSON SCHEMAWIReDSpace Community
JSON SCHEMAJSON 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 The Witwatersrand Article Structure
JSON STRUCTUREUniversity Of The Witwatersrand Community Structure
JSON STRUCTUREExamples 3
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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.
University Of The Witwatersrand Agentic Access
166 operations · 81 acting · 2 human-in-the-loop
AGENTICResources
Every other property we hold for University of the Witwatersrand — 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
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
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 2
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-the-witwatersrand · machine-readable index on apis.io