Washington University in St. Louis
Washington University in St. Louis (WashU) is a private research university in St. Louis, Missouri, now presenting itself on washu.edu with the historic wustl.edu domain redirecting to it. Its programmable footprint is small but, unusually for this cohort, not empty and not entirely someone else's: the McDonnell Genome Institute at WashU School of Medicine builds and operates CIViC, the Clinical Interpretation of Variants in Cancer knowledgebase, whose public GraphQL API at civicdb.org/api/graphql answers anonymous introspection with a 502-type schema, 112 root queries and 47 mutations, documents a bearer-token API key and a 3 request/second rate limit, and is released CC0. WashU also operates its own Shibboleth SAML 2.0 identity provider, published as signed metadata in InCommon with REFEDS Research & Scholarship and SIRTFI assurance — machine readable institutional infrastructure almost no university in this cohort catalogues. Its enterprise integration APIs (Person, Financial, Supplier, Location, Academic, Organization) are real but wholly gated: they live in a MuleSoft Anypoint Exchange tenant and access is granted by internal ServiceNow request, with no public specification, endpoint or sign-up. Everything else is a relationship rather than WashU engineering. The two research repositories that harvest cleanly over OAI-PMH 2.0 — the WashU Scholarly Repository and Digital Commons Data@Becker — both sit on wustl.edu hostnames that CNAME straight to Elsevier infrastructure (bepress and Mendeley Data), so the data and the DOIs are WashU's and the contracts are Elsevier's. WashU is a DataCite direct member with two registered repositories. There is no public open-data portal, no documented course or SIS API, and courses.wustl.edu no longer answers at all.
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 Washington University in St. Louis the way a machine reads it — 17 machine-readable artifacts across 10 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 — Washington University in St. Louis scores 43.1/100 (developing), with a separate agent-readiness read of 18/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 Washington University in St. Louis'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/washington-university-in-st-louis/"
title="Washington University in St. Louis on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/washington-university-in-st-louis.svg"
alt="Washington University in St. Louis Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/washington-university-in-st-louis/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/washington-university-in-st-louis/"
title="Washington University in St. Louis on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/washington-university-in-st-louis/card.svg"
alt="Washington University in St. Louis 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 Washington University in St. Louis
Each block below is one kind of artifact we hold for Washington University in St. Louis. 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.
CIViC — Clinical Interpretation of Variants in Cancer
A free, open, community-curated knowledgebase of the clinical significance of variants in cancer, built and operated by The McDonnell Genome Institute at Washington University S...
WashU Enterprise Integration APIs (MuleSoft Anypoint)
Institutional integration APIs published in a MuleSoft Anypoint Exchange tenant and described publicly as "Data at WashU", covering the Person, Financial, Supplier, Location, Ac...
WashU Shibboleth Identity Provider (InCommon)
Washington University's own SAML 2.0 identity provider, entityID https://login.wustl.edu/idp/shibboleth, published as signed metadata through the InCommon per-entity metadata qu...
WashU Scholarly Repository (OAI-PMH)
The university's institutional repository, "WashU Scholarly Repository", serving a live OAI-PMH 2.0 interface with nine metadata formats including oai_etdms for theses and oai_o...
Digital Commons Data@Becker (Research Data Repository)
The Becker Medical Library and School of Medicine research data repository, publishing an API documentation page and a live OAI-PMH 2.0 endpoint that serves the datacite, oai_da...
DataCite Membership — Washington University in St. Louis Libraries
Washington University in St. Louis Libraries is a DataCite direct member, symbol WUSTL, registered 2018-08-30, region AMER, and linked from DataCite's own record to https://ror....
ROR Registration — Washington University in St. Louis
The institution's Research Organization Registry record, https://ror.org/01yc7t268, carrying its display name, multilingual name variants, the WUSTL acronym, a St. Louis locatio...
WashU WordPress REST APIs (CampusPress)
Every WashU departmental site probed exposes a live, unauthenticated WordPress REST API with a complete route discovery document — data.wustl.edu ("Data at WashU", 467 routes), ...
CNDA — Central Neuroimaging Data Archive (XNAT)
WashU's neuroimaging data archive, running XNAT — imaging informatics software that originated at the university's own Neuroinformatics Research Group. cnda.wustl.edu resolves i...
BALSA Neuroimaging Database
A WashU-operated database of neuroimaging scenes and datasets at balsa.wustl.edu, and now the destination of db.humanconnectome.org, which CNAMEs to proxy.nrg.wustl.edu and redi...
Scroll within the panel for all 10 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
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.
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.
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.
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.
Resources
Every other property we hold for Washington University in St. Louis — 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 2
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
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 5
The organization behind the API
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/washington-university-in-st-louis · machine-readable index on apis.io
This is an independent, third-party profile of Washington University in St. Louis, 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.