Aarhus University
Aarhus University (Aarhus Universitet) is a public research university in Aarhus, Denmark, founded in 1928 and ranked #144 in the QS World University Rankings 2025. It does not operate a unified, public developer portal. Its most concrete machine-readable footprint is the Pure research information portal (pure.au.dk), which exposes a Pure web-service / REST API (gated, it returns HTTP 401 without credentials) and an OAI-PMH metadata service for research outputs. Student-facing systems (mitstudie.au.dk / STADS course catalog, timetables with iCal export) are web and feed based rather than documented open APIs, and most code activity lives in departmental GitHub organizations such as cs-au-dk rather than a central program.
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 Aarhus University the way a machine reads it — 58 machine-readable artifacts across 39 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 — Aarhus University scores 45.3/100 (developing), with a separate agent-readiness read of 48/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Aarhus University
Each block below is one kind of artifact we hold for Aarhus 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 39
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.
Pure OAI-PMH Metadata Service
OAI-PMH metadata harvesting service for the Aarhus University Pure research portal, used to expose and harvest research-output metadata. The service path resolves but the Identi...
Course Catalogue and Timetable (mitstudie / STADS)
Public course catalogue (kursuskatalog.au.dk) and the mitstudie.au.dk / STADS student self-service environment, which provides web-based course and timetable information. Timeta...
Aarhus University activity API
The activity API from Aarhus University — 39 operation(s) for activity.
Aarhus University application API
The application API from Aarhus University — 36 operation(s) for application.
Aarhus University authorCollaboration API
The authorCollaboration API from Aarhus University — 9 operation(s) for authorcollaboration.
Aarhus University award API
The award API from Aarhus University — 37 operation(s) for award.
Aarhus University classificationScheme API
The classificationScheme API from Aarhus University — 7 operation(s) for classificationscheme.
Aarhus University concept API
The concept API from Aarhus University — 4 operation(s) for concept.
Aarhus University conferenceSeries API
The conferenceSeries API from Aarhus University — 14 operation(s) for conferenceseries.
Aarhus University contract API
The contract API from Aarhus University — 26 operation(s) for contract.
Aarhus University course API
The course API from Aarhus University — 27 operation(s) for course.
Aarhus University dataSet API
The dataSet API from Aarhus University — 30 operation(s) for dataset.
Aarhus University education API
The education API from Aarhus University — 14 operation(s) for education.
Aarhus University equipment API
The equipment API from Aarhus University — 28 operation(s) for equipment.
Aarhus University ethicalReview API
The ethicalReview API from Aarhus University — 22 operation(s) for ethicalreview.
Aarhus University event API
The event API from Aarhus University — 22 operation(s) for event.
Aarhus University externalOrganization API
The externalOrganization API from Aarhus University — 29 operation(s) for externalorganization.
Aarhus University externalPerson API
The externalPerson API from Aarhus University — 22 operation(s) for externalperson.
Aarhus University fingerprint API
The fingerprint API from Aarhus University — 3 operation(s) for fingerprint.
Aarhus University fundingOpportunity API
The fundingOpportunity API from Aarhus University — 21 operation(s) for fundingopportunity.
Aarhus University impact API
The impact API from Aarhus University — 31 operation(s) for impact.
Aarhus University journal API
The journal API from Aarhus University — 22 operation(s) for journal.
Aarhus University keywordGroupConfiguration API
The keywordGroupConfiguration API from Aarhus University — 7 operation(s) for keywordgroupconfiguration.
Aarhus University milestone API
The milestone API from Aarhus University — 24 operation(s) for milestone.
Aarhus University organization API
The organization API from Aarhus University — 34 operation(s) for organization.
Aarhus University person API
The person API from Aarhus University — 58 operation(s) for person.
Aarhus University personExpertise API
The personExpertise API from Aarhus University — 7 operation(s) for personexpertise.
Aarhus University pressMedia API
The pressMedia API from Aarhus University — 24 operation(s) for pressmedia.
Aarhus University prize API
The prize API from Aarhus University — 29 operation(s) for prize.
Aarhus University project API
The project API from Aarhus University — 33 operation(s) for project.
Aarhus University publisher API
The publisher API from Aarhus University — 18 operation(s) for publisher.
Aarhus University researchOutput API
The researchOutput API from Aarhus University — 67 operation(s) for researchoutput.
Aarhus University role API
The role API from Aarhus University — 2 operation(s) for role.
Aarhus University semester API
The semester API from Aarhus University — 8 operation(s) for semester.
Aarhus University specialization API
The specialization API from Aarhus University — 8 operation(s) for specialization.
Aarhus University studentProject API
The studentProject API from Aarhus University — 26 operation(s) for studentproject.
Aarhus University studentThesis API
The studentThesis API from Aarhus University — 26 operation(s) for studentthesis.
Aarhus University thesaurus API
The thesaurus API from Aarhus University — 5 operation(s) for thesaurus.
Aarhus University user API
The user API from Aarhus University — 7 operation(s) for user.
Scroll within the panel for all 39 ·
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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Aarhus Plans Pricing
PLANSRate 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.
Aarhus 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.
Aarhus Finops
FINOPSSemantic 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.
Aarhus Context
JSON-LDSpectral Rules 2
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.
Aarhus University API Rules
SPECTRALAarhus University API Rules
SPECTRALJSON 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.
Aarhus University Pure API Person
JSON SCHEMAAarhus University Pure API Project
JSON SCHEMAAarhus University Pure API ResearchOutput
JSON SCHEMAJSON Structure 3
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Aarhus Person Structure
JSON STRUCTUREAarhus Project Structure
JSON STRUCTUREAarhus Researchoutput Structure
JSON STRUCTUREExamples 3
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.
Aarhus List Persons Example
EXAMPLEAarhus List Projects Example
EXAMPLESecurity Posture 3
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Aarhus 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/aarhus · machine-readable index on apis.io