University of Maryland College Park
The University of Maryland, College Park (UMD) is the flagship public research university of the University System of Maryland and the state's original 1862 land-grant institution. UMD operates no central developer portal and publishes no university-wide API programme. Its entire confirmed programmable footprint is run by three offices. UMD Libraries publish an Open Data site at opendata.lib.umd.edu documenting the interfaces they operate: a keyless FastAPI service for library hours and bookable-space availability, three live OAI-PMH 2.0 endpoints over digital collections, audio/video collections and ArchivesSpace finding aids, an OpenSearch descriptor over the Avalon A/V catalog, and IIIF Image and Presentation servers. The Division of IT operates the university's Shibboleth identity provider, which publishes SAML 2.0 metadata as InCommon entity urn:mace:incommon:umd.edu with the Research and Scholarship category and SIRTFI assurance — the most consequential machine-readable contract UMD runs, and one no vendor catalogues. The campus GIS office runs an ArcGIS Enterprise 12.1 deployment at gis.umd.edu whose REST service catalog, server info and portal endpoints answer keyless JSON while the fourteen service folders beneath them require a token — the machine-readable backend of the official campus map, and undocumented outside the map itself. Everything else that looks like a UMD API is somebody else's engineering. umd.io, the widely cited course, bus and campus-map API, is a student-run independent project on a NameCheap-registered .io domain hosted at DigitalOcean that states plainly it is not the school; the library discovery layer is Ex Libris Primo through the USMAI consortium; the LMS is Instructure Canvas; web archiving is Archive-It; the open-data repository referral is Dryad. Those are recorded here as tenant relationships, not as UMD's contracts. The DRUM institutional repository is genuinely UMD-operated and was serving a maintenance page across every one of its hosts throughout this review.
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 Maryland College Park the way a machine reads it — 31 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 Maryland College Park scores 47.9/100 (developing), with a separate agent-readiness read of 33/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 Maryland College Park'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-maryland-college-park/"
title="University of Maryland College Park on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-maryland-college-park.svg"
alt="University of Maryland College Park Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/university-of-maryland-college-park/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/university-of-maryland-college-park/"
title="University of Maryland College Park on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-maryland-college-park/card.svg"
alt="University of Maryland College Park 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 Maryland College Park
Each block below is one kind of artifact we hold for University of Maryland College Park. 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 16
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.
UMD Libraries Website Tools API
API middleware operated by the University of Maryland Libraries that exposes today's open/closed status, current bookable-space availability, and raw LibCal space records for fi...
UMD Libraries Digital Collections OAI-PMH
OAI-PMH 2.0 harvesting endpoint over UMD Libraries' Fedora-backed digital collections. Identify reports repositoryName "UMD Libraries" and adminEmail lib-ssdr@umd.edu, with reco...
UMD Libraries Audio/Video Collections OAI-PMH and OpenSearch
The Libraries' Avalon Media System deployment for audio and video collections, with an OAI-PMH 2.0 endpoint (repositoryName "UMD Libraries", adminEmail lib-dpi@umd.edu), an Open...
UMD Archival Collections OAI-PMH
OAI-PMH 2.0 endpoint over the Libraries' ArchivesSpace instance, exposing finding aids for Special Collections and the Performing Arts collections. Identify reports adminEmail a...
UMD Shibboleth Identity Provider — SAML 2.0 Metadata
The university's own Shibboleth identity provider, publishing a SAML 2.0 EntityDescriptor as InCommon entity urn:mace:incommon:umd.edu with scope umd.edu, the InCommon and REFED...
UMD Libraries IIIF Services
IIIF Image and Presentation services operated by UMD Libraries — a Cantaloupe 5.0.5 image server and Papaya 1.2.0, the Libraries' own IIIF Presentation API application, behind a...
UMD Enterprise GIS — ArcGIS REST Services
The university's own ArcGIS Enterprise deployment — ArcGIS Server 12.1.0 and Portal 2026.1 at gis.umd.edu — and the machine-readable backend behind the official campus map at ma...
DRUM — Digital Repository at the University of Maryland
UMD Libraries' DSpace 7 institutional repository of UMD scholarship and research data, and the university's DOI-minting surface. UMD Libraries document a DSpace REST API, an OAI...
Testudo Schedule of Classes
The Office of the Registrar's public Schedule of Classes, a server-rendered web application for browsing course offerings by term and department. It is the authoritative UMD cou...
umd.io — student-run University of Maryland data API
A read-only REST API over UMD course, section, professor, campus bus, building/map and major data, covering ground the university itself does not expose programmatically. It is ...
UMD Discover — library discovery layer
UMD's library catalog and discovery layer, delivered as Ex Libris Primo through the University System of Maryland and Affiliated Institutions (USMAI) consortium. The search expe...
UMD Web Archives on Archive-It
UMD Libraries' web archiving programme, operated as Archive-It organization 408 at the Internet Archive. UMD Libraries document Archive-It's OpenSearch interface as an access ro...
UMD Collection on the Internet Archive
The University of Maryland, College Park collection at the Internet Archive, documented by UMD Libraries as one of their ten Open Data services with archive.org's advancedsearch...
UMD Research Data on Dryad
UMD Libraries refer researchers to Dryad for open research-data deposit and document Dryad's v2 REST API as the access route, scoped to UMD by ROR identifier https://ror.org/047...
BTAA Geoportal — UMD geospatial contributions
The Big Ten Academic Alliance Geoportal, a consortium-operated discovery layer for geospatial data to which UMD Libraries contribute records. Operated by the BTAA at geo.btaa.or...
ELMS-Canvas — UMD learning management system
UMD's learning management system, an Instructure Canvas tenancy at umd.instructure.com fronted by elms.umd.edu. Requests to the tenancy redirect to UMD's own Shibboleth identity...
Scroll within the panel for all 16 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONPricing 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.
FinOps 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.
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 3
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.
UMD Libraries today's open status
JSON SCHEMAUMD Libraries space availability
JSON SCHEMAUMD Libraries raw space records
JSON SCHEMAExamples 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 Maryland College Park — 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 3
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
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 4
The organization behind the API
Other 9
Properties that don't map to a standard resource type
Scroll within the panel for all 9 ·
← All providers · Data indexed from github.com/api-evangelist/university-of-maryland-college-park · machine-readable index on apis.io
This is an independent, third-party profile of University of Maryland College Park, 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.