University of Pittsburgh
The University of Pittsburgh is a public research university in Pittsburgh, Pennsylvania, ranked #271 in the QS World University Rankings 2025. It operates no central developer portal, no API gateway and no institution-wide developer program — developer.pitt.edu and apis.pitt.edu do not resolve, and www.pitt.edu serves neither apis.json nor llms.txt. What it does operate is four unrelated machine-readable surfaces built by four different units that share no identifier, no envelope, no error model and no case convention: Project Tycho, a global epidemiological surveillance API at www.tycho.pitt.edu built in the Public Health Dynamics Laboratory; the Western Pennsylvania Regional Data Center, a CKAN 2.11.6 open data portal led by Pitt's UCSUR in partnership with Allegheny County and the City of Pittsburgh; the University Library System's E-Journal Publishing platform, a self-hosted PKP Open Journal Systems estate on ULS's own machines serving conformant OAI-PMH 2.0 across dozens of journals and 14,470 Crossref-registered DOIs; and Pitt Passport, the campus Shibboleth SAML 2.0 identity provider registered in InCommon and eduGAIN. None of the four publishes an OpenAPI, a changelog, a deprecation policy or a status page, and Project Tycho serves a rejected credential with HTTP 200 and an HTML sentence. Two further surfaces carrying Pitt's name are tenancies rather than Pitt's engineering: D-Scholarship@Pitt is now a Hyku Commons tenant (d-scholarship.pitt.edu CNAMEs to pittir.hykucommons.org), and PittAPI is an unofficial library written by a student club. This profile was rebuilt on 2026-08-30 under the university pipeline, which settles who operates a surface before saving anything about it.
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 Pittsburgh the way a machine reads it — 18 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 Pittsburgh scores 39.8/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 University of Pittsburgh'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-pittsburgh/"
title="University of Pittsburgh on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-pittsburgh.svg"
alt="University of Pittsburgh Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/university-of-pittsburgh/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/university-of-pittsburgh/"
title="University of Pittsburgh on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-pittsburgh/card.svg"
alt="University of Pittsburgh 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 Pittsburgh
Each block below is one kind of artifact we hold for University of Pittsburgh. 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 6
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.
Project Tycho API
Project Tycho is an open-access repository for global health surveillance data, built and run at the University of Pittsburgh and served from www.tycho.pitt.edu. It holds case c...
Western Pennsylvania Regional Data Center (WPRDC) CKAN API
WPRDC is a regional open data portal led by the University Center for Social and Urban Research (UCSUR) at the University of Pittsburgh, in partnership with Allegheny County and...
ULS E-Journal Publishing — OAI-PMH 2.0 providers
The University Library System publishes dozens of open-access journals on PKP Open Journal Systems that ULS self-hosts, each with a conformant OAI-PMH 2.0 provider on a pitt.edu...
Pitt Passport (Shibboleth SAML 2.0 Identity Provider)
The University of Pittsburgh's campus-wide single sign-on identity provider. Its SAML 2.0 metadata is publicly readable at the canonical Shibboleth /idp/shibboleth location, dec...
D-Scholarship@Pitt Institutional Repository (Hyku Commons) — tenant
D-Scholarship@Pitt is the University Library System's institutional repository of research and scholarly output. The content, the collections and the DataCite DOIs are Pitt's; t...
PittAPI (Pitt Computer Science Club) — student-built
PittAPI is an unofficial, community-maintained Python library published by the Pitt Computer Science Club that scrapes University of Pittsburgh web sources for courses, dining, ...
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 Pittsburgh 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 Pittsburgh 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 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.
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 Pittsburgh — 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.
Documentation 5
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 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 11
Properties that don't map to a standard resource type
Scroll within the panel for all 11 ·
← All providers · Data indexed from github.com/api-evangelist/university-of-pittsburgh · machine-readable index on apis.io
This is an independent, third-party profile of University of Pittsburgh, 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.