Purdue University

Purdue University is a public land-grant research university in West Lafayette, Indiana, United States, a member of the Association of American Universities and the Big Ten Academic Alliance. Purdue operates no central developer portal, no API gateway and no self-service key issuance, and its programmable footprint is small, scattered across service units, and almost entirely undocumented. Four surfaces were confirmed institution-operated by live probe: the Rosen Center for Advanced Computing (RCAC) publishes its own OpenAPI 3.0 document at www.rcac.purdue.edu/api covering 206 paths and 452 operations behind Purdue Web Authentication; Housing and Food Services runs an open, keyless dining menus API at api.hfs.purdue.edu/menus/v2; the Purdue University Research Repository exposes an OAI-PMH 2.0 endpoint at purr.purdue.edu/oaipmh; and Purdue runs its own Shibboleth identity provider, registered in InCommon, whose SAML 2.0 metadata is public. Three further surfaces are recorded as tenant relationships, not Purdue engineering - Purdue e-Pubs on bepress Digital Commons, the events calendar on Localist, and the community-built Purdue.io course-catalog API, which runs on a privately registered domain and DigitalOcean hosting with no evidence of institutional operation or endorsement. The Purdue Libraries API host resolves but has served only a placeholder page since at least June 2026.

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.

How we profile Purdue University

Each block below is one kind of artifact we hold for Purdue 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 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.

Purdue RCAC API

The Rosen Center for Advanced Computing publishes its own OpenAPI 3.0.0 description at www.rcac.purdue.edu/api - 206 paths and 452 operations covering research computing groups ...

Purdue HFS Dining Menus API

A public, keyless HTTP API operated by Purdue University Housing and Food Services at api.hfs.purdue.edu, serving dining-court locations, published daily menus by location and d...

PURR OAI-PMH Metadata API

The Purdue University Research Repository exposes an OAI-PMH 2.0 endpoint for harvesting research dataset metadata, supporting the standard verbs (Identify, ListSets, ListMetada...

Purdue Shibboleth Identity Provider

Purdue operates its own Shibboleth identity provider, entityID https://idp.purdue.edu/idp/shibboleth, with SAML 2.0 SSO endpoints under sso.purdue.edu. The IdP is registered in ...

Purdue e-Pubs OAI-PMH (bepress Digital Commons tenant)

Purdue e-Pubs is the university's institutional repository for scholarly output, reachable at docs.lib.purdue.edu with a working OAI-PMH 2.0 endpoint. The content, the collectio...

Purdue Events Calendar API (Localist tenant)

Purdue's public events calendar at events.purdue.edu serves a live JSON events API on the Localist v2 contract. The events are Purdue's; the API is Localist's. events.purdue.edu...

Purdue.io Course Catalog API (community-built, third-party)

Purdue.io is an OData v4 API over Purdue's course catalog, started in 2015 as a Computer Science senior design project and still maintained by its community. It is genuinely use...

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.

Purdue Plans Pricing

2 plans

PLANS

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.

Purdue Rate Limits

1 limits

RATE LIMITS

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.

Purdue Finops

FINOPS

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.

Purdue University API Rules

8 rules · 1 errors · 3 warnings

SPECTRAL

JSON 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.

Purdue HFS Published Daily Menu

5 properties

JSON SCHEMA

Purdue HFS Dining Location

11 properties

JSON SCHEMA

Examples 2

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.

Purdue Hfs Location Menu Example

2 fields

EXAMPLE

Purdue Hfs Locations Example

2 fields

EXAMPLE

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.

Purdue Authentication

0 schemes

SECURITY

Purdue Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for Purdue 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.

← All providers · Data indexed from github.com/api-evangelist/purdue · machine-readable index on apis.io