Dartmouth College
Dartmouth College is a private Ivy League research university in Hanover, New Hampshire. Its programmable footprint is small, mostly gated, and largely operated by vendors on Dartmouth's behalf — the ordinary shape for a research university, which is a federation of buyers rather than an API producer. Exactly one institution-operated interface is open to the public without credentials: the JSON backend of Dartmouth Class Search (courses.dartmouth.edu), which returns the full timetable of class meetings keyless and which Dartmouth does not document as an API. Everything else Dartmouth itself runs is behind authentication: DartAPI at api.dartmouth.edu answers 401 on every resource path and issues JWTs only against a hand-issued API key tied to a Dartmouth Service Account, its developer portal at developer.dartmouth.edu redirects to Microsoft Entra SAML so not one reference page is readable from outside, and the Dartmouth Chat AI API requires a DARTMOUTH_API_KEY. The one genuinely open machine-readable artifact Dartmouth publishes is its SAML identity-federation metadata in InCommon. The research and data surfaces — Dartmouth Open Data on ArcGIS Hub, Dartmouth Digital Commons on bepress/Elsevier, Dartmouth Dataverse — are Dartmouth's data on someone else's contract and are recorded here as tenant relationships, not as Dartmouth engineering.
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 Dartmouth College the way a machine reads it — 16 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 — Dartmouth College scores 43.9/100 (developing), with a separate agent-readiness read of 23/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.
Why this profile is thin
Dartmouth operates real APIs and almost all of them are closed. developer.dartmouth.edu, including every /docs/ page, 302s to Microsoft Entra SAML, so DartAPI's endpoint inventory cannot be read from outside the institution and none is asserted here. api.dartmouth.edu answers 401 on every resource path and chat.dartmouth.edu/api answers 401 without a DARTMOUTH_API_KEY — both live, both credentialed, neither describable. What could be captured was captured: the keyless Dartmouth Class Search backend, described from live probes into a full artifact set, and Dartmouth's InCommon SAML metadata. The research and data surfaces are tenant deployments whose contracts belong to Esri, bepress/Elsevier and the Dataverse project. Seven ArcGIS Hub Search OpenAPIs plus 26 files derived from them were removed from this repo on 2026-08-30; they described Esri's product, were re-based onto chat.dartmouth.edu, and their sample data was a StoryMap about a park in Panama City.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Dartmouth College's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://courses.dartmouth.edu/api/?page=fose&route=search→ HTTP 200https://api.dartmouth.edu/api/people/→ HTTP 401https://api.dartmouth.edu/api/jwt→ HTTP 405https://chat.dartmouth.edu/api/models→ HTTP 401https://developer.dartmouth.edu/docs/100_basic/010_introduction.md→ HTTP 302https://mdq.incommon.org/entities/urn%3Amace%3Aincommon%3Adartmouth.edu→ HTTP 200https://digitalcommons.dartmouth.edu/do/oai/?verb=Identify→ HTTP 200https://dataverse.dartmouth.edu/api/info/version→ HTTP 200https://dataverse.dartmouth.edu/oai?verb=Identify→ HTTP 503https://chat.dartmouth.edu/openapi.json→ HTTP 200
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 Dartmouth College'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/dartmouth/"
title="Dartmouth College on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/dartmouth.svg"
alt="Dartmouth College Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/dartmouth/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/dartmouth/"
title="Dartmouth College on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/dartmouth/card.svg"
alt="Dartmouth College 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 Dartmouth College
Each block below is one kind of artifact we hold for Dartmouth College. 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.
Dartmouth Class Search API
The JSON backend of Dartmouth Class Search, the institution's public timetable of class meetings. Keyless: an unauthenticated POST returned 1393 sections for term 202609 on 2026...
DartAPI
Dartmouth's institutional API platform, serving resource APIs such as People (directory identity) and Nextgen class schedules. Live and institution-operated: every resource path...
Dartmouth Chat AI API
An OpenAI- and Anthropic-compatible API over large language, embedding and reranking models running on Dartmouth's own research-computing infrastructure, plus third-party cloud ...
Dartmouth Identity Federation (InCommon)
Dartmouth's SAML identity provider, registered in the InCommon federation under entityID urn:mace:incommon:dartmouth.edu and retrievable as machine-readable metadata over the In...
Dartmouth Open Data (ArcGIS Hub tenant)
Dartmouth's open-data portal, a tenant site on Esri's ArcGIS Hub. The data and the catalog are Dartmouth's; the search API behind it is Esri's Hub Search API on the shared host ...
Dartmouth Digital Commons (bepress/Elsevier tenant)
Dartmouth's institutional repository for scholarly, research and educational output, running on bepress/Elsevier Digital Commons under a Dartmouth subdomain. Its OAI-PMH 2.0 end...
Dartmouth Dataverse
Dartmouth's research-data repository, a Dataverse 6.11 deployment on Dartmouth's own host. The native Dataverse API answers unauthenticated — /api/info/version returns 200 with ...
Scroll within the panel for all 7 ·
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.
Dartmouth 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.
Dartmouth Finops
FINOPSSpectral 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.
Dartmouth College API Rules
SPECTRALJSON Schema 1
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.
Dartmouth Class Search response
JSON SCHEMAExamples 1
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.
Resources
Every other property we hold for Dartmouth College — 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
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 4
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 4
The organization behind the API
Other 7
Properties that don't map to a standard resource type
Scroll within the panel for all 7 ·
← All providers · Data indexed from github.com/api-evangelist/dartmouth · machine-readable index on apis.io
This is an independent, third-party profile of Dartmouth College, 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.