University of Michigan-Ann Arbor
The University of Michigan-Ann Arbor is a public research university (QS World University Rankings 2025 #20-21, United States), a member of the Association of American Universities and the Big Ten Academic Alliance. Its programmable footprint is large in aggregate and almost entirely closed to the public. The enterprise estate — MCommunity directory, Schedule of Classes, class rosters, room scheduling and other institutional data — sits behind the U-M ITS API Directory on Google Apigee X, which cannot be browsed, let alone called, without a U-M uniqname, Duo two-factor authentication and presence on the U-M network or VPN. What is genuinely open and genuinely U-M's own is library and identity infrastructure: the Deep Blue Documents DSpace repository publishes a fully working OAI-PMH 2.0 harvesting endpoint on a umich.edu host (all six verbs verified live, twelve metadata formats, 726 sets, records back to 2005), and U-M ITS Identity and Access Management operates its own Shibboleth SAML 2.0 identity provider registered in InCommon, with public SAML and OIDC integration examples on GitHub. U-M Library is a DataCite direct member (symbol UMICH, five repositories) and a Crossref member (prefix 10.3998). Around those sit smaller institution-run surfaces — the Magic Bus transit API and Deep Blue Data — and one large vendor tenancy, Canvas at umich.instructure.com, whose contract belongs to Instructure and is not stored here. U-M publishes no public developer portal, no OpenAPI, no changelog and no API terms of service. Most of the umich.edu estate returns a Cloudflare bot challenge to automated clients, so several pointers below are documented-and-live rather than machine-readable.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles University of Michigan-Ann Arbor the way a machine reads it — 16 machine-readable artifacts across 1 API, 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 Michigan-Ann Arbor scores 59.2/100 (strong), with a separate agent-readiness read of 30/100 (agent ready). 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
U-M's programmable footprint is real and mostly unreachable, for two different reasons that must not be conflated. FIRST, and this is the finding about the institution: the enterprise API estate — MCommunity, Schedule of Classes, class rosters, room scheduling — lives in the ITS API Directory on Apigee X and requires a U-M uniqname, Duo two-factor authentication and U-M network/VPN presence to even browse. There is no public developer registration path, so no endpoint in it could be probed or described, and none has been. SECOND, and this is a limit on us rather than on them: most of the umich.edu estate sits behind a Cloudflare managed challenge and returns HTTP 403 "Just a moment..." to automated clients — umich.edu, its.umich.edu, documentation.its.umich.edu, deepblue.lib.umich.edu, search.lib.umich.edu, arc.umich.edu, genai.umich.edu, safecomputing.umich.edu, ro.umich.edu and www.icpsr.umich.edu among them. Those pointers are live and real; they are just not readable by us, and they should be re-probed with a browser-grade client. Deep Blue Data in particular is a documented public REST API that we could not read, so no contract was written for it. What WAS fully readable is genuinely U-M's and is described here in full: the Deep Blue Documents OAI-PMH endpoint (all six verbs, twelve metadata formats, 726 sets, four error codes reproduced) and the U-M Shibboleth SAML 2.0 identity provider registered in InCommon. One vendor tenancy is recorded rather than absorbed: Canvas at umich.instructure.com. A suspected Figshare tenancy at umich.figshare.com was REJECTED — a nonsense control subdomain returns the identical AWS WAF 202, so the response is a wildcard artefact and not evidence of a U-M account.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is University of Michigan-Ann Arbor'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://backend.production.deepblue-documents.lib.umich.edu/server/oai/request?verb=Identify→ HTTP 200https://backend.production.deepblue-documents.lib.umich.edu/server/oai/request?verb=ListMetadataFormats→ HTTP 200https://backend.production.deepblue-documents.lib.umich.edu/server/oai/request?verb=ListSets→ HTTP 200https://backend.production.deepblue-documents.lib.umich.edu/server/oai/request?verb=GetRecord&identifier=oai:deepblue.lib.umich.edu:2027.42/61022&metadataPrefix=oai_dc→ HTTP 200https://shibboleth.umich.edu/idp/shibboleth→ HTTP 200https://mdq.incommon.org/entities/https%3A%2F%2Fshibboleth.umich.edu%2Fidp%2Fshibboleth→ HTTP 200https://api.datacite.org/providers/umich→ HTTP 200https://mbus.ltp.umich.edu/bustime/api/v3/getroutes→ HTTP 200https://umich.instructure.com/api/v1/accounts→ HTTP 401https://zzznotarealtenant.instructure.com/api/v1/accounts→ HTTP 404https://umich.figshare.com/→ HTTP 202https://zzznotarealtenant.figshare.com/→ HTTP 202https://www.lib.umich.edu→ HTTP 200https://atlas.ai.umich.edu/→ HTTP 200https://materialscommons.org/→ HTTP 200https://github.com/umich-iam→ HTTP 200https://its.umich.edu/data/data-database/api-directory→ HTTP 403https://deepblue.lib.umich.edu/data/rest-api→ HTTP 403https://umich.edu→ HTTP 403https://arc.umich.edu/→ HTTP 403https://genai.umich.edu/→ HTTP 403https://api.umich.edu/→ HTTP 0
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 Michigan-Ann Arbor'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/university-of-michigan-ann-arbor/"
title="University of Michigan-Ann Arbor on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-michigan-ann-arbor.svg"
alt="University of Michigan-Ann Arbor Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/university-of-michigan-ann-arbor/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/university-of-michigan-ann-arbor/"
title="University of Michigan-Ann Arbor on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-michigan-ann-arbor/card.svg"
alt="University of Michigan-Ann Arbor 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 Michigan-Ann Arbor
Each block below is one kind of artifact we hold for University of Michigan-Ann Arbor. 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.
U-M Shibboleth Identity Provider (InCommon)
The University of Michigan's own Shibboleth SAML 2.0 identity provider, and the most unambiguously institution-operated machine-readable surface U-M publishes. GET https://shibb...
U-M ITS API Directory
Enterprise API directory and gateway operated by U-M Information and Technology Services on Google Apigee X (migrated from IBM API Connect v5 in 2024), exposing institutional da...
Deep Blue Data REST API
Public REST API for Deep Blue Data, the University of Michigan Library's open repository for research datasets produced by U-M researchers, with DataCite DOI persistent identifi...
Magic Bus (U-M Transit) BusTime API
Real-time campus transit API for U-M's Magic Bus service, served from a U-M host on Clever Devices BusTime. Live and gated by an API access key — GET /bustime/api/v3/getroutes a...
Materials Commons
Materials-science data repository for storing, sharing and publishing research datasets and workflows, operated by the PRISMS Center at the University of Michigan. It advertises...
Canvas LMS (U-M tenancy on Instructure)
The University of Michigan's Canvas learning management system tenancy. The courses, the enrollments and the data are U-M's; the API contract is Instructure's, published once fo...
University of Michigan-Ann Arbor Repository API
Repository-level description and capability discovery.
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 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.
University Of Michigan Ann Arbor 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.
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.
Spectral 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 1
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.
Deep Blue Documents OAI-PMH Response
JSON SCHEMASecurity 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.
Resources
Every other property we hold for University of Michigan-Ann Arbor — 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 3
Reference material describing how the API behaves
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 7
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 7 ·
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 3
Pricing, plans, and the legal terms of use
Company 3
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/university-of-michigan-ann-arbor · machine-readable index on apis.io
This is an independent, third-party profile of University of Michigan-Ann Arbor, 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.