University of Minnesota
The University of Minnesota is a public land-grant research university whose flagship campus is in the Twin Cities. Its programmable footprint is small, real, and unevenly distributed: the one place it publishes machine-readable contracts of its own is GEMS Informatics, whose Exchange APIs serve agricultural, climate and geospatial data from exchange-1.gems.msi.umn.edu behind an api key and ship nine live OpenAPI 3.1 documents. Everything else is either gated, undocumented in machine terms, or somebody else's contract running under the University's name. The OIT Integrations Team's Common Good APIs are institution-operated at integration-boomi.umn.edu but are approved per data custodian and their Swagger lives inside a tenant Boomi developer portal that answers no anonymous request. UMN Libraries operates a genuine JSON API over the UMedia digital collections and an OAI-PMH 2.0 endpoint for the Digital Conservancy, but publishes no contract for either, and UMedia's image delivery runs on the Libraries' OCLC CONTENTdm tenancy rather than on University infrastructure. The strongest institution-operated machine-readable surface the University has is not an API at all: it is the Shibboleth identity provider it publishes through InCommon as urn:mace:incommon:umn.edu. There is no central developer portal, no institution-wide API catalog, and no public API programme.
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 Minnesota the way a machine reads it — 24 machine-readable artifacts across 9 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 Minnesota scores 53.4/100 (developing), with a separate agent-readiness read of 29/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.
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 Minnesota'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-minnesota/"
title="University of Minnesota on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-minnesota.svg"
alt="University of Minnesota Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/university-of-minnesota/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/university-of-minnesota/"
title="University of Minnesota on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-minnesota/card.svg"
alt="University of Minnesota 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 Minnesota
Each block below is one kind of artifact we hold for University of Minnesota. 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 10
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.
GEMS Informatics Exchange APIs
Ten agricultural, climate and geospatial data APIs operated by GEMS Informatics at the University of Minnesota — biotic risk, climate, crop calendar, elevation, hydrology, land ...
Common Good APIs
A suite of APIs published by the OIT Integrations Team over the University's Common Data Layer — person, class, employee, student academic, organization, HR and term information...
UMedia Digital Collections JSON API
A read-only JSON API over UMedia, the University of Minnesota Libraries digital collections platform. Any search or item URL returns JSON when ".json" is appended, with Blacklig...
UMN Digital Conservancy — OAI-PMH and DSpace REST
The University of Minnesota Digital Conservancy, which also holds DRUM (Data Repository for the University of Minnesota), runs DSpace 10.0 on University infrastructure. Its OAI-...
InCommon Identity Federation — University of Minnesota Shibboleth IdP
The University operates its own Shibboleth identity provider and publishes it through the InCommon federation as entityID urn:mace:incommon:umn.edu, with shibmd:Scope umn.edu an...
DataCite membership — University of Minnesota
The University of Minnesota is a DataCite direct member, symbol UMN, registered since 2018-12-19 and linked to ROR 017zqws13. It operates the repository client UMN.DRUM (Data Re...
Crossref membership — University of Minnesota
The University of Minnesota is Crossref member 10551, registering DOIs under prefixes 10.24926 and 10.64517. University of Minnesota Press (member 3779, prefix 10.5749) and Univ...
ROR registration — University of Minnesota
The University of Minnesota's Research Organization Registry identifier is https://ror.org/017zqws13. It is the identifier DataCite links the University's membership to, and the...
Boomi API Developer Portal (UMN tenant)
The University's developer portal for the Common Good APIs runs as a UMN-specific tenant on Boomi's cloud at umn-prod-apigw.boomi.cloud, where it catalogues twenty-four APIs and...
UMedia IIIF image delivery (OCLC CONTENTdm tenant)
UMedia's digital objects are delivered over the IIIF Image API 2.1 from the Libraries' OCLC CONTENTdm instance at cdm16022.contentdm.oclc.org, which every UMedia record points t...
Scroll within the panel for all 10 ·
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 Minnesota 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.
University of Minnesota API Rules
SPECTRALJSON Schema 2
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.
Examples 4
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 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 Minnesota — 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 4
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
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/university-of-minnesota · machine-readable index on apis.io
This is an independent, third-party profile of University of Minnesota, 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.