University of California, Los Angeles
The University of California, Los Angeles is a public land-grant research university in the University of California system, ranked 29th in the QS World University Rankings, and it is one of the few institutions in this cohort that genuinely runs a central API program rather than renting one. UCLA operates its own API gateway at api.ucla.edu, fronted by Apigee under a certificate issued to the university, and a Drupal/Apigee developer portal at developer.api.ucla.edu that catalogues eight API products. Seven of those products publish a real machine-readable contract, anonymously downloadable, and all seven describe routes on UCLA's own gateway - six Swagger 2.0 contracts covering the student information system (classes, class sections, courses, GE foundations, a 61-operation Registrar data dictionary, the mainframe production calendar, a connectivity health check and the MyUCLA portal menu) plus one OpenAPI 3.0.3 contract for a campus weather station. Ninety-one operations in total, every one of them a read. UCLA also runs its own Shibboleth identity provider, registered by InCommon under entityID urn:mace:incommon:ucla.edu with REFEDS Research & Scholarship and SIRTFI certification - the most complete machine-readable artifact the university publishes, and the one no API catalogue had looked at. UCLA Library self-hosts a Cantaloupe IIIF image server, a Hyrax digital collections platform and a Dataverse instance, all on ucla.edu hosts under UCLA's own TLS certificates. What UCLA does not have is any way in: every credential requires a UCLA logon and a human approval, there is no self-service path, no status page, no changelog, no llms.txt, no machine-readable catalog index, and no rate-limit or error documentation. The learning management system, BruinLearn, is Instructure Canvas on a vanity subdomain and is recorded as a tenant relationship rather than as UCLA engineering.
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 California, Los Angeles the way a machine reads it — 32 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, Los Angeles scores 52.7/100 (developing), with a separate agent-readiness read of 24/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.
Why this profile is thin
UCLA is the strongest institution-operated API program measured in this cohort so far and it is still not consumable. Seven real OpenAPI contracts covering 91 operations are anonymously downloadable from the developer portal, and every route they describe is live on UCLA's own Apigee gateway - a documented SIS path returns 401 with oauth.v2.InvalidAccessToken and a conformant RFC 6750 Bearer challenge, which proves the contracts describe real endpoints. But a credential exists only after a developer signs in with a UCLA logon, creates an App, selects an API Product and a campus unit approves the request. There is no public registration, no sandbox, no trial key. The portal states plainly that most APIs are only visible after log on, so the eight catalogued products are a subset of an unknown whole. Two secondary limits are recorded rather than treated as findings about UCLA - dataverse.ucla.edu and digital.library.ucla.edu both answer 200 with an Anubis proof-of-work bot challenge on every path, so OAI-PMH, Dataverse version and DOI prefix could not be read and are not claimed; and UCLA Library's Cantaloupe IIIF server answers 403 with a stack trace for every identifier including a deliberate nonsense control, so no manifest could be retrieved. This is a correct gated profile, not a failed probe - roughly 60 URLs were fetched successfully across 15 hosts, including 7 contracts, signed federation metadata and 3 live error surfaces.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is University of California, Los Angeles's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://developer.api.ucla.edu/api-catalog→ HTTP 200https://developer.api.ucla.edu/sites/default/files/apidoc_specs/classes_v1_4.json→ HTTP 200https://developer.api.ucla.edu/sites/default/files/apidoc_specs/courses_v1%20%281%29_0.json→ HTTP 200https://developer.api.ucla.edu/sites/default/files/apidoc_specs/dictionary_v1%20%281%29.json→ HTTP 200https://developer.api.ucla.edu/sites/default/files/apidoc_specs/productioncalendarjobs_v1_0.json→ HTTP 200https://developer.api.ucla.edu/sites/default/files/apidoc_specs/_infrastructure_verifyconnectivity_v1.json→ HTTP 200https://developer.api.ucla.edu/sites/default/files/apidoc_specs/_myucla_menudata_v1.json→ HTTP 200https://developer.api.ucla.edu/sites/default/files/apidoc_specs/UCLAWeather_3.yaml→ HTTP 200https://api.ucla.edu/sis/dictionary/buildings/v1→ HTTP 401https://api.ucla.edu/weather/api→ HTTP 401https://api.ucla.edu/oauth/client_credential/accesstoken→ HTTP 200https://api.ucla.edu/nonexistentpath→ HTTP 500https://qa.api.ucla.edu/→ HTTP 404https://mdq.incommon.org/entities/urn%3Amace%3Aincommon%3Aucla.edu→ HTTP 200https://met.refeds.org/met/entity/urn:mace:incommon:ucla.edu/→ HTTP 200https://bruinlearn.ucla.edu/api/lti/security/jwks→ HTTP 200https://bruinlearn.ucla.edu/api/v1/accounts→ HTTP 401https://dataverse.ucla.edu/api/info/version→ HTTP 200https://dataverse.ucla.edu/oai?verb=Identify→ HTTP 200https://digital.library.ucla.edu/catalog/oai?verb=Identify→ HTTP 200https://iiif.library.ucla.edu/→ HTTP 200https://iiif.library.ucla.edu/iiif/2/bogus-identifier/info.json→ HTTP 403https://api.ucla.edu/→ HTTP 500https://data.ucla.edu/→ HTTP 0https://developer-pilot.api.ucla.edu/→ HTTP 0https://weather.atmos.ucla.edu/→ HTTP 0https://www.ucla.edu/llms.txt→ HTTP 404https://developer.api.ucla.edu/.well-known/security.txt→ HTTP 404https://escholarship.org/oai?verb=ListSets→ HTTP 200https://it.ucla.edu/privacy→ HTTP 200
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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from University of California, Los Angeles's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/ucla/"
title="University of California, Los Angeles on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/ucla.svg"
alt="University of California, Los Angeles Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/ucla/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/ucla/"
title="University of California, Los Angeles on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/ucla/card.svg"
alt="University of California, Los Angeles Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile University of California, Los Angeles
Each block below is one kind of artifact we hold for University of California, Los Angeles. 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 14
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.
UCLA Shibboleth Identity Provider (InCommon)
UCLA's own Shibboleth identity provider and the most complete machine-readable artifact the university publishes. Registered by InCommon under entityID urn:mace:incommon:ucla.ed...
UCLA Library IIIF Image Service
UCLA Library self-hosts a Cantaloupe 5.0.5 image server exposing both IIIF Image API 2.x and 3.0 endpoints for its digital collections. Institution-operated on UCLA's own AWS in...
UCLA Library Digital Collections
UCLA Library's digital collections platform, institution-hosted on a UCLA IP under a UCLA-issued certificate and developed in the open by the UCLA Library engineering organisati...
UCLA Dataverse
UCLA's research data repository, running open-source Dataverse on a UCLA-owned host under a UCLA-issued certificate with no vendor CNAME - which distinguishes it from the Figsha...
BruinLearn (Canvas LMS)
UCLA's learning management system. The brand, the courses, the learners and the subdomain are UCLA's; the REST API, the LTI 1.3 implementation, the key rotation and the contract...
University of California, Los Angeles Class Sections API
The Class Sections API from University of California, Los Angeles — 2 operation(s) for class sections.
University of California, Los Angeles Classes API
The Classes API from University of California, Los Angeles — 4 operation(s) for classes.
University of California, Los Angeles Courses API
The Courses API from University of California, Los Angeles — 5 operation(s) for courses.
University of California, Los Angeles Dictionary API
The Dictionary API from University of California, Los Angeles — 61 operation(s) for dictionary.
University of California, Los Angeles GE Foundations API
The GE Foundations API from University of California, Los Angeles — 2 operation(s) for ge foundations.
University of California, Los Angeles Infrastructure API
The Infrastructure API from University of California, Los Angeles — 1 operation(s) for infrastructure.
University of California, Los Angeles My UCLA API
The MyUCLA API from University of California, Los Angeles — 1 operation(s) for myucla.
University of California, Los Angeles Production Calendar Jobs API
The Production Calendar Jobs API from University of California, Los Angeles — 1 operation(s) for production calendar jobs.
University of California, Los Angeles Weather API
The Weather API from University of California, Los Angeles — 14 operation(s) for weather.
Scroll within the panel for all 14 ·
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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Ucla 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.
Ucla 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.
Ucla 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.
Ucla Context
JSON-LDSpectral Rules 1
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 7
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.
UCLA myUCLA menu data — schemas in use
JSON SCHEMAUCLA sis classes — schemas in use
JSON SCHEMAUCLA sis courses — schemas in use
JSON SCHEMAUCLA sis dictionary — schemas in use
JSON SCHEMAUCLA weather — schemas in use
JSON SCHEMAScroll within the panel for all 7 ·
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.
Ucla Bruinlearn Lti Jwks
EXAMPLESecurity 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.
Resources
Every other property we hold for University of California, Los Angeles — 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
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 7
Properties that don't map to a standard resource type
Scroll within the panel for all 7 ·
← All providers · Data indexed from github.com/api-evangelist/ucla · machine-readable index on apis.io
This is an independent, third-party profile of University of California, Los Angeles, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.