Stanford University
Stanford University is a private research university in Stanford, California. Unusually for a higher-education institution, essentially its entire programmable footprint is genuinely institution-operated rather than a vendor tenancy: every surface listed here runs on a stanford.edu host. Stanford Libraries (SUL-DLSS) publishes five first-party OpenAPI contracts for the Stanford Digital Repository — SDR, DOR Services, Technical Metadata, Preservation Catalog and SURI, 76 operations, Apache 2.0, on its own GitHub org — though the services themselves sit on the internal network. Public and open without credentials are PURL (XML/MODS/IIIF Presentation 2.1 off purl.stanford.edu), the Library Hours JSON:API, and the Registrar's ExploreCourses XML query interface, which reports its own deprecation in every response body. University IT runs the certificate-gated MaIS Registry web services (Account, Person, Student, CourseClass, Privilege, Workgroup) and a metered AI API Gateway keyed to a Stanford billing account. Stanford also publishes signed Shibboleth SAML 2.0 identity-provider metadata at idp.stanford.edu — machine-readable identity federation that most universities never get catalogued. What is missing is equally clear: no OAI-PMH provider was found on any Stanford host, no institution-operated open-data portal, no OAuth scopes, no contact or terms in any contract, no examples on any of the 76 operations, and no unified developer portal spanning the Libraries and University IT surfaces.
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 Stanford University the way a machine reads it — 43 machine-readable artifacts across 5 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 — Stanford University scores 54.1/100 (developing), with a separate agent-readiness read of 26/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. 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 Stanford University'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/stanford/"
title="Stanford University on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/stanford.svg"
alt="Stanford University Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/stanford/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/stanford/"
title="Stanford University on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/stanford/card.svg"
alt="Stanford University 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 Stanford University
Each block below is one kind of artifact we hold for Stanford University. 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 26
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.
Stanford Libraries PURL API
Persistent URLs into the Stanford Digital Repository. GET /{druid} returns HTML, /{druid}.xml returns the cocina publicObject document, /{druid}.mods returns MODS 3.7. Open, no ...
Stanford Libraries IIIF API
IIIF Presentation (v2.1 stable, v3 alpha) and Image v2 APIs over the Stanford Digital Repository. Manifests served from purl.stanford.edu, image tiles from stacks.stanford.edu. ...
Stanford Libraries Library Hours API
Operating hours for 24 Stanford library locations, answered as a JSON:API document at library-hours.stanford.edu/libraries.json. Open, no credential. Verified live 2026-08-19.
Stanford Libraries Digital Stacks API
File and image delivery for Stanford Digital Repository content, served from stacks.stanford.edu. Documentation verified live 2026-08-19; access to individual files follows each...
Stanford Libraries Embed API
oEmbed-style service returning an embeddable viewer for a Stanford Digital Repository object. Documentation verified live 2026-08-19.
ExploreCourses course-data XML query interface
The Registrar's course catalog, queryable as XML by appending view=xml-20140630 to a search. Open, no credential, and the largest genuinely public dataset Stanford serves — a si...
Stanford Identity Provider — SAML 2.0 metadata
Signed Shibboleth SAML 2.0 identity-provider metadata, entityID https://idp.stanford.edu/, valid until 2027-08-16. Declares an IDPSSODescriptor, three SSO bindings (HTTP-POST, H...
Stanford AI API Gateway
Direct API access to the large language models hosted in Stanford's own cloud infrastructure behind the AI Playground, for faculty, staff and students building their own AI appl...
MaIS Registry APIs
University IT's Registry web services — Account, Person, Student, CourseClass, Privilege and Workgroup — over Stanford's consolidated system of record. Documented publicly but g...
CAP / Stanford Profiles API
API over the Community Academic Profiles directory (18,000+ faculty, students, postdocs and staff). The interactive console at cap.stanford.edu/cap-api/console redirects to auth...
Stanford University About API
The About API from Stanford University — 1 operation(s) for about.
Stanford University Authentication API
Authenticate the user
Stanford University Catalog API
Add and update Moabs in the catalog
Stanford University Events API
Operations about events
Stanford University Files API
upload binary files
Stanford University Identifiers API
Identifier operations
Stanford University Integrations API
Integrations with other Systems
Stanford University Jobs API
Operations involving background jobs
Stanford University Legacy API
Legacy endpoints
Stanford University Metadata API
Digital Repository Objects
Stanford University Objects API
Digital Repository Objects
Stanford University Release Tags API
Operations about release tags
Stanford University Versions API
Operations about object versions
Stanford University Workflows API
Operations about workflows
Stanford University Workspaces API
Operations about workspaces
Scroll within the panel for all 26 ·
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.
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.
Stanford 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.
Stanford 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.
Stanford 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.
Stanford University API Rules
SPECTRALJSON Schema 5
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.
DOR Services API — component schemas
JSON SCHEMASDR API — component schemas
JSON SCHEMASURI API — component schemas
JSON SCHEMATechnical Metadata API — component schemas
JSON SCHEMAExamples 3
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 3
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.
Resources
Every other property we hold for Stanford University — 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 2
Reference material describing how the API behaves
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/stanford · machine-readable index on apis.io
This is an independent, third-party profile of Stanford University, 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.