How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Norwegian University of Science and Technology website screenshot

Norwegian University of Science and Technology

The Norwegian University of Science and Technology (NTNU) is Norway's largest university, headquartered in Trondheim with campuses in Gjovik and Alesund. NTNU operates no consolidated institutional developer portal and publishes no OpenAPI, AsyncAPI or other machine-readable API contract of its own. Its one openly callable, institution-operated surface is the OAI-PMH interface of NTNU Open Access Journals at www.ntnu.no/ojs, which answers Identify, ListMetadataFormats and ListSets over sixteen NTNU-published journals. NTNU also runs an institutional API gateway at api.ntnu.no, but every path on it is behind Feide OAuth and no public documentation, contract or scope list is served without an institutional account. Everything else that looks programmable under NTNU's name is operated by somebody else and entered here as a tenant relationship, not as NTNU engineering: research data in the NTNU collection of DataverseNO (run by UiT The Arctic University of Norway on Dataverse software), research information in Cristin and the national research archive NVA (both run by Sikt), timetables in TP on educloud.no, identity in the Feide federation where NTNU exists as the scope ntnu.no on Sikt's national IdP rather than as its own eduGAIN entity, and teaching in a hosted Canvas tenant. This repo previously carried 35 OpenAPI files and 87 derived artifacts that were splits of the generic Dataverse 6.6 product contract; they were the vendor's, not NTNU's, and have been removed.

human only

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles Norwegian University of Science and Technology the way a machine reads it — 12 machine-readable artifacts across 7 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 — Norwegian University of Science and Technology scores 29.9/100 (thin), with a separate agent-readiness read of 5/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Behind a wall

Why this profile is thin

NTNU publishes no API contract of its own — no OpenAPI, AsyncAPI, GraphQL schema, llms.txt or developer portal exists on any NTNU host (www.ntnu.no/llms.txt 404, developer.ntnu.no does not resolve). It does operate a real API gateway at api.ntnu.no, but every path on it, including /docs, /openapi.json and /status, redirects to Feide OAuth and serves the same account-chooser page, so no contract, scope list or reference could be read without an institutional account. The one institution-operated surface that is openly callable is the OAI-PMH interface of NTNU Open Access Journals at www.ntnu.no/ojs, which was fully probed and is recorded as an API. All remaining programmable footprint is tenant: DataverseNO (UiT), Cristin and NVA (Sikt), TP (educloud.no) and Feide (Sikt). This profile is thin because NTNU's own API surface is behind a national identity federation, not because it was unreachable.

An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Norwegian University of Science and Technology'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://www.ntnu.no/ojs/index.php/index/oai?verb=IdentifyHTTP 200
  • https://www.ntnu.no/ojs/index.php/index/oai?verb=ListMetadataFormatsHTTP 200
  • https://www.ntnu.no/ojs/index.php/index/oai?verb=ListSetsHTTP 200
  • https://api.ntnu.no/HTTP 200
  • https://api.ntnu.no/openapi.jsonHTTP 200
  • https://www.ntnu.no/.well-known/security.txtHTTP 200
  • https://www.ntnu.no/llms.txtHTTP 404
  • https://developer.ntnu.no/HTTP 0
  • https://dataverse.no/api/dataverses/ntnuHTTP 200
  • https://api.cristin.no/v2/institutions/194HTTP 200
  • https://api.nva.unit.no/HTTP 403
  • https://tp.educloud.no/ntnu/ws/HTTP 403

Checked 2026-08-30. If this is out of date, tell us on the provider's repo and we will re-run the profile.

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 Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Norwegian University of Science and Technology Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Norwegian University of Science and Technology'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/ntnu/"
   title="Norwegian University of Science and Technology on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/ntnu.svg"
       alt="Norwegian University of Science and Technology Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Norwegian University of Science and Technology

Each block below is one kind of artifact we hold for Norwegian University of Science and 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 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.

NTNU Open Access Journals OAI-PMH

NTNU runs its own Open Journal Systems installation, "NTNU Open Access Journals", on its own registrable domain at www.ntnu.no/ojs, publishing sixteen journals including Nordic ...

NTNU API Gateway (api.ntnu.no)

api.ntnu.no is an NTNU-operated API gateway serving internal and partner integrations. It is live and institution-run — responses carry NTNU's own X-TIA-Processed-by frontend-au...

Cristin Research Information API (NTNU institution 194)

Cristin is Norway's national Current Research Information System, operated by Sikt (the Norwegian Agency for Shared Services in Education and Research) on behalf of every partic...

NVA National Research Archive (NTNU Open successor)

Nasjonalt vitenarkiv (NVA) is the Sikt-operated national open research archive that absorbed NTNU's institutional repository — ntnuopen.ntnu.no now redirects to nva.sikt.no. NTN...

DataverseNO — NTNU Research Data Collection

NTNU's research data is deposited into the "NTNU – Norwegian University of Science and Technology" collection (alias "ntnu") of DataverseNO, the Norwegian national research-data...

TP Timetable Web Service (NTNU instance)

TP (Timeplan) is the timetable, room-booking and course-activity system NTNU uses, hosted on the shared educloud.no platform at tp.educloud.no/ntnu. The /ntnu/ws/ web-service pa...

Feide / Dataporten Identity Federation (NTNU membership)

NTNU authenticates through Feide, the Norwegian national identity federation operated by Sikt, with Dataporten providing OAuth2 / OpenID Connect and SAML single sign-on. NTNU do...

Scroll within the panel for all 7 ·

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.

Ntnu Plans Pricing

2 plans

PLANS

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.

Ntnu Rate Limits

1 limits

RATE LIMITS

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.

Ntnu Finops

FINOPS

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.

Ntnu Domain Security

TLSv1.3 · HSTS · DNSSEC

SECURITY

Ntnu Vulnerability Disclosure

security.txt · contact published

SECURITY

Resources

Every other property we hold for Norwegian University of Science and 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.

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Learn 1

Tutorials, courses, talks, and written guidance

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/ntnu · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Norwegian University of Science and Technology, 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.