Chalmers University of Technology
Chalmers University of Technology (Chalmers tekniska hogskola) is a private technical university in Gothenburg, Sweden, ranked #139 in the QS World University Rankings 2025. Its public, machine-readable footprint is centered on research information and library/repository services rather than a unified developer portal. Confirmed surfaces include the Chalmers Research API (api.research.chalmers.se), OAI-PMH metadata interfaces for the Chalmers Research portal and the Chalmers Open Digital Repository (ODR), and the Chalmers University Library GitHub organization hosting open-source data and metadata tooling. There is no single consolidated, self-service developer portal; access is API/repository specific.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Chalmers University of Technology the way a machine reads it — 40 machine-readable artifacts across 24 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 — Chalmers University of Technology scores 43.5/100 (thin), 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 Chalmers University of Technology
Each block below is one kind of artifact we hold for Chalmers University of Technology. 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 24
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.
Chalmers Research OAI-PMH
OAI-PMH 2.0 metadata harvesting interface for the Chalmers Research portal (research.chalmers.se), covering Chalmers research publications with records dating back to 1942. Retu...
Chalmers Open Digital Repository (ODR) OAI-PMH
OAI-PMH 2.0 metadata harvesting interface for the Chalmers Open Digital Repository (ODR), which holds student theses and selected special digital collections. Confirmed via an I...
Chalmers University of Technology ContractImport API
The ContractImport API from Chalmers University of Technology — 1 operation(s) for contractimport.
Chalmers University of Technology DeltaImportCplPublication API
The DeltaImportCplPublication API from Chalmers University of Technology — 1 operation(s) for deltaimportcplpublication.
Chalmers University of Technology DeltaImportProjectOrganization API
The DeltaImportProjectOrganization API from Chalmers University of Technology — 1 operation(s) for deltaimportprojectorganization.
Chalmers University of Technology DeltaImportProjectPerson API
The DeltaImportProjectPerson API from Chalmers University of Technology — 1 operation(s) for deltaimportprojectperson.
Chalmers University of Technology ElectronicPublicationAgreementSignature API
The ElectronicPublicationAgreementSignature API from Chalmers University of Technology — 2 operation(s) for electronicpublicationagreementsignature.
Chalmers University of Technology IndexAllProjects API
The IndexAllProjects API from Chalmers University of Technology — 1 operation(s) for indexallprojects.
Chalmers University of Technology IndexOneProject API
The IndexOneProject API from Chalmers University of Technology — 1 operation(s) for indexoneproject.
Chalmers University of Technology LocalOrganizations API
The LocalOrganizations API from Chalmers University of Technology — 1 operation(s) for localorganizations.
Chalmers University of Technology Organizations API
The Organizations API from Chalmers University of Technology — 2 operation(s) for organizations.
Chalmers University of Technology ProjectEmbargos API
The ProjectEmbargos API from Chalmers University of Technology — 1 operation(s) for projectembargos.
Chalmers University of Technology ProjectOrganizationUpdated API
The ProjectOrganizationUpdated API from Chalmers University of Technology — 1 operation(s) for projectorganizationupdated.
Chalmers University of Technology ProjectParticipantsVerification API
The ProjectParticipantsVerification API from Chalmers University of Technology — 1 operation(s) for projectparticipantsverification.
Chalmers University of Technology ProjectParticipantsVerificationMail API
The ProjectParticipantsVerificationMail API from Chalmers University of Technology — 1 operation(s) for projectparticipantsverificationmail.
Chalmers University of Technology ProjectPersonUpdated API
The ProjectPersonUpdated API from Chalmers University of Technology — 1 operation(s) for projectpersonupdated.
Chalmers University of Technology ProjectPublishStatus API
The ProjectPublishStatus API from Chalmers University of Technology — 1 operation(s) for projectpublishstatus.
Chalmers University of Technology ProjectQueries API
The ProjectQueries API from Chalmers University of Technology — 1 operation(s) for projectqueries.
Chalmers University of Technology Projects API
The Projects API from Chalmers University of Technology — 2 operation(s) for projects.
Chalmers University of Technology ProjectsConnectedToOrganization API
The ProjectsConnectedToOrganization API from Chalmers University of Technology — 1 operation(s) for projectsconnectedtoorganization.
Chalmers University of Technology ProjectsConnectedToPerson API
The ProjectsConnectedToPerson API from Chalmers University of Technology — 1 operation(s) for projectsconnectedtoperson.
Chalmers University of Technology ProjectSearch API
The ProjectSearch API from Chalmers University of Technology — 1 operation(s) for projectsearch.
Chalmers University of Technology SimpleProjectMetadata API
The SimpleProjectMetadata API from Chalmers University of Technology — 1 operation(s) for simpleprojectmetadata.
Chalmers University of Technology SolrImport API
The SolrImport API from Chalmers University of Technology — 1 operation(s) for solrimport.
Scroll within the panel for all 24 ·
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.
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.
Spectral 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.
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.
Organization
JSON SCHEMAProject
JSON SCHEMAJSON Structure 2
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.
Chalmers University Of Technology Organization Structure
JSON STRUCTUREChalmers University Of Technology Project 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.
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.
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 Chalmers University of Technology — 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 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
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/chalmers-university-of-technology · machine-readable index on apis.io