University of California, Los Angeles
The University of California, Los Angeles (UCLA) is a public land-grant research university in Los Angeles, California, ranked #30 in the QS World University Rankings 2025. UCLA operates a centralized API Developer Portal (developer.api.ucla.edu) that publishes a catalog of campus APIs covering student information systems, course and class data, the Registrar data dictionary, MyUCLA menu data, and enterprise integration services. Most products are interactive-documented but gated behind an access request and approval workflow with App Key/secret credentials. UCLA Library additionally exposes IIIF-compliant digital collections manifests for image interoperability.
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.
API Evangelist profiles University of California, Los Angeles the way a machine reads it — 11 machine-readable artifacts across 6 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 23.5/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
How this is scored →scored 2026-07-27 · rubric v0.5
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 6
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.
Classes API
Information on all classes offered in a selected term, including title, description, notes and final exam details, as well as class sections with meeting times, locations, enrol...
Courses API
Information on all approved courses (currently and historically offered) at UCLA, including course title, description, General Education and diversity attributes, and course req...
Dictionary API
Access to general data dictionary information and descriptions from the UCLA Registrar's Office, used to interpret coded values across the student information system APIs. Acces...
MyUCLA Menu Data API
Returns the information needed to build the MyUCLA megamenu navigation, published through the UCLA API Developer Portal. Access is gated by the portal's approval workflow.
Production Calendar Jobs API
Endpoints for obtaining information about production calendar operations and scheduled jobs, published through the UCLA API Developer Portal. Access is gated by the portal's app...
UCLA Library Digital Collections IIIF
UCLA Library Digital Collections comply with the International Image Interoperability Framework (IIIF). Each item page exposes a IIIF JSON manifest that can be opened in IIIF-co...
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.
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-LDSecurity 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.
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
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
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/ucla · machine-readable index on apis.io