Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
University of British Columbia website screenshot

University of British Columbia

The University of British Columbia (UBC) is a public research university in Vancouver and Kelowna, British Columbia, Canada, ranked #33 in the QS World University Rankings 2025. UBC's public developer footprint is led by UBC Library, which operates the Open Collections API (an ElasticSearch-backed REST API over digitized collections) and the Abacus Dataverse research-data repository (a standard Dataverse REST API), along with an OAI-PMH harvesting endpoint. Institutional/enterprise data APIs are delivered through the Office of the CIO's Integration Enablement Centre via MuleSoft and a Data Access Framework, which are gated behind a formal data access request rather than a self-service public developer portal.

agent aware

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 University of British Columbia the way a machine reads it — 41 machine-readable artifacts across 25 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 British Columbia scores 39.9/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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 39.9/100 · thin
Contract Quality 11.4 / 25
Developer Ergonomics 2.2 / 20
Commercial Clarity 5.8 / 20
Operational Transparency 3.4 / 13
Governance 8.8 / 12
Discoverability 8.8 / 10
Regulatory · Government & Public Sector 5.6 / 15
Agent readiness — 39/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile University of British Columbia

Each block below is one kind of artifact we hold for University of British Columbia. 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 25

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.

UBC Library Open Collections API

Public REST/JSON API over UBC Library's Open Collections, the university's digitized historical and research collections. Backed by an ElasticSearch index, it exposes search and...

UBC Library OAI-PMH Endpoint

OAI-PMH metadata-harvesting endpoint exposed by UBC Library Open Collections, supporting the standard Open Archives Initiative Protocol for Metadata Harvesting verbs (Identify, ...

UBC Integration Enablement Centre APIs (MuleSoft / DAF)

Enterprise/institutional APIs delivered by the Office of the CIO's Integration Enablement Centre using MuleSoft, aligned with the University Data Model and secured through a Dat...

University of British Columbia Access API

The Access API from University of British Columbia — 20 operation(s) for access.

University of British Columbia Admin API

The Admin API from University of British Columbia — 113 operation(s) for admin.

University of British Columbia Batch API

The Batch API from University of British Columbia — 3 operation(s) for batch.

University of British Columbia Builtin Users API

The Builtin Users API from University of British Columbia — 4 operation(s) for builtin users.

University of British Columbia Datasets API

The Datasets API from University of British Columbia — 54 operation(s) for datasets.

University of British Columbia Datatags API

The Datatags API from University of British Columbia — 1 operation(s) for datatags.

University of British Columbia Dataverses API

The Dataverses API from University of British Columbia — 26 operation(s) for dataverses.

University of British Columbia Edit API

The Edit API from University of British Columbia — 1 operation(s) for edit.

University of British Columbia Files API

The Files API from University of British Columbia — 9 operation(s) for files.

University of British Columbia Harvest API

The Harvest API from University of British Columbia — 7 operation(s) for harvest.

University of British Columbia Info API

The Info API from University of British Columbia — 40 operation(s) for info.

University of British Columbia Ingest API

The Ingest API from University of British Columbia — 1 operation(s) for ingest.

University of British Columbia Mail API

The Mail API from University of British Columbia — 1 operation(s) for mail.

University of British Columbia Meta API

The Meta API from University of British Columbia — 2 operation(s) for meta.

University of British Columbia Metadatablocks API

The Metadatablocks API from University of British Columbia — 2 operation(s) for metadatablocks.

University of British Columbia Mydata API

The Mydata API from University of British Columbia — 1 operation(s) for mydata.

University of British Columbia Notifications API

The Notifications API from University of British Columbia — 1 operation(s) for notifications.

University of British Columbia Pids API

The Pids API from University of British Columbia — 4 operation(s) for pids.

University of British Columbia Roles API

The Roles API from University of British Columbia — 2 operation(s) for roles.

University of British Columbia Search API

The Search API from University of British Columbia — 1 operation(s) for search.

University of British Columbia Users API

The Users API from University of British Columbia — 8 operation(s) for users.

University of British Columbia Workflows API

The Workflows API from University of British Columbia — 1 operation(s) for workflows.

Scroll within the panel for all 25 ·

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.

Ubc Plans Pricing

2 plans

PLANS

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.

Ubc Rate Limits

1 limits

RATE LIMITS

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.

Ubc Finops

FINOPS

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.

Ubc Context

15 classes · 9 properties

JSON-LD

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 British Columbia API Rules

5 rules · 3 warnings

SPECTRAL

University of British Columbia API Rules

5 rules · 1 errors · 3 warnings

SPECTRAL

JSON Schema 3

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.

UBC Abacus Dataverse DataFile

14 properties

JSON SCHEMA

UBC Abacus Dataverse Dataset

16 properties

JSON SCHEMA

UBC Abacus Dataverse Collection

11 properties

JSON SCHEMA

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.

Ubc Dataset Structure

13 properties

JSON STRUCTURE

Ubc Dataverse Structure

8 properties

JSON STRUCTURE

Examples 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 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.

Ubc Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Ubc Vulnerability Disclosure

security.txt · contact published

SECURITY

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.

Ubc Agentic Access

378 operations · 177 acting · 5 human-in-the-loop

378 operations · 177 acting

AGENTIC

Resources

Every other property we hold for University of British Columbia — 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/ubc · machine-readable index on apis.io