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 California, Santa Barbara website screenshot

University of California, Santa Barbara

University of California, Santa Barbara (UCSB) is a public land-grant research university and a member of the University of California system, ranked #79 in the QS World University Rankings 2025. UCSB operates a formal, well-structured API Developer Portal at developer.ucsb.edu that exposes campus enterprise APIs across Academics, Administration, Dining, Employees, Housing, and Students categories. Most APIs are gated behind registration and manual account approval (security classifications include Auto-Approved, Access Approval Required, and Private). The UCSB Library also runs the Alexandria Digital Research Library (ADRL), a Samvera/Fedora-based institutional repository, and maintains an official GitHub organization at github.com/ucsb.

human only

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles University of California, Santa Barbara the way a machine reads it — 12 machine-readable artifacts across 7 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 California, Santa Barbara scores 23.9/100 (emerging), with a separate agent-readiness read of 7/100 (human only). 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 — 23.9/100 · emerging
Contract Quality 3.8 / 25
Developer Ergonomics 2.2 / 20
Commercial Clarity 5.8 / 20
Operational Transparency 3.4 / 13
Governance 0.0 / 12
Discoverability 8.8 / 10
Agent readiness — 7/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 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 California, Santa Barbara

Each block below is one kind of artifact we hold for University of California, Santa Barbara. 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 7

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.

UCSB API Developer Portal

Central campus API developer portal for discovering, subscribing to, requesting elevated access for, and consuming UCSB web service APIs. Registration is required and new accoun...

UCSB Academics APIs

APIs covering the life-cycle of campus, departments, and students, including Academic Curriculums, Academic Graduate Programs, Academic Quarter Calendar, BARC Quarter Calendar, ...

UCSB Students APIs

APIs providing access to student rosters and individual student information including demographic, registration, academic program, and schedule data. Includes Student Courses, S...

UCSB Administration APIs

Administrative APIs pertaining to financials, accounts receivable, and related campus systems, including ClassCode Lookup Service, Department Chartfield, PeopleSoft FAU Combinat...

UCSB Dining APIs

APIs providing campus dining venue information used by students, faculty, and staff, including Dining Cams, Dining Commons, Dining Menu, Dining Patrons, and Meal Plan Rates.

UCSB Housing APIs

APIs delivering student housing data, including Contract Status and Housing Assignments.

UCSB Employees APIs

APIs offering faculty and staff details such as the Employee Job API and related identity mapping services.

Scroll within the panel for all 7 ·

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.

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

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

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

Ucsb Context

17 classes · 6 properties

JSON-LD

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.

Ucsb Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for University of California, Santa Barbara — 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

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Other 1

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/ucsb · machine-readable index on apis.io