University of Southern California
The University of Southern California is a private research university in Los Angeles, ranked #59 in the QS World University Rankings 2025. USC operates no central developer portal, publishes no OpenAPI, AsyncAPI or apis.json anywhere on its public surface, and issues no self-service API keys — www.usc.edu serves neither llms.txt nor .well-known/security.txt, and api.usc.edu is a default IIS Windows Server placeholder page last modified in 2019, not an API. What USC does operate, verified live on 2026-08-30, is three genuinely institutional machine surfaces: a Shibboleth SAML 2.0 identity provider whose metadata is published unauthenticated at shibboleth.usc.edu and registered with InCommon as urn:mace:incommon:usc.edu; a DataCite direct membership under its own name that carries eleven repositories and 1.5 million minted DOIs; and the FaceBase craniofacial data hub, whose keyless ERMrest REST API is built and run by USC's own Information Sciences Institute on ISI's Apache-2.0 DERIVA stack. Everything else that looks like a USC API is a vendor's contract running under USC's name and is recorded here as a tenant relationship, never as USC's engineering: Figshare, Ex Libris Primo/Alma, Orange Logic Cortex and Instructure Canvas. The Schedule of Classes Web Services API that this profile previously led with is gone — web-app.usc.edu no longer resolves at all.
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 Southern California the way a machine reads it — 13 machine-readable artifacts across 8 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 Southern California scores 25.0/100 (emerging), with a separate agent-readiness read of 3/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. 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 Southern California'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/usc/"
title="University of Southern California on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/usc.svg"
alt="University of Southern California Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/usc/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/usc/"
title="University of Southern California on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/usc/card.svg"
alt="University of Southern California 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 Southern California
Each block below is one kind of artifact we hold for University of Southern California. 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 8
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.
USC Shibboleth Identity Provider (SAML 2.0 Metadata)
USC's production single sign-on identity provider, operated by USC Information Technology Services on USC's own host, publishing its SAML 2.0 metadata unauthenticated. GET https...
FaceBase ERMrest Data API
Keyless, read-only JSON REST API of the FaceBase craniofacial data hub, an NIDCR-funded resource led from USC and engineered by USC's Information Sciences Institute. GET https:/...
USC DataCite DOI Registration (Provider Account)
USC holds a DataCite direct membership in its own name and mints DOIs for eleven USC repositories under it. GET https://api.datacite.org/providers/usc returns 200 with name "Uni...
USC Digital Library API (Orange Logic Cortex)
A live, token-gated REST API on USC's own host running Orange Logic's Cortex digital asset platform. GET https://digitallibrary.usc.edu/API/search/v3.0/search?query=test&format=...
USC Figshare Research Repository (Tenant)
USC Libraries offers Figshare to USC researchers as its data-output repository for datasets, posters and presentations, at the institution-specific tenant usc.figshare.com. Prob...
USC Libraries Discovery (Ex Libris Primo VE, Tenant)
USC Libraries' catalog and discovery layer runs on Ex Libris Primo VE as institution view 01USC_INST:01USC at uosc.primo.exlibrisgroup.com. The public Primo configuration REST e...
USC Canvas Learning Management System (Instructure, Tenant)
USC's learning management system is an Instructure Canvas tenant at usc.instructure.com, verified live 2026-08-30 (200, redirecting to /login/canvas). Canvas exposes a substanti...
USC Schedule of Classes (SOC) — Web Services API, retired
USC's Schedule of Classes Web Services API, which exposed terms, departments, courses and sections and once powered the online schedule, is retired. Its host, web-app.usc.edu, n...
Scroll within the panel for all 8 ·
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.
Usc 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.
Usc 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.
Usc 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.
Usc 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 Southern California — 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.
Documentation 3
Reference material describing how the API behaves
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 1
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 5
The organization behind the API
Other 8
Properties that don't map to a standard resource type
Scroll within the panel for all 8 ·
← All providers · Data indexed from github.com/api-evangelist/usc · machine-readable index on apis.io
This is an independent, third-party profile of University of Southern California, 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.